Consolidate discussion for antigravity (agy) consult issues

[mohidmakhdoomi]

Hi @waleedkadous @amrmelsayed , thought it would be good to create a discussion here to consolidate the current state of agy issues for consult and discuss our findings/concerns. Specifically for the issues related to agy consult timing out, not producing VERDICT, sandbox/permissions, worktree/git, general unreliability.

Note: I am on the latest version of agy cli (1.0.14) as of this post.

Some things to investigate for their impact to agy consult reliability:

• improve fail fast coverage (when agy misbehaves)
• check auth/update agy before spawning consult agy
• use --project CUSTOM_ID and create ~/.gemini/config/projects/CUSTOM_ID.json
  • can generate the json programmatically, allowing for custom deny and allow permissions isolated to the agy instance used for consult
  • see test project json bigtest.json
  • note deny: unsandboxed(*) is a powerful way to prevent bypassing sandbox
  • see https://antigravity.google/docs/cli/permissions
• add more --add-dir args (e.g. output of git rev-parse --git-common-dir)
• for --print arg provide full role text directly appended with a mention to read consult prompt file
  • hope/purpose of this would be more reliable instruction following, as currently for long prompts the entire --print arg is just 2 lines telling agy to read a file (which contains role + prompt)
• use @[./file/path/fname.ext] when referencing files in prompts to agy --print as this it seems to resolve quickly and reliably in my testing
• find and set any useful environment variables before spawning consult agy
• specific/lock model using --model arg (3.1 pro vs 3.5 flash and effort level)

Feel free to add to the list above and share your opinion. Alternatively, while agy cli matures, we can consider disabling gemini/agy for consult and rely on 2 way CMAP.

Current issue list:

• consult: harden agy integration — Gemini lane silently drops out (upstream agy non-TTY stdout bug #76) #1020
• agy/Gemini consult lane goes off-task on structured reviews — emits no VERDICT, breaking the porch consult loop #1032
• porch: a consult that RAN but returned no VERDICT is treated as REQUEST_CHANGES (should be a non-blocking skip) — causes review-loop churn #1033
• Consult: Gemini (agy/Antigravity) reviewer runs in empty sandbox + can execute real commands in the worktree (ran porch done, wrote files) #1051

Relevant PR list:

• Keep agy on-task and stop no-verdict review loops (#1032, #1033) #1085
• [Spec 778] Swap the gemini consult lane to the Antigravity CLI (agy) #988