# HarnessLink for Cursor

Cursor support is partial. You can register HarnessLink's MCP server in Cursor by hand, so its model can search and read the memory your other harnesses bank, and HarnessLink syncs `~/.cursor/sessions/*.jsonl` and `~/.cursorrules`. Cursor's chats live in an editor database HarnessLink does not read, so they are not captured or banked.

## What HarnessLink captures from Cursor

| Feature | In Cursor | Details |
| --- | --- | --- |
| Prompt history | No | Not captured: Cursor keeps chats in an editor database HarnessLink does not read. |
| Session transcripts | Partly | `~/.cursor/sessions/*.jsonl` only. |
| Memory bank (autobank) | No | Not supported. |
| Gateway routing | No | Not routed. |
| Context hooks | No | Not available. |
| Memory tools (MCP) | Partly | `mcpServers.superpi` in `~/.cursor/mcp.json`, registered by hand; setup does not do it for you. |
| Org policy rules | No | Not enforced: there is no tool hook. |
| Skills from templates | Yes | `hnl add <skill>` installs into `~/.cursor/skills`; Cursor also reads `~/.agents/skills`, `~/.claude/skills` and `~/.codex/skills`. |
| Resume in another harness | No | `hnl resume` does not offer Cursor sessions. |

## Set up Cursor

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. Register the MCP memory tools in Cursor yourself; setup does not.
   ```
   hnl mcp register --harness=cursor --yes
   ```
4. Sync Cursor's session files and `~/.cursorrules` if setup did not turn that on.
   ```
   hnl cloud harnesses enable cursor
   ```

## How memory reaches Cursor

**Through the memory tools**, once registered. The MCP server is the HarnessLink service's own (`superpi mcp`). Its tools include `memory_search` (search your memory across projects and machines), `memory_get` (read one entry in full), `memory_bank` (record a decision or outcome), `context_brief` (a budgeted brief of the project), `session_list` and `session_get`.

Nothing is added to a Cursor chat on its own: Cursor has no hooks HarnessLink can use, so the model reaches memory only when it calls a tool.

## Limits

- Cursor prompts and chats are not captured or banked.
- No gateway routing, context hooks or org policy rules.

## 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.
- [Installing HarnessLink](https://harnesslink.sh/docs/install): The full HarnessLink install guide: requirements, Windows, install options, verifying, the first-run onboarding, updating, troubleshooting and uninstalling.
- [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
- [Antigravity](https://harnesslink.sh/harnesses/antigravity): Transcripts and one memory entry per conversation

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