Antigravity Agent terminal commands fail to execute due to missing "Enter" character

Report

1. Description

Agents operating on the Antigravity platform are successfully sending text strings to the background terminal, but the commands are not executing. The text appears in the terminal input line but remains idle.

This issue appears to be caused by the models failing to append a newline/carriage return (↵) at the end of the command string.

2. Steps to Reproduce

  1. Initialize an Agent on Antigravity using a Gemini model.
  2. Give the Agent a prompt that requires executing a shell command (e.g., ls -la or pip install package).
  3. Open the background terminal view.
  4. Observe that the command text appears in the terminal but does not run.

3. Expected vs. Actual Behavior

  • Expected Behavior: The agent sends the command string followed by an execution character (Enter/\n), causing the terminal to run the command immediately.
  • Actual Behavior: The command string is typed into the terminal but hangs indefinitely without execution.

4. Investigation & Workaround

Root Cause Observation:
The issue stems from the model not implicitly including the “Enter” keystroke or newline character at the end of the generation.

Temporary Workaround:
Explicitly instructing (“threatening”) the model within the prompt to use the Enter character (↵) resolves the issue. When forced to include this character, the command executes successfully.
For those facing this issue still, telling the agent to use ‘↵’ at the end will work.

6. Attachments

  • Screenshot 1: Shows the command text sitting idle in the terminal (Bugged state).


Suggested Fix for Devs

Please investigate the command transmission logic or the default system prompt. Ensure that a newline character (\n) or carriage return (\r) is automatically appended to any code block or string sent to the terminal interface, regardless of whether the model generates it.

this must be fixed asap. completely broken.