[blitzcrieg1]

Codex sits in "Accounts with no domain", because its session file holds only IDs, so the Identity page cannot say whether its account is personal. The maintainer decided on 2026-11-07 to read its sign-in file to answer that.

Review this one carefully: it makes a security sensor read a file holding live credentials.

What it reads

From auth.json under CODEX_HOME or ~/.codex:

• Only the email claim of tokens.id_token, and only when auth_mode is chatgpt.
• Only the domain is kept, with source codex_auth. The full address follows the existing AGENTMETRY_LOG_ACCOUNT_EMAIL=1 opt-in.
• Nothing else in the file is copied, stored, logged or sent. An error carries no content from it.

The signature is not checked, so this is what the file says, not proof of who made a call. An API-key sign-in reports no domain. AGENTMETRY_CODEX_AUTH_DOMAIN=0 turns it off.

The cost

• The hook loads a file holding live tokens on every Codex tool call, briefly and without keeping them.
• Endpoint security tools may flag a process reading that file. This has not been tested against any EDR.
• This reverses "auth.json is never read" from feat(dashboard): add an Identity section, with Codex and Antigravity accounts #395. The code, schema doc and changelog are updated. A search of the README, docs and site found no other page making that promise.

It is on by default for now. Reconsider making it opt-in before a public release or a pilot.

Also fixed

The Identity view lost a domain row's IDs when another agent reported that domain first, so Codex's IDs now survive joining a row.

Checks

Run from this branch on Windows:

• pytest -q: 2287 passed, 7 skipped
• ruff check agentmetry tests: clean
• agentmetry benchmark: 0 missed, 0 false positives
• Dashboard: 201 tests pass, type check clean
• Fingerprint: 15846a0915769d4a, with no frozen file touched
• Tests with synthetic tokens: the access token, refresh token, API key, name, subject and full email reach neither the hook payload nor the stored event
• On the maintainer's real file, showing keys only: domain and IDs found in about 3 ms, classified as personal, with no email key and no token in the block

Not proven

• No real Codex session has produced the domain through a live hook. That test comes after merge.
• Behaviour under any EDR, including whether the read raises an alert.
• Other operating systems and other Codex versions, where this undocumented layout may differ.

🤖 Generated with Claude Code

[blitzcrieg1]

Replaced by #398. The secret scan flagged a test fixture here: a synthetic token part that decodes to "not json", not a real secret. #398 carries the same change with that value built at runtime.