fix(Antigravity menu): display email of Google AI account

[gianpaj]

When logged in with a free tier account (Antigravity Starter), you see the email correctly (the email is blurred)

But when logged in with a paid Google AI account, you don't:

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 20, 2026, 4:57 PM ET / 20:57 UTC.

Summary
Keep open: the screenshots show missing account identity, but do not establish a paid-account parsing defect or a verified fix. Repository policy also disables automatic closure.

Reproducibility: no. the screenshots establish the symptom, but the version and source are missing, and current tests cover both paid-account email display and intentional omission after identity-fetch failure.

Ways to help us reproduce this

• Add expected vs actual behavior.

Next step
Obtain the CodexBar version and selected Usage source for both screenshots, then redacted source diagnostics if needed; the missing source identity prevents a safe focused repair.

Review details

Best possible solution:

Display email verified for the quota-producing account, preserving source isolation and leaving identity unavailable when it cannot be established.

Do we have a high-confidence way to reproduce the issue?

No: the screenshots establish the symptom, but the version and source are missing, and current tests cover both paid-account email display and intentional omission after identity-fetch failure.

Is this the best way to solve the issue?

Unclear: there is no proposed patch, and adding a generic account-email fallback could mislabel another account's quotas; identify the failing source before choosing a repair.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The failing screenshot's CodexBar version, selected usage source, and identity response are unknown, so a parser defect cannot yet be distinguished from a documented identity-free fallback.

Codex review notes: model internal, reasoning medium; reviewed against 4b86ea7b3971.

Label changes

Label changes:

• add P2: Missing account identification is a limited menu usability problem; quota display still works.
• add impact:ux-friction: An unlabeled quota card makes it harder to identify which Google account is being displayed.
• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.

Label justifications:

• P2: Missing account identification is a limited menu usability problem; quota display still works.
• impact:ux-friction: An unlabeled quota card makes it harder to identify which Google account is being displayed.

Evidence reviewed

What I checked:

• Screenshots confirm the visible difference: Inspected both downloaded issue images. The first contains a blurred account label and an Antigravity Business plan label; the second has weekly quota rows but no email or plan. Different quota layouts suggest different source paths; neither image identifies the CodexBar version or selected source.
• Identity enrichment is already implemented: The quota-summary fetch attempts GetUserStatus for identity and preserves successful quota data if that optional request fails. The identity request has a one-second timeout cap. This provides a plausible explanation, not proof of the reporter's failure. (Sources/CodexBarCore/Providers/Antigravity/AntigravityStatusProbe.swift:1587, 4b86ea7b3971)
• Paid identity and absent identity are both covered: Quota-summary tests expect a returned Pro account email to survive conversion and explicitly expect nil email when the identity endpoint fails. MenuCardAntigravityTests also verifies that a Paid snapshot displays its supplied email. (Tests/CodexBarTests/AntigravityQuotaSummaryTests.swift:258, 4b86ea7b3971)
• Menu does not filter email by subscription: The shared card reads the provider-scoped snapshot email without a free-versus-paid condition. (Sources/CodexBar/MenuCardView.swift:989, 4b86ea7b3971)
• Documented identity-free source: The supported agy print-mode report contains neither account nor plan identity. Its usage must not be labeled with an unrelated selected Google account. (docs/antigravity.md:35, 4b86ea7b3971)
• Release comparison: The inspected Antigravity core, menu-card implementation, and quota-summary tests have no changes between v0.62.0 and current main. No fix specific to this report was established. (4b86ea7b3971)

Likely related people:

• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• Zhuoyuan Hao: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• Yuxin Qiao: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

Email depends on the source: OAuth supplies account claims, local HTTPS attempts a separate user-status lookup, and print-report parsing creates a quota snapshot without email. These paths contain no paid/free display branch. The screenshots alone do not establish which source ran or whether it supplied email, so this remains open. Any fix should preserve verified CLI identity rather than attach the selected Google account’s email to potentially different local quotas.