[Bug]: Detects Paid Tier But Revert to Free?

[iamhenry]

Description

I tried to add a paid account with and without providing a project id and both automatically revert back to a free tier even after briefly detected the paid tier.

Any ideas why it reverts here? I've had this happen with 2 accounts.

[shekohex]

Can you see what tier it has in the antigravity-accounts.json file? This should be in ~/.local/share/opencode

Do not share the whole file, just see what tier they are in.

[iamhenry]

@shekohex it said free tier but I manually changed it to paid. Not sure if that's gonna work tho bc I don't know how to force switching accounts. My current one hasn't hit it's limit

[shekohex]

Okay this is definitely a bug, changing it manually is a workaround for now. I will check the code later on tomorrow.

But of course feel free to ask Opus or Gemini and fill out a PR :)

[iamhenry]

Sounds good. If I can squeeze out some time from the fam I'll try to take a stab at it

It'll mostly be vibe coded since I'm not a dev 😅

[iamhenry]

Ok I did my best to provide a diagnosis that doesnt include noise. I provided the logs and scenarios I encountered to at least give you a jump start on the solution. It contains the logs in encountered during the flow and how it only added free tier to my .json file

I hope you find this research useful. Lmk how else i can help

---

Diagnosis

Tier detection works correctly (logs show g1-pro-tier detected), but the detected tier is lost due to two separate issues in the codebase.

BUG # 1: Fallback Discards Detected Tier (PRIMARY)

Location: src/antigravity/oauth.ts:168

Problem: When all 3 endpoints (daily, autopush, prod) fail to return a projectId, the function returns a hardcoded fallback that discards the detected tier:

return { projectId: "", tier: "free" };

When it occurs: New accounts that haven't used Gemini/Cloud Code before - the cloudaicompanionProject field is not populated in the API response.

Evidence:

