Ditto can live inside the agents you already use. The right setup depends on how the agent integrates with outside tools.
Choose Your Path
| Agent or tool | Integration type | Start here |
|---|---|---|
| Ditto CLI | Local command surface for agent skills | Ditto CLI |
| OpenClaw | ClawHub skill that calls the Ditto CLI | Connect Ditto to OpenClaw |
| Hermes Agent | Hermes skill tap that calls the Ditto CLI | Connect Ditto to Hermes Agent |
| Codex, Claude, Cursor, Antigravity, other MCP clients | Remote MCP server | Ditto MCP Server |
OpenClaw and Hermes do not connect to Ditto as MCP clients. They install a skill that invokes the ditto CLI. The CLI talks to Ditto’s API, stores or reads the same memory graph, and uses the same API key format as the app connect pages.
What The CLI Gives Agents
The Ditto CLI exposes the memory operations an agent needs while keeping auth local:
ditto searchfor semantic memory searchditto fetchfor retrieving specific memoriesditto savefor durable preferences, decisions, and factsditto subjectsfor subject lookupditto memoriesfor memory previews scoped to a subjectditto networkfor related memories and subject contextditto statusfor verifying auth and endpoint access
Use the dedicated docs for the exact install commands, API key flow, and troubleshooting steps for each agent. Use Ditto CLI when you need standalone install, auth, verification, or command reference details.
App Connect Pages
The app pages create API keys with the right naming and return path for each agent:
If you revoke a key from Ditto, the connected agent loses access immediately.