Give your AI agents a memory that lasts
Stop re-explaining your codebase, your conventions, and yesterday's work to every new chat. Context survives the session, the project, and the tool.
Free, no credit card. Setup in under a minute.
One agent writes a memory into a Capsule and a different agent recalls it later, shown across three scenarios: An incident you only debug once, A convention every agent follows, A quirk of your setup.
Index every new user lookup field before shipping. The last unindexed one caused a production rollback.
- database/indexed-lookups
- style/commit-messages
- ci/pnpm-catalog
This change adds a lookup field, so I've included the index — per the earlier rollback.
Persistent memory in three steps
Create a Capsule
An isolated key-value store. One per agent, project, or use case.
Generate an API key
Each Capsule gets its own key. Share it only with the agent that needs access.
Connect your agent
Point any MCP client at the Capsule, or call the REST API.
Show me the raw MCP config▾
mcp-config.json
More than a place to dump strings
Isolated Capsules, scoped keys
Every Capsule is its own key-value store with its own API key. Rotate or revoke from the dashboard.
coding-agent
agm_7fKq2aWd…
research-notes
agm_Rz4nBt09…
prod-bot
agm_Ld8xVc3M…
Audit logging built in
Every read and write is timestamped and traceable.
SET database/indexed-lookups
GET style/commit-messages
SET ci/pnpm-catalog
MCP and REST
Use the open protocol, or call plain HTTP from anything else.
Search, tags, and expiry
Agents can search stored memories, group them with tags, and set a TTL on anything that shouldn't outlive the task.
Every memory makes the next agent smarter
Three agents, one week, one Capsule. Watch a memory get written, recalled, and reused.
Built for the way agents actually work
Your conventions, every repo
Structure, naming, and preferred libraries live in memory, so agents start with your rules instead of guessing.
“Always use Drizzle, never Prisma. Server actions live in lib/.”
Drop into any codebase
Architecture notes and environment quirks persist, so a new agent is useful without rediscovering context.
“Monorepo with pnpm workspaces. Auth in Clerk. Deploy on Vercel.”
Preferences that stick
Save tone and formatting rules once and reuse them without repeating the same setup prompt.
“Concise, no emojis, prefer bullets over paragraphs.”
Resume where the job died
Checkpoints and outputs persist between runs, so long automations resume instead of starting over.
“Last row processed: 4,281. Retry queue: empty.”