> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sovseal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Antigravity Persistent Memory

> Integrate local-first, zero-knowledge memory with Google Antigravity IDE using the sovseal MCP server.

Give **Google Antigravity** a persistent, local-only memory layer across projects and sessions. Every conversation starts with full context of your architecture decisions, stack preferences, and coding conventions.

<Info>
  Google Antigravity supports MCP servers natively via its settings UI or project-level configuration. No signup or cloud dependencies are required for the local memory tier.
</Info>

## Installation

### Option 1: Settings UI

1. Open the **Antigravity** settings panel (gear icon).
2. Navigate to **MCP Servers** (or **Extensions → MCP**).
3. Click **+ Add MCP Server**.
4. Configure with **Name** `sovseal-memory`, **Transport** `stdio`, **Command** `npx`, **Args** `-y @sovseal/mcp-server`.
5. Save and restart.

### Option 2: Project Configuration

Add to your project's `.gemini/settings.json` (or create it):

```json theme={null}
{
  "mcpServers": {
    "sovseal-memory": {
      "command": "npx",
      "args": ["-y", "@sovseal/mcp-server"]
    }
  }
}
```

***

## Directing Antigravity with Rules

Google Antigravity loads workspace rules from `.agents/rules/` (or `.agent/rules/`) markdown files. To ensure the agent proactively uses your memory, create `.agents/rules/sovseal-memory.md`:

```markdown theme={null}
# sovseal persistent memory rules

## Memory Protocol

Always invoke the `recall_memory` tool as your first action on any new user
request to retrieve historical context, past code decisions, and user stack
preferences.

When the user shares a persistent stack choice, API change, or file path
decision, greedily call `store_memory` to persist it for future sessions.
```

<Tip>
  You can auto-generate this file by running `npx @sovseal/mcp-server onboard --write`. The `onboard` command detects your IDE and writes the correct rules file automatically.
</Tip>

For rules that apply across all projects, append the same memory protocol to your global config at `~/.gemini/GEMINI.md`.

***

## Project-Scoped vs. Global Memory

By default, sovseal stores memories globally in `~/.sovseal/db/memories.lance`. To scope memories to the current project (preventing cross-project context bleed), set the `SOVSEAL_DB_DIR` environment variable:

```json theme={null}
{
  "mcpServers": {
    "sovseal-memory": {
      "command": "npx",
      "args": ["-y", "@sovseal/mcp-server"],
      "env": { "SOVSEAL_DB_DIR": "./.sovseal/db" }
    }
  }
}
```

***

## Troubleshooting

### Tools Not Appearing

* **Check node version:** Antigravity spawns MCP servers as child processes. Ensure `node -v` reports `>= 20.0.0`.
* **First-run warmup:** On the first invocation, the ONNX embedding model (\~22 MB) downloads to `~/.sovseal/models/`. Tools may appear as "Connecting…" for 15–30 seconds.

### Memory Not Persisting

* Verify the rules file exists at `.agents/rules/sovseal-memory.md` (or `.agent/rules/sovseal-memory.md`).
* Check that the rules contain the `recall_memory` and `store_memory` instructions.
* Run `npx @sovseal/mcp-server mind` to inspect what the local memory node currently holds.