Stop detecting Antigravity from the shared .agents directory that Boost itself creates for other agents' skills - #981
Open
sulimanbenhalim wants to merge 1 commit into
Conversation
…st itself creates for other agents' skills
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.
boost:install thinks Antigravity is in the project for anyone who installed skills for Amp, Codex, OpenCode or Zed. those four all default their skills path to .agents/skills, so installing skills for any of them creates .agents/, and Antigravity's project detection matches on the bare .agents directory. same false positive class as #831/#832.
fix drops the paths entry and detects on .agents/mcp_config.json only, which is the file Antigravity actually writes.
repro on a real app: with only .agents/skills present, detectInProject returns true on main and false with this change, and a real .agents/mcp_config.json still detects.
re-file of #966, reviewed and re-tested individually.