[Bug]: Antigravity (agy) sessions show Idle while they are running #19829

Activity

1. OrcaWin

   added

   bugSomething isn't workingSomething isn't working

   on Sep 19, 2026
2. OrcaWin

   added the

   Bug

   issue type on Sep 19, 2026
3. nwparker commented on Sep 19, 2026

   

   nwparker

   on Sep 19, 2026

   Contributor

   More actions

   Additional installed-CLI verification (agy 1.2.7, macOS): the native read-only command

   agy --print /hooks --output-format json --print-timeout 5s --sandbox

   returned SUCCESS, num_turns: 0, and one enabled hook named orca-status. Its command actions register these five events:

   • PreInvocation
   • PostInvocation
   • PreToolUse
   • PostToolUse
   • Stop

   ELI5: agy itself confirms that it loaded Orca’s hook instructions. This is stronger than only checking that a configuration file exists. It still does not prove that a particular event was emitted, that the command completed, or that Orca received its status update.

   No hook settings were changed. The raw response includes local command/path details and is intentionally not attached. This command is verified on 1.2.7; do not assume older versions support the same print-mode command.

   The earlier workspace-local hook probes were not loaded by this installation, and generation continues to fail with 401 ACCESS_TOKEN_TYPE_UNSUPPORTED. Therefore successful-turn hook delivery and the reported idle-while-running behavior remain unverified; there is no new status-mapping patch or closure claim from this check.
4. nwparker commented on Sep 20, 2026

   

   nwparker

   on Sep 20, 2026

   Contributor

   More actions

   Fresh awin evidence: agy 1.2.7 reached a real authenticated TUI and returned to a bare composer; a refreshed /hooks probe reported all five managed orca-status events. This confirms the CLI and hook registration, but does not prove Orca received lifecycle events or rendered Running instead of Idle.

   ELI5: the messenger is installed and the phone can place a call; we still need to observe Orca receiving the call and changing the status label. The idle-while-running report remains open.
5. nwparker commented on Sep 20, 2026

   

   nwparker

   on Sep 20, 2026

   Contributor

   More actions

   ELI5: agy itself can be ready while Orca still shows Idle if Orca never receives the hook event that means “work started.” The real TUI and hook-registration probes pass, but a live Orca-rendered Idle → Running transition has not been captured, so this issue stays open without a speculative fix.
6. nwparker commented on Oct 24, 2026

   

   nwparker

   on Oct 24, 2026

   Contributor

   More actions

   Thanks for the report! Please retest on 1.4.239+ and share: Orca version, OS, agy --version, and orca worktree ps --json during a running turn plus the agent-hooks log lines (redacted). Please redact anything private before sharing; screenshots or log excerpts are fine.
7. nwparker commented on Nov 6, 2026

   

   nwparker

   on Nov 6, 2026

   Contributor

   More actions

   Thanks for the report. We couldn't reproduce this on the current build, and several related fixes have landed since. Could you retest on the latest Orca and, if it still happens, reply with: OS + Orca version + agy --version, minimal steps to reproduce, and any relevant logs/screenshots? We'll close this as insufficient information in 14 days if we don't hear back.

   The likely cause (the status hook waiting on stdin and getting killed before reporting) was fixed in #24596, #24622, #27713, #33645 and #34128 — if it still happens, the hook/status lines from Orca's logs while the session is running would help.
8. nwparker

   added

   pending_reproRepro attempted; still pending conclusive reproductionRepro attempted; still pending conclusive reproduction

   on Nov 6, 2026
9. nwparker commented on Nov 7, 2026

   

   nwparker

   on Nov 7, 2026

   Contributor

   More actions

   We retested this on current main (c108ee4) with a real agy 1.5.2 in an Orca dev build (e2e build, isolated profile and HOME) on macOS. Orca shows agy as Working for the whole run and doesn't fall back to Idle.

   What we ran

   • We started agy --dangerously-skip-permissions in Orca terminal tabs. Orca installed its orca-status hooks (PreInvocation, PostInvocation, PreToolUse, PostToolUse and Stop) into the isolated ~/.gemini/config/hooks.json.
   • agy's model requests went to a local scripted Gemini endpoint through agy's supported GOOGLE_GEMINI_BASE_URL. Each turn was a real agy turn: the model called run_command (sleep 8), agy ran its safety-rater calls, and the model then sent its final text. A turn took about 25 s.
   • We typed the prompt through the real Orca terminal input and checked both the store and the rendered sidebar status (AgentStateDot aria-label) every 500 ms.

   Result

   • In each of 3 consecutive turns, the status changed to Working within about 0.5–1 s of Enter. It stayed Working through generation and the 8 s tool run, then changed to Done when agy returned to its composer. No sample during a turn showed Idle or Done.
   • Subagent case: the model called invoke_subagent, and the subagent ran a 10 s command. The parent printed its text and returned to the composer at about 14 s, but Orca kept the pane Working until the subagent finished and the parent's final reply arrived (Done at about 37 s). This is the case fix(agent-status): an Antigravity subagent finishing no longer ends its parent's turn #33645 and fix(agent-status): keep Antigravity panes working until invoke_subagent helpers finish #34128 fixed.

   Fixes that landed since 1.4.198: #24596 (POSIX hooks launched through sh with bounded stdin), #27713, #33645 and #34128.

   Closing as fixed. If you still see Idle while agy is running on the latest Orca, please reopen with your Orca version, agy --version, and orca worktree ps --json taken during the run.
10. nwparker

    closed this as completedon Nov 7, 2026