Antigravity CLI
The Pensyve plugin gives Google Antigravity persistent memory through native rules, reusable skills, and the Pensyve MCP server. Interactive cloud access uses browser OAuth, so you do not need to copy an API key into the plugin.
Install the Plugin
Install from the Pensyve repository:
agy plugin install https://github.com/major7apps/pensyve/tree/main/integrations/antigravity-pluginThe plugin registers https://mcp.pensyve.com/mcp and loads eight focused
memory rules and skills. Restart Antigravity if the newly installed plugin does
not appear immediately.
Authenticate
- Open the
/mcppanel in Antigravity. - Select pensyve, then choose Authenticate.
- Approve the Pensyve consent screen in your browser.
- Return to Antigravity and confirm the server is connected.
Verify the connection with a read-only request such as “Check my Pensyve
status” or “Recall what you know about this project.” Antigravity should call
pensyve_status or pensyve_recall without asking for an API key.
Browser consent is the recommended interactive setup. Pensyve publishes OAuth discovery metadata, supports dynamic client registration, and requires PKCE S256 for the authorization-code flow.
MCP-Only Cloud Setup
If you want the Pensyve server without its bundled rules and skills, register the remote endpoint directly:
agy mcp add pensyve https://mcp.pensyve.com/mcpThen open /mcp and authenticate in the browser as described above.
Local-Only Setup
Install pensyve-mcp, then register its stdio command:
agy mcp add pensyve-local pensyve-mcpIf the installed binary needs the transport selected explicitly:
agy mcp add pensyve-local pensyve-mcp -- --stdioThe local server uses SQLite and ONNX embeddings on your machine. If the plugin
is installed, disable its bundled pensyve cloud entry in /mcp so the agent
does not have two memory servers. Keep only pensyve-local enabled.
API Keys for Automation
Use an API key only when browser consent is unavailable, such as unattended CI.
Create a scoped key in the Pensyve dashboard and add the Authorization: Bearer
header through a user-owned Antigravity configuration. Antigravity's JSON
configuration does not expand environment-variable placeholders, while running
shell expansion before saving a config writes the expanded secret to disk.
Prefer browser OAuth for interactive use and a secret-managed wrapper for
automation; never commit the resulting configuration.
What the Plugin Adds
The plugin organizes memory behavior into eight matching rules and skills:
| Capability | Purpose |
|---|---|
| Recall | Search memory before answering from assumptions |
| Remember | Store durable facts, decisions, and preferences |
| Observe | Capture interaction evidence for later extraction |
| Inspect | Review memories for an entity |
| Forget | Remove memories only with explicit user intent |
| Episodes | Bound related work into start/end sessions |
| Status | Check connection and namespace health |
| Account | Review plan, usage, and quota information |
Rules guide when memory actions are appropriate; skills provide the exact MCP
tool workflow. Every rule carries antigravity-cli provenance.
Migrating from Gemini CLI
Gemini CLI support has been retired. Remove the legacy Gemini extension and any
gemini mcp registration, then install the Antigravity plugin above. The new
plugin uses Antigravity's native rule and skill structure and browser OAuth;
legacy GEMINI.md context files are not required.
For other MCP clients, see Remote MCP. For offline storage and local configuration examples, see Local MCP Setup.
Remote MCP (Cloud)
Set up Codex MCP, OpenCode MCP, GitHub Copilot CLI, Claude Code, and other remote clients with Pensyve Cloud OAuth or API-key authentication.
Claude Code Memory Plugin
Give Claude Code persistent project memory with the Pensyve plugin, including installation, cloud or local setup, automatic capture, and commands.