Skip to content

[Bug]: Antigravity hub accounts show raw auth filenames instead of email initials badges in Usage → Limits #40678

Open

Description

@rune-gh

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server, packages/contracts or packages/shared

Steps to reproduce

  1. Configure a CLIProxyAPI-compatible usage hub (Settings → Providers → Usage providers → Add hub) that holds two or more Antigravity accounts alongside Claude or Codex accounts, where GET /v0/management/auth-files returns "email" and "project_id" for every account (e.g. id: "antigravity-alice@example.com.json", email: "alice@example.com", project_id: "...").
  2. Ensure Google's https://www.googleapis.com/oauth2/v2/userinfo call succeeds through POST /v0/management/api-call (the normal authenticated case).
  3. Open Usage → Limits.

Expected behavior

Antigravity hub accounts should render the same compact circular email-initials avatar badge (and show the toggleable account email in the hover popover) as Claude, Codex, and Grok hub accounts.

Actual behavior

Every Antigravity hub account bar renders the raw auth-file id (with .json stripped, e.g. antigravity-alice@example.com) as plain text with no circular initials avatar, and the hover popover has no avatar or account email row — even though GET /v0/management/auth-files provides email for those accounts.

Root cause

In apps/server/src/usage/cliproxyApi.ts (lines 387–399 on main @ f9b19a7f85), the antigravity hub reader drops ...listedIdentity(account) whenever userinfo succeeds (onSome):

// Local Antigravity reports no e-mail, so the Google account fingerprint is what pools the two.
const fingerprint = yield* call("https://www.googleapis.com/oauth2/v2/userinfo").pipe(
  Effect.flatMap(decodeJson),
  Effect.flatMap(antigravityAccountFingerprint),
  Effect.option,
);
const usageLimits = makeUsageLimits({ checkedAt, windows });
return Option.match(fingerprint, {
  onNone: () => ({ ...listedIdentity(account), usageLimits }),
  onSome: (credentialFingerprint) => ({
    usageLimits: { ...usageLimits, credentialFingerprint },
  }),
});

Because email is omitted on onSome:

  1. collectLimitAccounts (packages/shared/src/usageLimits.ts:430-431) falls back to displayName: account.email ? null : hubAccountName(account) (account.id.replace(/\.json$/i, "")) with email: undefined.
  2. The UsageLimits bar label renderer prefers displayName over email, so it prints the raw filename string instead of the circular initials badge.

Note on #38097: Open PR #38097 bridges driver:credential:<fingerprint> to driver:<email> in accountKeyResolver (packages/shared/src/usageLimits.ts) so local Antigravity instances with auth.email pool with hub accounts, but explicitly leaves cliproxyApi.ts unchanged (onSome still drops email). As a result, hub-only Antigravity accounts will still display raw auth filenames instead of email initials badges even after #38097 merges.

Suggested fix

Once accountKeyResolver bridges driver:credential:<fingerprint> ↔ driver:<email> when a report carries both (as in #38097), HUB_PROVIDERS.get("antigravity") in apps/server/src/usage/cliproxyApi.ts can return ...listedIdentity(account) in the onSome branch as well (and update apps/server/src/usage/cliproxyApi.test.ts:548). Hub Antigravity accounts will then keep email for initials badges and hover popovers while still deduplicating cleanly against local Antigravity logins that only report credentialFingerprint.

Impact

Minor bug or occasional failure

Version or commit

T3 Code 0.1.11 (main @ f9b19a7f85)

Environment

Windows / macOS desktop (T3 Code 0.1.11), CLIProxyAPI-compatible usage limit hub (t3code-proxy)

Workaround

None clean. Renaming auth files on the hub only shortens the raw plain-text filename shown in the bar; it does not restore the circular initials badge or popover email.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions