Skip to content

feat(plugin): Add Antigravity CLI and IDE plugin packaging - #15

Open
harveyfullstack wants to merge 8 commits into
mainfrom
feat/antigravity-plugin
Open

feat(plugin): Add Antigravity CLI and IDE plugin packaging#15
harveyfullstack wants to merge 8 commits into
mainfrom
feat/antigravity-plugin

Conversation

@harveyfullstack

@harveyfullstackharveyfullstack commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

What changed

People can install Hamster in Antigravity (agy) and get the same hosted Hamster workspace connection as Claude Code, Cursor, and Codex (#13). Skills show up as ask, ship, plan, and the rest.

Why it matters

Those other hosts already have a Hamster plugin. Antigravity did not.

How it works

This repo is packaged as an Agent Plugin, the shared plugin format Cursor already documents and that Google is adopting for Antigravity. That is why install is the repository URL, the same shape other public plugins use, not a one-off copy of files.

No credentials are bundled. The first time the Hamster connection is used, Antigravity asks the person to sign in. Cursor's existing marketplace packaging is unchanged.

User impact

agy plugin install https://github.com/gethamster/cli

/mcp lists hamster. Sign in from Antigravity IDE Customizations if asked. Claude Code, Cursor, and Codex install paths are unchanged.

Validation

Local install registered hamster. /mcp reached the Hamster server and asked for sign-in. /skills listed the usual Hamster skills.

Native plugin at .agents/plugins/hamster with plugin.json, mcp_config.json (serverUrl), and copied skills/agents. README documents agy plugin install and IDE drop paths.
Native plugin.json rejects extra properties; drop $schema so the manifest matches the host contract.
agy keys plugin skills by frontmatter name, so the copies need ask/plan/qa/resume/retro/review/ship without editing repo-root skills. README now matches where install actually writes and how /mcp auth works.
Match Compound Engineering: one skills/agents tree, plugin dir links at it. agy plugin install still stages a real copy. Root plugin.json stays out so Cursor does not treat this repo as an Agent Plugin.
Root plugin.json uses the Agent Plugins schema so agy plugin install works on the GitHub URL without a clone. mcp.json is for Agent Plugin clients; mcp_config.json is what live agy reads. Cursor marketplace stays in .cursor-plugin.
@harveyfullstack
harveyfullstack marked this pull request as ready for review August 26, 2026 16:50
Sign up for freeto 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.

2 participants

@harveyfullstack@maxtuzz