Repository navigation
Add Antigravity CLI support - #24
Merged
Merged
Conversation
init adds a canaryhook entry to .agents/hooks.json with PreToolUse and SessionStart. Tool arguments are mapped to the names the checks use, a pass answers allow (which defers to the user's rules), and the output check is reported as not supported since the payload carries no output.
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
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.
Adds an Antigravity CLI adapter (the Gemini CLI successor). init adds a
canaryhookentry to.agents/hooks.jsonwithPreToolUseandSessionStart, keeping other entries.toolCall.argsare mapped to the names the checks use (CommandLinetocommand,AbsolutePath/TargetFiletofile_path,CodeContenttocontent), so globs and tamper work the same. Every PreToolUse answer carries a decision:allowon a pass (which defers to the user's own permission rules, not auto-approve),denywith a reason on a trip. PostToolUse payloads carry no tool output, so the output check is not registered; status shows it as "not supported" and stays healthy. Backlog task-5.