Skip to content

feat(agent-plugins): install global plugins for Antigravity CLI and Goose - #349

Closed
fnzko wants to merge 13 commits into
symposium-dev:mainfrom
fnzko:agent-plugins-antigravity-goose
Closed

fnzko wants to merge 13 commits into
symposium-dev:mainfrom
fnzko:agent-plugins-antigravity-goose

Conversation

@fnzko

@fnzko fnzko commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do?

Part of #277.
Depends on #332 (until it merges, only the last 3 commits are new here).

A plugin enabled with cargo agents use --global still reached Antigravity CLI and Goose only as per-project copies of its skills, although both load plugin directories from a folder of their own.

Antigravity CLI now gets a copy of the compiled plugin in ~/.gemini/config/plugins/<plugin>/ and Goose in ~/.agents/plugins/<plugin>/ (or $GOOSE_PATH_ROOT/.agents/plugins/<plugin>/), with Claude Code's copy routine and its rule for a directory symposium does not own. Both load it in every project, Goose under the skills' own names. Symposium writes none of their settings.

Verified with Antigravity CLI 1.2.14 and Goose 1.53.0 through cargo agents sync, by asking each agent what it loaded.

Take into account:

  • Antigravity offers a plugin installed by the session-start sync after /skills reload or in the next session; Goose from the next message.
  • With Claude Code also configured, Goose loads the same skills from Claude Code's copy in ~/.claude/skills/, so turning the plugin off in Goose has no effect.
Disclosure questions

AI disclosure.

  • The AI tool authored large parts of the code

@fnzko

fnzko commented Oct 20, 2026

Copy link
Copy Markdown
Contributor Author

Folded into #332.

@fnzko fnzko closed this Oct 20, 2026
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.

1 participant