Choose an agent integration
OpenViking can act as the long-term memory and context backend for many agent runtimes. Pick the integration that matches your agent.
Which integration should I use?
| If you use… | Use this |
|---|---|
| Claude Code | Claude Code Memory Plugin — auto-recall + auto-capture via hooks |
| OpenClaw | OpenClaw Plugin — context-engine with full lifecycle integration |
| Codex / TraeCode CLI 2.0 | Codex Memory Plugin — lifecycle hooks for auto-recall and incremental capture |
| Cursor | Cursor Memory Integration — one command installs lifecycle hooks, MCP tools, rules, and skills |
| TRAE / TRAE CN | TRAE Memory Integration — one installer configures prompt-time recall, turn capture, and OpenViking tools |
DeepSeek Harness (dsh) | DeepSeek Harness Memory Bundle — in-process Cordis plugin with pre-step recall, event capture, and the OpenViking MCP tools |
| Hermes Agent | Hermes Agent. Memory plugin with automatic capture and recall. Older releases include a built-in provider. |
| OpenCode | OpenCode Plugin — MCP tools plus lifecycle hooks for repo context, auto-recall, and capture |
| pi | pi Coding Agent Extension — native extension with auto-recall, turn capture, threshold commit, and the server's MCP tools registered as native pi tools |
| LangChain / LangGraph | LangChain and LangGraph — retriever, tools, context backend, store, and middleware |
| Multiple local coding agents / a desktop UI | OpenViking Helper — visual agent setup, session inspection, and memory management |
| Any Agent Plugins 1.0 client | Agent Plugins 1.0 Package — one portable package: openviking-memory skill plus the OpenViking MCP tools |
| Manus / Claude Desktop / ChatGPT / other MCP clients | MCP Clients — point any MCP-compatible client at the built-in /mcp endpoint |
| Chat clients / SDK and API apps / other clients without a plugin | OpenViking Gateway — point any client that takes a base URL and an API key at the gateway; it recalls memory and saves conversations with nothing to install in the client |
| ZCode / AstrBot / … | Community Plugins — community-maintained integrations for various runtimes |
Some agents, such as Claude Code, Codex, OpenCode, pi and DSH, can use either their plugin or OpenViking Gateway. To decide between them, see Gateway or plugin?.
Compare integrations side by side
For the concrete differences between integrations — tool surface, automatic recall, session and commit behaviour, compaction takeover, degradation and fault tolerance — see the Capability Reference, a cross-integration comparison matrix.
Developing and maintaining plugins
To add or maintain an integration, follow the Hook + MCP Agent Plugin Development and Maintenance Standard. When using VibeCoding, require your coding agent to read and follow it before making changes, using Claude Code, Codex, and other existing plugins as implementation references.
Prerequisite for all integrations
Every integration on this page connects to a running OpenViking server. If you don't have one yet, follow the Quickstart Guide. The default endpoint is http://localhost:1933; remote use requires an API key (see Authentication).
Low-latency recall
After verifying the integration, use Tune recall latency to configure query expansion, result compression and timeouts.