Antigravity CLI 1.1.5 on Windows receives empty prompts in Open Design 0.15.1 (-p - incompatibility)

[oriancm]

Title

Antigravity CLI 1.1.5 on Windows ignores prompts in Open Design 0.15.1 (-p - incompatibility)

Hi everyone,

I encountered an issue using Antigravity with Open Design on Windows.

Environment

• Windows 11
• Open Design 0.15.1
• Antigravity CLI 1.1.5

Symptoms

Open Design correctly detected the Antigravity CLI and the connection test succeeded.

However, every prompt sent from Open Design was ignored. Instead of answering the actual request, Antigravity returned a generic greeting or behaved as if no prompt had been provided.

Root cause

Open Design launches Antigravity using:

agy -p -

and then writes the actual prompt to stdin.

With Antigravity CLI 1.1.5, supplying -p means the CLI no longer reads the prompt from stdin. As a result, the literal string "-" is treated as the prompt and the data written to stdin is ignored.

Workaround / Fix

Removing:

args.push("-p");
args.push("-");

while keeping stdin enabled (promptViaStdin: true) immediately fixed the issue.

After this change, Open Design correctly sends prompts to Antigravity and everything works as expected.

This appears to match the fix proposed in PR #5585 and confirms that it resolves the issue on Windows with Antigravity CLI 1.1.5.

[roian6]

Thanks for the detailed Windows repro. I checked the current main adapter, and it still invokes Antigravity with the legacy -p - argument while piping the prompt through stdin, so this fix has not landed yet.

Your diagnosis lines up with #5495. PR #5585 has been approved and QA-accepted, but it is still open and currently conflicts with main; #6060 is another open, mergeable implementation awaiting review and validation.

The agy 1.1.5 Windows evidence is especially useful because it confirms the changed 1.1.x flag behavior against a current upstream version. Until one of these fixes lands in a release, affected Open Design builds can still reproduce the empty-prompt behavior.

[devadeboye]

I'm experiencing the same issue on mac os.