# HarnessLink for Antigravity

HarnessLink reads what the Antigravity CLI (`agy`) writes: your prompts, each conversation's transcript and its summary, banked as one memory entry per conversation. Antigravity's model traffic goes straight to Google and it has no hooks or MCP preset, so HarnessLink does not route or add to its sessions.

## What HarnessLink captures from Antigravity

| Feature | In Antigravity | Details |
| --- | --- | --- |
| Prompt history | Yes | `~/.gemini/antigravity-cli/history.jsonl`. |
| Session transcripts | Yes | `~/.gemini/antigravity-cli/brain/<conversation>/.system_generated/logs/transcript_full.jsonl`, uploaded moments after it changes. Sub-agent conversations stay out. |
| Memory bank (autobank) | Partly | One entry per conversation, from Antigravity's conversation summaries, not one per turn. |
| Gateway routing | No | Not supported: signed-in traffic goes directly to Google. |
| Context hooks | No | Not available. |
| Memory tools (MCP) | No | There is no MCP preset for Antigravity. |
| Org policy rules | No | Not enforced: there is no documented tool hook. |
| Skills from templates | Yes | `hnl add <skill>` installs into `~/.gemini/antigravity-cli/skills`. |
| Resume in another harness | No | `hnl resume` does not offer Antigravity sessions. |

## Set up Antigravity

1. Install HarnessLink on macOS or Linux ([Windows](https://harnesslink.sh/docs#windows) has its own one-liner).
   ```
   curl -fsSL https://harnesslink.sh/install.sh | bash
   ```
2. Sign in once in your browser; setup then turns on what each harness on the machine supports.
   ```
   hnl cloud setup
   ```
3. Or turn the pieces on one at a time.
   ```
   hnl cloud harnesses enable antigravity
   hnl cloud autobank enable antigravity
   ```
4. Check what is connected: plain `hnl` shows, for each harness, the gateway, transcripts, autobank, context and memory tools.
   ```
   hnl
   ```

## How memory reaches Antigravity

HarnessLink does not add memory to an Antigravity session: there are no hooks or MCP preset to do it with.

Each conversation is banked as one entry, so Claude Code, Codex and omp can find what you did in Antigravity, and the dashboard shows the conversation as turns: your words, its thinking, each tool call and the answer.

## Limits

- No gateway routing, so no usage records, model rules or usage limits for Antigravity.
- No context hooks, MCP memory tools or org policy rules.
- Autobank writes one entry per conversation, not one per turn.

## Guides

- [Using HarnessLink](https://harnesslink.sh/docs/usage): Using HarnessLink day to day: Ask, history, policies, shared memory, resuming sessions across harnesses, profile sync, templates, delegation, runs and cost.
- [Memory Banking](https://harnesslink.sh/docs/memory-banking): How HarnessLink turns each finished turn in omp, Claude Code, Codex, pi and Antigravity into a Markdown memory entry, when banking runs, and what reads it.
- [What HarnessLink captures from each harness](https://harnesslink.sh/docs/multi-harness): What HarnessLink captures from omp, Claude Code, Codex, pi, Antigravity and Cursor after setup, and how it stays a controller rather than a harness.

## Other harnesses

- [Claude Code](https://harnesslink.sh/harnesses/claude-code): Hooks, MCP memory tools, gateway and autobank
- [Codex](https://harnesslink.sh/harnesses/codex): Hooks, MCP memory tools, gateway and autobank
- [omp](https://harnesslink.sh/harnesses/omp): Context extension, MCP memory tools, gateway and autobank
- [pi](https://harnesslink.sh/harnesses/pi): Transcripts, autobank and gateway
- [Cursor](https://harnesslink.sh/harnesses/cursor): MCP memory tools, by hand; chats not captured

[All harnesses](https://harnesslink.sh/harnesses) · [Install guide](https://harnesslink.sh/docs) · [Pricing](https://harnesslink.sh/pricing) · [Integrations](https://harnesslink.sh/integrations)