Skip to content

[Bug]: Antigravity does not resume turns on subagent/background task completion #30082

Closed as duplicate

Description

@vedmalex

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. Start T3 Code and open a session with the Antigravity provider (gemini-3.8-flash-high).
  2. Run a task that delegates work to a subagent (delegate_task) or executes background operations.
  3. Wait for the subagent or background task to complete.

Expected behavior

The parent Antigravity turn receives the continuation delivery and resumes processing the subagent results.

Actual behavior

The parent session stalls indefinitely in "Waiting on background task..." because deferFinalizeForBackgroundWork and enablePostSettleContinuation are omitted from the Antigravity ACP adapter flavor. Additionally, assistant streaming paragraphs were held until full turn completion if no markdown boundary followed.

Impact

Major degradation or frequent failure

Version or commit

main @ cefb544

Environment

macOS, Antigravity ACP runtime 1.4.5, gemini-3.8-flash-high

Workaround

Manually interrupting or sending new prompts after subagents finish.

Related issues

Activity

  1. DeliciousBuding commented on Nov 14, 2026

    @DeliciousBuding

    Confirming this is reproducible on the latest Windows release build (T3 Code Beta 0.1.9.0) with the Antigravity provider:

    • Environment: Windows 11, T3 Code (Beta) 0.1.9.0, Antigravity ACP provider
    • Observed behavior: When a parent Antigravity turn spawns a delegated/background task (e.g. \delegate_task), the parent turn does not automatically resume after the child task settles.
    • Build check: Inspecting the bundled server in 0.1.9.0 confirms \makeAntigravityAcpAdapterFlavor\ still omits \�nablePostSettleContinuation: true.

    Looking forward to #30083 landing!

  2. mahammadismayilov commented on Nov 18, 2026

    @mahammadismayilov

    This was generated by AI during triage.

    Confirming this on Windows 11 (0.1.10-nightly.20261116.4787, web surface, agy.exe 1.5.9, gemini-4-hydrogen) with Antigravity's schedule / background task wakes:

    1. Antigravity starts a background command, sets a timer, and ends its turn (session/prompt finishes at 06:39:50Z), so T3 finalizes Run 266 and stops listening for new turns.
    2. When the timer fires (06:41:22Z–06:41:43Z), Antigravity runs tools and writes a reply in its native transcript (steps 5783–5790), but nothing appears in T3.
    3. Sending a dummy message like "huh" or "status" (06:41:51Z, Run 267) suddenly reveals those held updates in statev2.sqlite (06:41:57Z); wakes with no follow-up user message (06:45:14Z) never appear at all.

    In 0.1.10-nightly.20261116.4787, makeAntigravityAcpAdapterFlavor (AntigravityAdapterV2.ts) still omits enablePostSettleContinuation / deferFinalizeForBackgroundWork / followAgentWorkState, and AcpSessionRuntime closes assistantUpdatesOpenRef after session/prompt settles (related open PRs: #30083, #37485, #37489).

    Triaged with Gemini 4 Hydrogen via Antigravity.

  3. dimsedra commented on Nov 19, 2026

    @dimsedra

    Still hitting this every day on 0.1.11-nightly.20261118.4890 with agy acp 1.5.11 on Linux, for both background commands (like unit tests) and subagents.

    In standalone agy CLI, when the main agent puts a task in the background and waits, the CLI wakes the main agent up automatically once the task finishes and prints the final answer. In T3 Code, as soon as the agent pauses to wait, T3 treats the whole turn as finished. When the background work completes later, the thread stays completely idle until I manually send a nudge like "done yet?" or "any update?" just to wake the agent up and see the result.

    Also shared this experience on the related issues: #36105, #38478, #38535, and #16442.

  4. t3dotgg commented on Nov 19, 2026

    @t3dotgg
    Member

    Note

    🤖 Claude Fable 5.2 responding on behalf of Theo

    Partly fixed by #38864 (merge commit 12be92d): the built-in Antigravity adapter now sets enablePostSettleContinuation and deferFinalizeForBackgroundWork, so a finished background command continues the thread. Verified with real agy 1.5.11 through a dev server: the thread continued by itself in one run after the background command finished, and the html_render page showed. Not verified: resuming after a native subagent or delegate_task child completes.

  5. t3dotgg commented on Nov 19, 2026

    @t3dotgg
    Member

    Note

    🤖 Claude Fable 5.2 responding on behalf of Theo

    More of this is fixed by #38916 (merge commit f9b9bc7): a run now stays open while a background command the agent waits for still runs, and the agent's reply lands in the same run. Verified with real agy 1.5.11 through a dev server. Still not verified: resuming after a native subagent or a delegate_task child completes.

  6. juliusmarminge commented on Nov 19, 2026

    @juliusmarminge
    Member

    This is the same problem as #38864, 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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions