[Antigravity IDE / Agent Execution] Unable to cancel/interrupt ongoing agent execution ("Executor has not processed the previous input yet")

Google Antigravity
1

Environment & Context

  • Platform/Tool: Antigravity IDE (Agent Chat Interface)

  • Model Used: Gemini 3.6 Flash (High)

  • OS / Browser: CachyOS

Description

When the agent is executing a terminal/tool command (e.g., writing/running scripts), there is no intuitive way or functional “Stop/Cancel” button to interrupt the process.

If a new prompt (like “please stop previous process”) is sent while the previous tool step is still running, the UI gets blocked with the message:

Executor has not processed the previous input yet

This creates a soft-lock state where the user cannot interrupt a long-running/stuck execution and cannot send new commands until the executor finishes or times out.

Steps to Reproduce

  1. Initiate a prompt that triggers the agent to run a shell/tool command (e.g., running cat << 'EOF' > ... or long-running script).

  2. While the agent status shows “Worked for XXs” and is actively running a tool call, send a new text prompt to stop or redirect the agent.

  3. Observe the input area.

Expected Behavior

  • An explicit “Stop / Cancel” button should be available to interrupt ongoing agent tool executions immediately.

  • Sending a new message should either cleanly append to the queue or prompt the user to cancel the ongoing execution.

Actual Behavior

  • The user prompt is held in a pending state with the warning Executor has not processed the previous input yet.

  • The user is unable to abort the stuck or unwanted process manually.

Attachment

image
image1160×1303 68.7 KB

2

Hello @Ihza_Fikri_Zaki_Karu.

  • Since manual interrupts are failing to propagate, please fully close and restart the Antigravity desktop application to forcefully kill the active process tree and release the executor lock.
  • If the agent remains stuck, wait for the default 30-second timeout window to expire, or if you have custom hooks defined in hooks.json, wait for those specific thresholds.
  • If the problem persists, purge the corrupted local trajectory state by deleting the .antigravity/ cache directory in your project root (or ~/.config/antigravity and ~/.cache/antigravity on Linux).
  • Try disabling all MCP servers in the Antigravity settings to rule out tool conflicts, re-enabling them one by one to isolate the cause.

Finally, ensure you are running the latest versions: Antigravity 2.0 (2.7.1), Antigravity IDE (2.1.1), and Antigravity CLI (1.1.12)