feat(config): Antigravity as a first-class client for config and Project Skills - #56
Merged
Winlifes merged 3 commits intoSep 7, 2026
Conversation
…ect Skills Antigravity keeps its MCP servers in a single global ~/.gemini/config/mcp_config.json (the alternative, per-plugin plugins/<name>/mcp_config.json, only loads with its plugin, so it is not a place a Unity plugin should be writing to). Its remote-server spec names the endpoint serverUrl, not the url key every other JSON client here uses -- Antigravity's McpServerSpec has no url field at all, so an entry written in the usual shape would sit in the config connecting to nothing. Its documentation calls that field "SSE transport", but the shipped language server registers exactly two connectors -- LocalSubprocessConnector for command and StreamableHTTPConnector for serverUrl -- so the streamable-HTTP endpoint this server exposes is what it actually speaks. MCPConfigTarget gains an UrlFieldName (empty means url) so the endpoint key follows the target instead of being hardcoded. Like Cursor/VS Code/Trae/Kiro, Antigravity has no project-scoping concept in its config, so the entry is global and stays distinguishable only by its per-project name. Antigravity is also wired up as a Project Skills platform: SKILL.md bundles are written to .agents/skills/ at the repository root. Its customization discovery walks from the session's working directory up to the repo root, so in a monorepo layout (git root above the Unity project folder) a .agents inside the Unity folder would only ever be found by a session started at or below it -- the same trap DeepSeek Harness's .dsh/skills placement avoids. It reads AGENTS.md natively, so it joins Codex/OpenCode/DSH on the single shared managed block (written while any of them is enabled, removed only when all are disabled); the block's skills bullet gained the .agents/skills/ entry, with the previous wording kept in the legacy-migration variant list so files already on disk keep migrating instead of erroring. ## Tests New EditMode coverage in ProjectSkillsManagerTests: the legacy-variant chain now recognizes four renderings of the shared AGENTS.md wording (current, pre-Antigravity, pre-DSH, Codex-only) instead of three; Antigravity's skills land at the discovered git root and not inside the Unity project folder; and Antigravity shares the AGENTS.md block with Codex while its own skill directory tracks only its own toggle.
… key RemoveSupersededFunplayEntries decides whether a recorded previous entry is still ours to remove by checking that it points at a loopback URL, but it only ever read that URL under the "url" key. Antigravity's entries carry the endpoint under "serverUrl" instead, so after this project was renamed (or toggled its hash suffix) and reconfigured, its previous Antigravity entry looked hand-edited and was never retired, leaving two funplay entries on the same port in ~/.gemini/config/mcp_config.json. Both IsLoopbackEntry and RemoveSupersededFunplayEntries take an optional urlFieldName that defaults to "url", and the JSON write path threads the target's field name through. CreateHttpEntry gains a static overload taking its inputs directly so the endpoint-key behavior can be tested without constructing an MCPConfigTarget, and GetUrlFieldName centralizes the empty-means-url fallback so every reader and writer of an entry's endpoint resolves the key the same way. ## Tests Two new EditMode tests in MultiEditorPortAndKeyTests: a previous entry written under serverUrl is retired by the rename cleanup exactly like one written under url, and CreateHttpEntry emits the requested key only (an Antigravity-shaped entry carries serverUrl and no url).
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
2 participants
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 one-click Antigravity MCP configuration and Project Skills support. Funplay's Unity endpoint is configured per workspace, so it is not automatically exposed in unrelated Antigravity workspaces.
Configuration and Skills
.agents/mcp_config.jsonwithmcpServersentries usingserverUrl, following the current Antigravity MCP documentation..agents/skills/, andAGENTS.md: the nearest Git ancestor, including worktrees, or the Unity project directory outside Git. The configuration dialog identifies the directory to open in Antigravity.serverUrl.Validation
Unity 2022.3.62f3c1, dedicated FunplayMcp project: 89 EditMode tests passed, 0 failed, 0 skipped across:
git diff --checkpassed. This was a focused regression run, not the full Unity suite. An actual Antigravity client connection was not exercised on this host.