Skip to content

Antigravity: t3_background_wait always fails with "This provider cannot mark background work as awaited" #39411

Closed

Description

@juliusmarminge

What users report

From feedback on the Antigravity integration (post):

t3_background_wait don't work at all with antigravity

Reproduced

main @ 6b6950adfe2, Linux x86_64, agy CLI 1.5.12, model gemini-3.8-flash (effort low), isolated vp run dev state.

  1. Start an Antigravity thread:
    node apps/server/src/bin.ts thread start --provider antigravity --model gemini-3.8-flash --option effort=low --wait <project> 'Start the shell command \sleep 15 && echo finished` in the background. Then call the T3 MCP tool t3_background_wait with that background task id. Report the exact result or error text the t3_background_wait tool returned, verbatim, then report the command output once it finishes.'`
  2. The tool call fails every time:
    Encountered error in tool execution: {"_tag":"OrchestratorMcpFailure","code":"invalid_request","message":"This provider cannot mark background work as awaited."}
    
  3. Antigravity's own background tracking still kept the turn open until the command finished (output finished was reported), so the call is pure noise: a guaranteed error the agent sees, and users read as "doesn't work".

Cause

  • t3_background_wait is exposed to every provider (apps/server/src/mcp/toolkits/orchestrator/tools.ts, BackgroundWaitTool); its description says "Claude/OpenCode only" but nothing filters it per provider.
  • ThreadManagementService.awaitBackgroundTasks (apps/server/src/orchestration-v2/ThreadManagementService.ts) returns reason: "unsupported" when the runtime has no awaitBackgroundTasks. Only the Claude and OpenCode adapters implement it; the ACP adapter used by Antigravity does not.

Fixed looks like

An Antigravity agent never gets an error from t3_background_wait. Either:

Pick the smaller of the two. A test should cover the Antigravity path. If the tool stays exposed, keep its description accurate.

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