[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier  ← DETECTED ✓
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier  ← DETECTED ✓
Failed to resolve Antigravity account info: loadCodeAssist missing project id...

Result: tier: "free" saved to JSON despite paid tier being detected.

Additional context: User-provided projectId does NOT help because tier always comes from accountInfo.tier (line 249), which is "free" when the fallback executes.

---

BUG # 2: Callback Missing Tier Field (SECONDARY)

Location: src/plugin.ts:363-371

Problem: The callback returned to opencode's auth system does not include the tier field:

callback: async (): Promise<AntigravityTokenExchangeResult> => {
  return {
    type: "success",
    refresh: combinedRefresh,
    access: firstAcc.access,
    expires: firstAcc.expires,
    email: firstAcc.email,
    projectId: firstAcc.projectId,
    // ❌ MISSING: tier: firstAcc.tier
  };
},

When it occurs: Even when tier is correctly detected and saved to antigravity-accounts.json, opencode's auth system doesn't receive the tier in the callback response.

Impact: If opencode rebuilds account state from its own auth data (which lacks tier), the tier could be lost.

---

DATA FLOW DIAGRAM

┌─────────────────────────────────────────────────────────────────┐
│                    fetchAccountInfo()                           │
│  for each endpoint:                                             │
│    tier = "free"  ← RESET EACH ITERATION                        │
│    detect paidTier → tier = "paid" ✓                            │
│    if (projectId) return {tier}  ← NEVER FIRES (no projectId)   │
│                                                                 │
│  return { projectId: "", tier: "free" }  ← BUG #1               │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│                    plugin.ts                                    │
│  saveAccounts() → tier: "free" saved to JSON                    │
│  callback() → returns to opencode WITHOUT tier  ← BUG #2        │
└─────────────────────────────────────────────────────────────────┘

---

REPRODUCTION SCENARIOS

Both scenarios result in tier reverting to "free":

1. Without explicit projectId - API returns no projectId for new accounts
2. With explicit projectId - User-provided projectId doesn't bypass the fallback

Tested with:

• Brand new email account added to family plan
• Existing email account that created a GCP project for the first time

---

PROPOSED FIX LOCATIONS

Priority	Location	Fix
P0	oauth.ts:168	Preserve detected tier in fallback return
P1	oauth.ts:114	Accumulate tier across loop iterations instead of resetting
P2	oauth.ts:249	Use detected tier even when user provides projectId
P3	plugin.ts:371	Add tier: firstAcc.tier to callback return

[shekohex]

Hi, please try v0.2.12 of the plugin, and let me know if you still having the same issue so we can reopen this bug report.

backup your old antigravity-accounts.json file and keep it somewhere else and delete the old one so you can login in again.

https://github.com/shekohex/opencode-google-antigravity-auth/releases/tag/v0.2.12

[iamhenry]

so i think it might've worked because the .json file DID add the "tier": "paid" to all my accounts when i did not provide any project id's for any of my accounts

I did clear my cache before the attempt.

however, here are the logs saying it added a free tier to the last account added, which is inaccurate:

┌  Add credential
│
◇  Select provider
│  Google
│
◇  Login method
│  OAuth with Google (Antigravity)
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier

You have 1 account(s) configured. Add another? (y/n): y
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier

You have 2 account(s) configured. Add another? (y/n): y
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier
[antigravity] Detected free tier variant: free-tier

You have 3 account(s) configured. Add another? (y/n): n
│
●  Multi-account setup complete!
│
◇  Login successful
│
└  Done

[shekohex]

so i think it might've worked because the .json file DID add the "tier": "paid" to all my accounts when i did not provide any project id's for any of my accounts

I did clear my cache before the attempt.

however, here are the logs saying it added a free tier to the last account added, which is inaccurate:

┌  Add credential
│
◇  Select provider
│  Google
│
◇  Login method
│  OAuth with Google (Antigravity)
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier

You have 1 account(s) configured. Add another? (y/n): y
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier

You have 2 account(s) configured. Add another? (y/n): y
Project ID (leave blank to use your default project): 
[antigravity] Detected free tier variant: free-tier
[antigravity] Detected paid tier from paidTier field: g1-pro-tier
[antigravity] Detected free tier variant: free-tier

You have 3 account(s) configured. Add another? (y/n): n
│
●  Multi-account setup complete!
│
◇  Login successful
│
└  Done

I guess the logs may have been misleading, but if your third account is free and detected as paid in this case, I guess we still have a bug somewhere and could be the logs still misleading.

[iamhenry]

To be clear, all of my accounts are paid. It did indicate that correctly in the .json file. There might be a bug still somewhere.

[shekohex]

Okay, keeping this open until we solve it.

[iamhenry]

sounds good. i'll take a deeper look when i get a chance

[iamhenry]

Here's an update investigation based on the new logs and taking into account the recent commits that were merged to main

Below is my ai assisted investigation:

---

Investigation Update

Problem

The tier detection VALUE is saved correctly ("tier": "paid" in JSON), but the LOGGING is misleading. The last log message shows "Detected free tier variant" which causes users to believe their tier was incorrectly set to "free".

Root Cause

Commit 3e2202a fixed tier value accumulation by hoisting detectedTier outside the loop, but did not update the logging condition at oauth.ts line 133-134. The log still triggers based on API response content, not on whether the tier state actually changed.

Reproduction Scenarios

Scenario: First endpoint missing projectId (account 3 in user's logs)

Endpoint 1 (daily):
  → allowedTiers has "free-tier" → logs "Detected free tier variant: free-tier"
  → paidTier has "g1-pro-tier"  → logs "Detected paid tier...", sets detectedTier="paid"
  → projectId NOT found → CONTINUES

Endpoint 2 (autopush):
  → allowedTiers has "free-tier" → logs "Detected free tier variant: free-tier" ← MISLEADING
  → projectId found → RETURNS with tier="paid" ✓

Result: Last log says "free tier variant" but actual tier is "paid". User sees misleading output.

Potential Solutions

#	Solution	Confidence	Complexity	Description
1	Add guard to logging condition	95%	Low	Change line 133 to else if (tierId !== "legacy-tier" && detectedTier !== "paid") - only log if tier isn't already determined
2	Log only final tier determination	85%	Medium	Remove intermediate logs, add single log after loop: [antigravity] Final tier: ${detectedTier}
3	Consolidate detection logic	70%	Medium	Check paidTier first (more authoritative), then allowedTiers. Log once per endpoint with full context