Windows/Codex: agy --print exits 0 but produces empty stdout in non-interactive shell

[dimakor]

Summary

When agy is launched from OpenAI Codex on Windows in non-interactive print mode, it exits successfully but produces empty stdout. The same command prints the expected response when run manually from an interactive PowerShell session.

This makes Codex plugins/wrappers that rely on agy --print unable to consume Antigravity responses without reading Antigravity internal transcript files, which is not a good integration boundary.

Environment

• OS: Windows
• Shell: PowerShell
• Antigravity CLI: agy 1.0.8
• Caller: OpenAI Codex desktop/tool shell, non-interactive process execution
• Auth: agy is authenticated and works interactively

Reproduction

From an interactive PowerShell terminal:

agy -p "Say hello" --print-timeout 1m

Expected and observed: response is printed to stdout.

From Codex/non-interactive PowerShell execution:

agy -p "Say hello" --print-timeout 1m

Observed:

• exit code: 0
• captured stdout: empty
• captured stderr: empty or no actionable error
• Antigravity still appears to create internal transcript/log files containing the model response

Expected behavior

agy --print should write the final model response to stdout consistently when launched from non-interactive processes on Windows, as long as authentication succeeds and the command exits with code 0.