You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Switching a rate-limited Codex thread to Antigravity can stay "Working" with nothing happening (not reproduced) #39412
From feedback on the Antigravity integration (post):
I couldn't get it to hand off, I had a task going with codex, and I hit a rate limit, so I switched the model, and it just wouldn't go. Said "working" but nothing was happening
Not reproduced
main @ 6b6950adfe2, Linux x86_64, agy CLI 1.5.12, isolated vp run dev state.
I tried the plain switch without a rate limit: a thread completed a turn on Codex (gpt-6-luna), then I switched the composer model to Antigravity Gemini 3.8 Flash (Low) and sent a follow-up. It worked: a handoff item completed, then the Antigravity turn read a file and answered (about 15 s end to end).
So the plain provider switch works. The difference in the report is that the Codex thread had hit a usage/rate limit mid-task before the switch. I could not trigger a real Codex rate limit here. That state (a run stopped by a usage limit, possibly waiting for its reset or auto-resume, see #24511 / #38498) is the likely trigger.
To investigate
Put a Codex thread into the usage-limited state (failed or waiting-for-reset run), switch the model to Antigravity, send a message, and check whether the new run starts or whether the thread stays "Working" with no provider activity.
After a provider hits its usage limit, switching the thread to another provider and sending a message starts a turn on the new provider promptly, or shows a clear reason why it can't.
Tried to reproduce on main @ 29b42d4 (Linux x86_64, native agy 1.5.12). Not reproduced.
To put a Codex thread in the real usage-limited state without exhausting an account, I ran a dev Codex instance whose provider points at a local endpoint that answers every /v1/responses call with 429 {"error":{"type":"usage_limit_reached","resets_in_seconds":7200,…}}.
New thread on that Codex instance (gpt-6-luna) → run 1 fails at 01:20:33 with Codex's real message: "You've hit your usage limit. Visit https://chatgpt.com/settings/usage …".
In the same thread, switch the composer to Antigravity → Gemini 3.8 Flash and send.
Run 2 starts on the Antigravity instance at 01:20:57 and completes at 01:21:00. Items: handoff completed → user_message → assistant_message ("handed") → checkpoint. Nothing is left in "Working".
So a provider switch after a Codex usage limit works on current main, including the handoff. The report differs in that the limit hit mid-task during a longer Codex turn, on an unknown T3 version. If it still happens, the next useful data is the T3 version and whether the thread showed "Limited"/auto-resume before the switch. Suggest closing unless the reporter can reproduce on a current build.
Activity
juliusmarminge commentedon Nov 20, 2026
Tried to reproduce on main @ 29b42d4 (Linux x86_64, native
agy1.5.12). Not reproduced.To put a Codex thread in the real usage-limited state without exhausting an account, I ran a dev Codex instance whose provider points at a local endpoint that answers every
/v1/responsescall with429 {"error":{"type":"usage_limit_reached","resets_in_seconds":7200,…}}.gpt-6-luna) → run 1 fails at 01:20:33 with Codex's real message: "You've hit your usage limit. Visit https://chatgpt.com/settings/usage …".handoffcompleted →user_message→assistant_message("handed") →checkpoint. Nothing is left in "Working".So a provider switch after a Codex usage limit works on current main, including the handoff. The report differs in that the limit hit mid-task during a longer Codex turn, on an unknown T3 version. If it still happens, the next useful data is the T3 version and whether the thread showed "Limited"/auto-resume before the switch. Suggest closing unless the reporter can reproduce on a current build.
juliusmarminge commentedon Nov 20, 2026
Closing: not reproducible on current main (agy 1.5.12); test details above. Reopen with a repro on a current build if it still happens.