Skip to content

fix(cli): wire --antigravity and remove broken --universal in setup#2700

Open
fahreddinozcan wants to merge 2 commits into
masterfrom
ctx7-1677-add-antigravity-setup
Open

fix(cli): wire --antigravity and remove broken --universal in setup#2700
fahreddinozcan wants to merge 2 commits into
masterfrom
ctx7-1677-add-antigravity-setup

Conversation

@fahreddinozcan
Copy link
Copy Markdown
Contributor

@fahreddinozcan fahreddinozcan commented Jun 1, 2026

Summary

ctx7 setup advertised --universal and --antigravity but neither was wired through getSelectedAgents. Passing them silently fell back to auto-detection and wrote to the wrong directory (#2695).

  • Removes --universal from setup entirely.
  • Wires --antigravity through and adds an Antigravity SetupAgent config, with paths verified against Google's Codelabs and Google Cloud Community:
    • MCP: global only at ~/.gemini/config/mcp_config.json (the Antigravity 2.0 shared location). No documented project-level MCP — setupAgent / uninstallMcp fall back to globalPaths when projectPaths is empty, so --project --mcp --antigravity still writes to the right place.
    • HTTP key: httpUrl (Gemini-family convention).
    • Rule: append to GEMINI.md / ~/.gemini/GEMINI.md, since Antigravity is Gemini-based.
    • Skill: .agent/skills, matching the in-repo IDE_PATHS convention used by ctx7 skill / ctx7 generate.

Fixes #2695.

Test plan

  • npx tsc --noEmit clean
  • npx vitest run — 207/207 pass (incl. updated ALL_AGENT_NAMES order, httpUrl for antigravity, and remove tests covering the empty-projectPaths fallback)
  • npx eslint clean on changed files
  • Manual: ctx7 setup --cli --antigravity --project writes to ./.agent/skills/find-docs/
  • Manual: ctx7 setup --mcp --antigravity writes to ~/.gemini/config/mcp_config.json with httpUrl
  • Manual: ctx7 setup --universal … is now rejected as unknown option

The setup command advertised --universal and --antigravity flags but
neither was wired through getSelectedAgents, so passing them silently
fell back to auto-detection and wrote to the wrong directory (see #2695).

Remove --universal from setup entirely, and add a full Antigravity
SetupAgent config: skills under .agent/skills, MCP config at
~/.gemini/antigravity/mcp_config.json with serverUrl for HTTP, and
detection of .agent or ~/.gemini/antigravity.
@linear-code
Copy link
Copy Markdown

linear-code Bot commented Jun 1, 2026

CTX7-1677

After verifying against Google Codelabs / Google Cloud Community
docs, correct the Antigravity config:

- MCP global path: ~/.gemini/config/mcp_config.json (Antigravity 2.0
  shared config, replacing the older ~/.gemini/antigravity/ path
  which an outdated github/github-mcp-server install guide cited).
- HTTP key: httpUrl (Gemini convention; antigravity is Gemini-based).
  The previous serverUrl was sourced from the same outdated guide.
- Rule: append to GEMINI.md / ~/.gemini/GEMINI.md (Antigravity reads
  Gemini-family rules, not a vendor-specific file).
- Project MCP: none documented; projectPaths is empty and setupAgent
  / remove falls back to globalPaths so --project --mcp still writes
  to the correct location.

Skills stay at .agent/skills to keep the in-repo IDE_PATHS convention
consistent across setup, skill, and generate commands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: setup --cli --universal --project silently ignores --universal` and installs to auto-detected agent dir

2 participants