fix: bypass soft quota check for gemini-cli requests

[xzipyx]

Problem

The AccountManager incorrectly applies the Antigravity soft quota check to gemini-cli requests. When an account has exhausted its Antigravity quota (100% usage), isOverSoftQuotaThreshold returns true. This causes the account selection logic to skip the account, even if cli_first is enabled or the CLI pool is explicitly requested.

Impact

Users cannot utilize the gemini-cli pool as a fallback when their Antigravity quota is full.

Proposed Fix

Modify src/plugin/accounts.ts to bypass the soft quota check when the requested headerStyle is gemini-cli.

Changes in src/plugin/accounts.ts

• Updated getCurrentOrNextForFamily (both hybrid and sticky paths) to skip quota threshold checks for CLI requests.
• Updated getNextForFamily filter logic to allow CLI requests to proceed regardless of Antigravity quota status.

Verification

Verified locally with a new test case in src/plugin/accounts.test.ts and confirmed via debug logs that gemini-cli requests now proceed when Antigravity quota is exhausted.

[github-actions]

👋 Thanks for opening this issue!

Confirmed: this is a real logic bug, not setup error. soft_quota_threshold_percent (Antigravity usage) is being applied to gemini-cli routing, which contradicts cli_first/dual-pool behavior in the docs. Temporary workaround: set soft_quota_threshold_percent to 100 in ~/.config/opencode/antigravity.json so Gemini CLI requests are not blocked when Antigravity is exhausted.

---

This is an automated response. A maintainer will review your issue soon.

[NoeFabris]

That should be fixed on the beta version, please give it a go

[xzipyx]

1.5.0-beta.0 is the version where this bug appeared

[NoeFabris]

@xzipyx new fix released in the latest beta

[NoeFabris]

Fixed in v1.5.0. Please update to v1.5.0.