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
Support Antigravity background tasks in T3 Code UI and t3_background_wait#39902
When an Antigravity agent launches background work via its native run_command (backgrounded past WaitMsBeforeAsync) or schedule tools and ends its turn to wait for reactive wakeup, those active background tasks are not visible in T3 Code's UI, and t3_background_wait explicitly only supports Claude and OpenCode.
What happens today
In an Antigravity thread on T3 Code, the agent starts one or more long-running background shell jobs via run_command (e.g. multi-minute simulations or test suites) and ends its turn to wait for completion notifications.
Because t3_background_wait is limited to Claude/OpenCode and Antigravity background tasks are not surfaced in T3 Code's background-work UI, the user sees no active background tasks or indicator in the thread UI — making it look like nothing is running or that reporting is broken.
Requested feature
Surface active Antigravity background tasks (run_command, schedule) in T3 Code's thread UI (showing running status / task summaries while the thread is waiting on them).
Extend t3_background_wait (or the equivalent Antigravity ACP adapter lifecycle) to support Antigravity task IDs so an Antigravity agent can explicitly mark awaited background jobs as active work in T3 Code and clear them when done.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
(Moved from #39898 per maintainer guidance.)
Summary
When an Antigravity agent launches background work via its native
run_command(backgrounded pastWaitMsBeforeAsync) orscheduletools and ends its turn to wait for reactive wakeup, those active background tasks are not visible in T3 Code's UI, andt3_background_waitexplicitly only supports Claude and OpenCode.What happens today
run_command(e.g. multi-minute simulations or test suites) and ends its turn to wait for completion notifications.t3_background_waitis limited to Claude/OpenCode and Antigravity background tasks are not surfaced in T3 Code's background-work UI, the user sees no active background tasks or indicator in the thread UI — making it look like nothing is running or that reporting is broken.Requested feature
run_command,schedule) in T3 Code's thread UI (showing running status / task summaries while the thread is waiting on them).t3_background_wait(or the equivalent Antigravity ACP adapter lifecycle) to support Antigravity task IDs so an Antigravity agent can explicitly mark awaited background jobs as active work in T3 Code and clear them when done.Related issues
t3_background_waitlisted to unsupported providers including ACP agents)All reactions