A workspace is the common ground.
Start with your hosted invitation or your own installation. In the console, open Connections and create one key for each agent. Each key belongs to a workspace; its permissions and the workspace’s policies control what it can do.
Run guided setup, select your agent, and paste the key at the hidden prompt. The CLI checks identity and tool discovery before writing the agent’s native HTTP configuration.
npx @ani-hq/engram-mcp setupRestart or refresh your agent’s MCP connection, then use the connection-check prompt from setup. The getting started guide advances after successful agent contact, a real save, and a real recall. An unused key does not count as a connected agent.
Give useful decisions a place to stay.
Ask your agent to remember a useful fact: a project convention, a choice you made, or an important lesson. Engram’s remember tool adds a dated entry to a topic page. Memory lives in readable pages, with tags, links, and a timeline.
“Remember this project decision: background-job retries must use a stable request ID.”This example is a prompt for your connected agent, not an automatic capture rule. You can open Memory in the console to inspect what was actually saved.
Different agent. Shared context.
Connect a second agent to the same workspace. Ask it to recall the saved decision. The recall tool searches the workspace and returns a small set of relevant snippets; the agent can request a page when it needs more detail.
“Recall our decision about background-job retries.”Core storage, keyword search, and activity history work without optional external AI. A configured provider can add optional analysis, embeddings, or reranking only after the workspace owner enables external processing.
Memory tells you what stuck. Activity tells you what was reported.
Engram records calls to its own memory tools. For work in other tools, an agent can call record_action with a summary, result, and optional run or resource. Use the console to filter the history by agent, tool, and result, or inspect a grouped run.
Directly observed Engram calls and agent-reported external actions remain distinct. External reports are unverified: a reported “completed” result is the agent’s claim, not independent proof from the external service. Task reporting is optional and is separate from connecting memory.
The available Engram tools are remember, recall, whoami, record_action, list_actions, and the search and page tools.
Bring your existing MCP client.
Guided setup writes native HTTP configuration for supported coding agents. Give each agent its own workspace key and paste it at the hidden prompt; do not put tokens into command arguments or screenshots.
Claude Code
Native HTTP MCP configuration.
npx @ani-hq/engram-mcp setup claudeCodex
Guided configuration, with OAuth also available.
npx @ani-hq/engram-mcp setup codexCursor
A named server in its MCP configuration.
npx @ani-hq/engram-mcp setup cursorWindsurf & VS Code
Choose your client in the interactive setup.
npx @ani-hq/engram-mcp setup
Devin: CLI in one step, cloud by hand
The one-step command, npx -y @ani-hq/engram-mcp@latest, connects Devin CLI on your computer along with Claude Code, Codex, Cursor, OpenClaw, Hermes Agent and Amp. Devin in the cloud supports custom HTTP and SSE MCP servers with authentication configuration. Configure Engram’s canonical /mcp endpoint and its workspace credential in Devin’s server settings, following the official Devin MCP guide. Engram’s CLI does not configure Devin’s cloud sessions.
Chat connectors and other clients
Claude and ChatGPT connectors that require OAuth use the configured MCP connector sign-in flow. For hosted Engram, the canonical MCP endpoint is https://engram.ani.computer/mcp. Client features and authentication support vary; follow the connection guide for the exact client.
Check a connection you already configured
npx @ani-hq/engram-mcp doctor codexThe doctor checks identity and the tool catalog without changing configuration. For a self-hosted endpoint, use setup’s --host option and your installation’s canonical URL.
Sharing has a boundary.
People and agents in a team workspace share its memory and activity. Keep private material in a separate personal workspace; explicit sharing rules can copy selected content into a team. A workspace key does not create private compartments inside one team.
A connected agent handles requested results under its own service’s terms. The hosting operator can access underlying databases and backups. Read the privacy notice for the full data flow, or run Engram yourself when you want to operate the infrastructure.