Skip to content

[Bug]: Antigravity run_workflow child agents hang indefinitely waiting for approval on run_command in Full access #40609

Closed as duplicate

Description

@KenionX

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

  1. Open a thread in T3 Code using the managed Antigravity provider (agy.exe acp, 1.5.13) in full-access mode (interactionMode: "default", gemini-4-neon xhigh).
  2. Ask the agent to run a parallel workflow via run_workflow (e.g., 3 parallel agent(..., type_name="self") workers researching different topics with search_web).
  3. Have one or more workflow child agents invoke run_command (in our repro, 2 of the 3 workers called run_command with curl.exe -sI to resolve Google search redirect URLs, while the 3rd only called search_web and finish).
  4. Wait for the workflow to finish and inspect the workflow task log and child conversation SQLite DBs.

Expected behavior

In full-access mode, run_workflow child agents should be able to execute run_command (matching the parent Antigravity session) without hanging on hidden approval prompts—or fail cleanly if approval cannot be requested—and the workflow should complete normally.

Ideally, T3 Code should also indicate that a run_workflow background task is running rather than leaving the thread looking idle.

Actual behavior

  • The 1 worker that only called search_web and finish completed cleanly in ~53s.
  • The 2 workers that called run_command never spawned a powershell.exe or curl.exe process and hung indefinitely (manage_task stayed RUNNING with Last progress: 6m42s ago until manually cancelled).
  • Inspecting the child conversation SQLite DBs (antigravity-acp/conversations/<childId>.db, steps table) showed completed search_web steps at status = 3 (DONE), while each stuck run_command step stayed frozen at status = 9 (waiting for user approval), with no approval prompt surfaced in T3 Code (t3_pending_request empty) and no 60s timeout.
  • T3 Code showed no live progress or active indicator for run_workflow while it was running/hung, so from the UI it was impossible to tell whether the workflow was executing or stuck.
  • Re-running the exact same 3-agent run_workflow while explicitly instructing the child agents not to call run_command (search_web + finish only) completed cleanly in ~72s.

Related issues

Impact

Major degradation or frequent failure

Version or commit

0.1.12-nightly.20261121.5064

Environment

Windows, T3 Code (Nightly) 0.1.12-nightly.20261121.5064, managed agy.exe 1.5.13, gemini-4-neon (xhigh), full-access

Logs or stack traces

Task log (stuck for 6m42s+ before manual cancel):
- [phase] Research
- Starting 3 parallel research agents
- [agent:self] WASI Researcher: running (2974af57-95c1-4df3-bcd3-7344378fba39)
- [agent:self] io_uring Researcher: running (22012723-e408-4be3-9b3b-c1b301854a51)
- [agent:self] SQLite WAL Researcher: done (216db0ba-7f36-4f4f-9f94-d949c6750bc4)

Child SQLite DB steps:
- 2974af57-95c1-4df3-bcd3-7344378fba39.db: idx 0..6 status = 3 (DONE), idx 7 step_type = 132 status = 9 (run_command, no child shell process spawned)
- 22012723-e408-4be3-9b3b-c1b301854a51.db: idx 0..7 status = 3 (DONE), idx 8 step_type = 132 status = 9 (run_command, no child shell process spawned)

Spawned process command line:
agy.exe acp --gemini-dir <profile> --app-data-dir antigravity-acp

Screenshots, recordings, or supporting files

No response

Workaround

Explicitly instruct run_workflow child agents not to call run_command (or other tools requiring approval) and only use auto-allowed tools such as search_web, read_file, and finish.

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Nov 21, 2026
  2. S1ckZer commented on Nov 21, 2026

    @S1ckZer

    annoying bug

  3. juliusmarminge commented on Nov 21, 2026

    @juliusmarminge
    Member

    This is the same problem as #39029, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions