Every harness HarnessLink banks writes to the same memory: omp, Claude Code, Codex and pi bank each finished turn, Antigravity one entry per conversation. Claude Code, Codex and omp read it back: a brief of the project when a session starts, related entries on each prompt, and the MCP memory tools when the model wants more. Cursor gets the memory tools too, registered by hand. So a decision made in Claude Code can come up in Codex, and when you are signed in, memory_search adds what your other machines banked.
| Feature | Claude Code | Codex | omp | pi | Antigravity | Cursor |
|---|---|---|---|---|---|---|
| Prompt history | Yes | Yes | Yes | Yes | Yes | No |
| Session transcripts | Yes | Yes | Yes | Yes | Yes | Partly |
| Memory bank (autobank) | Yes | Yes | Yes | Yes | Partly | No |
| Gateway routing | Yes | Yes | Yes | Yes | No | No |
| Context hooks | Yes | Yes | Yes | No | No | No |
| Memory tools (MCP) | Yes | Yes | Yes | No | No | Partly |
| Org policy rules | Yes | Partly | Yes | No | No | No |
| Skills from templates | Yes | Yes | Yes | Yes | Yes | Yes |
| Resume in another harness | Yes | Yes | Yes | Yes | No | No |
Claude Code gets everything HarnessLink does: its transcripts and prompts are captured, every finished turn becomes a memory entry, a project brief and related memories arrive through Claude Code's own hooks, and the model can search the same memory your other harnesses write.
Codex gets the full set: its transcripts and prompt history are captured, every finished turn is banked, context hooks bring a project brief and related memories into each session, and the MCP memory tools search what Claude Code, omp and pi banked too.
omp is the harness the installer adds by default. HarnessLink captures its prompts, transcripts, todos and plans, banks every finished turn, brings memory into each session through a managed omp extension and gives the model the MCP memory tools.
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.
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.
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.