Skip to content

[Bug]: Antigravity /swarm turn completes while the swarm is still running, so the coordinator's report never arrives #36475

Closed as duplicate

Description

@samwang0041-star

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. Antigravity provider configured through Binary path with agy 1.5.7 (agy acp), model gemini-4-carbon (Carbon 4 High), macOS.
  2. In an Antigravity thread, send /swarm <task> as plain text (/swarm is not in the composer's command list, so it goes out as an ordinary prompt and agy expands it).
  3. Let the coordinator post its kickoff message and start its workers.
  4. Wait for the swarm to finish without touching the thread.

Expected behavior

The coordinator's completion report is delivered as a continuation of the same thread. While the swarm runs, the thread should not look finished with no way to tell that work is still in flight.

Actual behavior

The session/prompt for /swarm resolves about ten minutes in, while the coordinator has only briefed the workers. T3 settles that run as completed. The swarm keeps running inside agy — its board keeps advancing — but nothing reopens the thread: no session/update, no continuation prompt, no error, no notice. The final report is never delivered.

From statev2.sqlite, the run that started the swarm:

ordinal  status     requested_at              completed_at
26       completed  2026-11-13T23:50:13.652Z   2026-11-14T00:00:34.282Z

The only assistant text in that turn is the kickoff message naming the eight members it had just started. The next run begins only because the user types /swarm board at 00:47:37; that reply reports three workers recovered after a service restart, and it is the first content of any kind since the kickoff. In a second thread with the same setup, the complete report appeared only after the user sent an unrelated report progress message, which started run 132 (requested_at 00:32:07, completed_at 00:50:25).

Mechanism as far as I can trace it on main:

  • makeAntigravityAcpAdapterFlavor in apps/server/src/orchestration-v2/Adapters/AntigravityAdapterV2.ts forwards continuationRequests and sets promptInactivityTimeout: "15 minutes", but does not opt into deferFinalizeForBackgroundWork or enablePostSettleContinuation (the same gap as [Bug]: Antigravity does not resume turns on subagent/background task completion #30082, proposed fix in fix(server): harden Antigravity continuation and checkpoint recovery #30083). Once the coordinator ends its turn, the run settles while the swarm is still working.
  • Swarm workers post to Antigravity's own board rather than emitting ACP subagent tool calls, so extractAntigravitySubagentUpdate does not see them. Nothing carries their progress or the coordinator's later report into T3.
  • /swarm board is likewise sent as a normal prompt and cannot open the native board from T3, so the only visible signal left is whatever the coordinator chooses to write in a turn the client has to start itself.

Impact

Major degradation or frequent failure

Version or commit

T3 Code (Nightly) 0.1.10-nightly.20261113.4656 (0517d15)

Environment

macOS 26 (darwin-arm64), built-in Antigravity provider (oauth-personal), Antigravity CLI 1.5.7 through Binary path, coordinator gemini-4-carbon (Carbon 4 High). /swarm is the CLI 1.5.5 preview.

Logs or stack traces

No provider error is logged for the swarm turn; there is no failed request to report. The run row above is the whole record of the turn.

Screenshots, recordings, or supporting files

No response

Workaround

Send any message to the thread after the swarm finishes (for example report progress). That starts a new turn and the coordinator reports the full result there. Progress requires polling with /swarm board as a prompt.

Related issues

Activity

  1. juliusmarminge commented on Nov 14, 2026

    @juliusmarminge
    Member

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