What HarnessLink captures from omp

Feature	In omp	Details
Prompt history	Yes	`~/.omp/agent/history.db`.
Session transcripts	Yes	`~/.omp/agent/sessions/<folder>/*.jsonl`, subagents included, uploaded moments after they change.
Memory bank (autobank)	Yes	Every finished turn becomes a memory entry, plus todo, plan and checkpoint snapshots.
Gateway routing	Yes	`providers.anthropic.baseUrl` and `providers.openai-codex.baseUrl` in `~/.omp/agent/models.yml`.
Context hooks	Yes	A managed extension, `~/.omp/agent/extensions/superpi-context.ts`, since omp has no settings-file hooks.
Memory tools (MCP)	Yes	`mcpServers.superpi` in `~/.omp/agent/mcp.json`.
Org policy rules	Yes	Checked in the extension's `tool_call` handler; "ask first" opens a confirm dialog.
Skills from templates	Yes	`hnl add <skill>` installs into `~/.omp/agent/skills`; agents and extensions install for omp only.
Resume in another harness	Yes	`hnl resume` reopens a session with `omp --resume`.

Set up omp

Install HarnessLink. The installer also installs omp (@oh-my-pi/pi-coding-agent) unless you pass --no-omp.
```
curl -fsSL https://harnesslink.sh/install.sh | bash
```
Sign in once in your browser; setup then turns on what each harness on the machine supports.
```
hnl cloud setup
```

Or turn the pieces on one at a time.

hnl gateway connect omp
hnl cloud harnesses enable omp
hnl cloud autobank enable omp
hnl harness context omp
hnl mcp register --harness=omp --yes

Check what is connected: plain hnl shows, for each harness, the gateway, transcripts, autobank, context and memory tools.
```
hnl
```

How memory reaches omp

At session start the extension's before_agent_start handler adds your organisation's policy instructions and a brief of the project, up to 9,500 characters.

On each prompt it adds up to 3 memory entries that share at least two distinctive words with your prompt, from any harness.

The hooks read files on the machine only (the local memory index and MAIN.md); they never call the cloud, so they stay fast and work offline.

When the model needs more it calls the memory tools. 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.

Near the context limit the extension tells you to start a new session with /new, and saves a handoff before omp compacts.

Limits

Org model rules and usage limits apply to omp's Anthropic and OpenAI Codex providers, the two the gateway routes.

Guides

Installing HarnessLink: The full HarnessLink install guide: requirements, Windows, install options, verifying, the first-run onboarding, updating, troubleshooting and uninstalling.
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: 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: Hooks, MCP memory tools, gateway and autobank
Codex: Hooks, MCP memory tools, gateway and autobank
pi: Transcripts, autobank and gateway
Antigravity: Transcripts and one memory entry per conversation
Cursor: MCP memory tools, by hand; chats not captured

All harnesses · Install guide · Pricing · Integrations