Repository navigation
Antigravity provider session fails to open with Argon 4 Medium after weekly quota reset #32856
Description
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
Steps to reproduce
Observed sequence (a deterministic reproduction and repeatability have not been established):
- Use T3 Code Nightly 0.1.8-nightly.20261108.4353 (3cd97a1) with AGY CLI v1.5.3 configured as the custom executable, without a separate server installation.
- After the team reset the weekly quota, select Argon 4 with Medium reasoning effort.
- Try to start/use the Antigravity provider session.
The Argon 4 usage-limit display is empty on the T3 Code side. The session fails to open. This was observed on the updated version; a causal link to the update, quota reset, or setup has not been confirmed.
Expected behavior
The Antigravity provider session opens and processes messages.
Actual behavior
T3 Code shows "Provider session failed to open" and does not open the provider session. The Argon 4 usage-limit display is empty.
Impact: work is blocked in this affected Antigravity session. Behavior with other providers/models and repeatability have not been established.
Related but not an exact match: #32419 reports an incorrect 100%-used quota display while Argon turns still succeed. Here the display is empty and the provider session fails to open; whether the underlying causes are related is unknown.
Impact
Blocks work completely
Version or commit
T3 Code Nightly 0.1.8-nightly.20261108.4353 (3cd97a1)
Environment
AGY CLI v1.5.3; Antigravity provider; custom executable configured without a separate server installation; Argon 4 with Medium reasoning effort. OS/version not supplied.
Logs or stack traces
Provider session failed to open
Failed to open antigravity provider session provider-session:provider-instance:antigravity:thread:07e9c026-4428-400d-aabe-f74fdfc9b28c:f1f6ff7b-a302-4576-bb0c-93bcf9015cbc.Screenshots, recordings, or supporting files
Activity
meinarus commentedon Nov 8, 2026
I had the same issue, and I noticed it might be related to how T3 Code handles permission modes for agy acp (from CLI). Supervised works fine for me, but Auto-accept edits and Full Access both give me that error.
For now, switching to Supervised seems to work as a workaround.
t3dotgg commentedon Nov 9, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of Theo
Likely fixed by #33143, merged as 51675e0. With
agy1.5.3 as the custom executable, T3 sent session modes the CLI rejects (Invalid value "yolo" for session config option "mode"). Full access is the default, so every new thread failed with "Provider session failed to open".Verified with real
agy1.5.3. Onmaina Full access thread fails with that error, and on the fix it opens and runs. If you still see the error after updating, please share the provider log line that follows "Failed to open antigravity provider session".shivamhwp commentedon Nov 10, 2026
Closing as fixed by #33143, merged as 51675e0. T3 no longer sends
agythe session modes it rejects, so Full access and Auto-accept edits threads open again. If sessions still fail to open, or the quota display is still wrong, on a build that includes that commit, reopen this or file a new issue with the build number.