Repository navigation
Fix the antigravity leg, which never received the prompt - #50
Merged
Merged
Conversation
`-p -` does not read stdin. Antigravity takes the literal `-` as the prompt and answers "Hello! How can I help you today?", so every panel has been silently losing that agent's review. It now joins vibe and grok in reads_stdin() and gets the prompt as `-p`'s value instead. Verified with a 6KB multiline prompt: safe as an argv operand here because gg ships antigravity as a native binary, not a .cmd shim. Switch the gg tool from the raw gh/google-antigravity/antigravity-cli release path to the registry tool that landed in gg 199, and bundle gg 199 so it resolves. The name is `antigravity-cli` and not `antigravity` on purpose: gg caches it under the repo name whatever alias you run, and `gg update` looks it up by cache name, so `update antigravity` silently finds nothing. That is a gg bug, fixed upstream but not released yet. Until this change the update leg never worked either, since the raw gh/... path was no more resolvable. Also accept `agy` in from_name, matching gg's own alias list.
eirikb
added a commit
that referenced
this pull request
Aug 20, 2026
…all (#51) Antigravity ignores the process cwd. Print mode opens no workspace at all and works out of ~/.gemini/antigravity-cli/scratch instead, so the leg reviewed an empty dir - one run went looking for the repo with `find $HOME -maxdepth 3`. It takes the workspace as `--add-dir`, which `command` appends since it is the one that knows the repo. OsString and not String: a repo path need not be UTF-8, and to_string_lossy() hands antigravity a U+FFFD path that opens nothing. Headless print mode soft-denies every tool that needs approval (since 1.1.3), which under the stock `toolPermission: request-review` is every shell command. Bare `-p` then exits 1 with "permission check failed", and under `--sandbox` it exits 0 having printed nothing at all - so since #50 made the prompt actually arrive, the leg has been trying to work and dying. `--dangerously-skip-permissions` clears the deny and `--mode plan` is what holds the tree: it refused both a straight "overwrite this file, do not plan" and the same thing routed through the terminal. Not `--disable-slash-commands`, though it fixes prompts that open with `/`: plan mode is built on that same expansion and the flag silently voids it, leaving skip-permissions on with nothing holding the tree. Plan mode is also told by its own system prompt to put the findings in an artifact file and not repeat them in the reply, so stdout came back as "I have created a plan, please review it" with the review itself in a brain dir nothing reads. decorate_prompt appends a coda for that leg only, asking for the answer in the reply and for the workspace to be left alone. Read-only there is a persona and not a sandbox, unlike every other leg, so stop claiming otherwise in agents.rs, README and SKILL.md, and check it instead: `git status --porcelain` before and after the fan-out, with a run note naming antigravity if the tree moved. Note an Ok leg that returned under 300 characters too - a placeholder answer used to render as an ordinary section, and the caller read a silent leg as one with nothing to add.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
-p -does not read stdin. Antigravity takes the literal-as the prompt and answers "Hello! How can I help you today?", so every panel has been silently losing that agent's review. It now joins vibe and grok inreads_stdin()and gets the prompt as-p's value instead. Verified with a 6KB multiline prompt: safe as an argv operand here because gg ships antigravity as a native binary, not a .cmd shim.Switch the gg tool from the raw
gh/google-antigravity/antigravity-clirelease path to the registry tool that landed in gg 199, and bundle gg 199 so it resolves. The name isantigravity-cliand notantigravityon purpose: gg caches it under the repo name whatever alias you run, andgg updatelooks it up by cache name, soupdate antigravitysilently finds nothing. That is a gg bug, fixed upstream but not released yet. Until this change the update leg never worked either, since the rawgh/...path was no more resolvable.Also accept
agyinfrom_name, matching gg's own alias list.