gemini-cli - 💡(How to fix) Fix AGY 1.0.2: -p/--print mode outputs nothing to stdout on Windows

Description

The -p / --print flag for headless/non-interactive mode does not output anything to stdout on Windows, even though the API call succeeds and generates a response.

Environment

• OS: Windows 11
• AGY Version: 1.0.2
• Installation: irm https://antigravity.google/cli/install.ps1 | iex
• Path: C:\Users\<user>\AppData\Local\agy\bin\agy.exe

Expected Behavior

agy -p "Say OK"
# Expected output: OK

Actual Behavior

agy -p "Say OK"
# Actual output: (nothing)

Evidence from Logs

When running with --log-file, the logs clearly show the response is generated:

I0526 22:47:32.511998 http_helpers.go:182] URL: https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse
I0526 22:47:32.572962 text_drip.go:173] Drip stopped: lastStepIdx=2, charIdx=2, length=2

The length=2 confirms the response "OK" (2 characters) was generated, but it never appears in stdout.

Steps to Reproduce

1. Install AGY on Windows: irm https://antigravity.google/cli/install.ps1 | iex
2. Authenticate: agy (complete OAuth flow)
3. Run in print mode:

   & 'C:\Users\<user>\AppData\Local\agy\bin\agy.exe' -p 'Say OK' --log-file='test.log'

4. Observe: stdout is empty, but test.log shows Drip stopped: length=2

Workaround

Use Gemini CLI (gemini -p "prompt") which works correctly on Windows.

Probable Cause

The text_drip.go component seems to not handle non-TTY stdout correctly on Windows. The drip rendering works for TUI but doesn't flush to stdout in headless mode.

Impact

Cannot use AGY in:

• CI/CD pipelines
• Shell scripts with pipe/redirect
• Any automation requiring stdout capture

Reported from YAKKI project testing