HarnessLink for pi
HarnessLink captures pi's prompts and transcripts, banks every finished turn into the memory your other harnesses search, and routes pi's Anthropic and OpenAI Codex calls through the local gateway. pi has no hooks HarnessLink can use, so memory does not flow back into a pi session.
What HarnessLink captures from pi
| Feature | In pi | Details |
|---|---|---|
| Prompt history | Yes | Your prompts, read from the session transcripts. |
| Session transcripts | Yes | ~/.pi/agent/sessions/<folder>/*.jsonl, 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 ~/.pi/agent/models.json. |
| Context hooks | No | pi has no hook HarnessLink can install. |
| Memory tools (MCP) | No | There is no MCP preset for pi. |
| Org policy rules | No | Not enforced: pi has no tool hook. |
| Skills from templates | Yes | hnl add <skill> installs into ~/.pi/agent/skills; pi also reads ~/.agents/skills. |
| Resume in another harness | Yes | hnl resume reopens a pi session through omp. |
Set up pi
Install HarnessLink on macOS or Linux (Windows has its own one-liner).
curl -fsSL https://harnesslink.sh/install.sh | bashSign in once in your browser; setup then turns on what each harness on the machine supports.
hnl cloud setupOr turn the pieces on one at a time.
hnl gateway connect pi hnl cloud harnesses enable pi hnl cloud autobank enable piCheck what is connected: plain
hnlshows, for each harness, the gateway, transcripts, autobank, context and memory tools.hnl
How memory reaches pi
HarnessLink does not add memory to a pi session: pi has neither context hooks nor an MCP preset.
What you do in pi still counts. Every finished turn is banked, so Claude Code, Codex and omp find it through their hooks and memory tools, and it shows on the dashboard's Memory and History pages.
Limits
- No context hooks and no MCP memory tools in pi.
- Org policy rules are not enforced in pi. Model rules and usage limits apply to its Anthropic and OpenAI Codex providers through the gateway.
Guides
- Using HarnessLink: Using HarnessLink day to day: Ask, history, policies, shared memory, resuming sessions across harnesses, profile sync, templates, delegation, runs and cost.
- 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
- omp: Context extension, MCP memory tools, gateway and autobank
- Antigravity: Transcripts and one memory entry per conversation
- Cursor: MCP memory tools, by hand; chats not captured