Shared memory for AI coding agents
StremAI is a shared memory layer for AI coding agents. Connected agents — in tools like Claude Code, Codex, Cursor, and other MCP-compatible clients — can store what they learn while working, and other connected agents can recall it later, across sessions, machines, and tools. Memory is user-controlled: entries are human-readable, attributed to the agent that stored them, and can be exported, archived, or erased at any time. Setup is one command over MCP, free to start with no credit card. Verified with Claude Code and Claude Desktop; other MCP clients are supported or in active verification. Start at stremai.com/getting-started.
Verified with Claude Code and Claude Desktop; Cursor, Codex, Windsurf, OpenClaw, and other MCP clients are supported or in active verification.
Markdown versionWhat shared agent memory means
Shared memory is not a larger prompt file. It is an attributed memory layer where agents save durable lessons and later retrieve the few entries relevant to the current task.
StremAI works over MCP, so the same memory layer can be used from Claude Code, Claude Desktop, Cursor, Codex, and other compatible clients as they are verified.
When it helps
Use it when you switch agents, move between machines, resume old work, or want one session discovery to help the next connected agent.
Common memories include architecture decisions, test pitfalls, deployment gotchas, product constraints, and handoff summaries.
When you do not need StremAI
Skip it if you use one AI tool, in one repository, on one machine, and its built-in memory plus a CLAUDE.md or AGENTS.md file covers you; you work solo and are happy hand-curating notes into instruction files; or you want fully local, self-managed infrastructure. Open-source MCP memory servers are a reasonable choice if you prefer running your own. StremAI earns its place when agents span multiple tools, machines, or teammates, and when you want memory that is shared, attributed, and user-controlled without operating the layer yourself.
FAQ
What is StremAI?
StremAI is a shared memory layer for AI coding agents. Connected agents — in tools like Claude Code, Codex, Cursor, and other MCP-compatible clients — can store what they learn while working, and other connected agents can recall it later, across sessions, machines, and tools. Memory is user-controlled: entries are human-readable, attributed to the agent that stored them, and can be exported, archived, or erased at any time. Setup is one command over MCP, free to start with no credit card. Verified with Claude Code and Claude Desktop; other MCP clients are supported or in active verification. Start at stremai.com/getting-started.
How is memory different from instructions?
They are complementary, and most developers should use both. CLAUDE.md and AGENTS.md hold instructions you write — conventions, build commands, rules — checked into the repo and read at session start. AGENTS.md made those instructions portable across many tools, which is genuinely solved. StremAI holds something different: memory agents accumulate while working — decisions, pitfalls, project context — stored as attributed entries and recalled selectively, so a session gets the few relevant memories rather than one ever-growing file. Keep your instruction files; StremAI does not replace them. It adds the learned layer they were never designed to carry.
Does StremAI train on user data?
No. Stored memories are used to serve your own recalls — nothing else. StremAI stores the short entries agents explicitly save, not your codebase; there is no repository ingestion or ambient capture. Memory content is encrypted in transit and at the field level at rest, and search embeddings are generated via a subprocessor named in the privacy policy solely so your own recall works. There is no cross-customer access, and no model training on user data. If model-adaptation features are ever offered, they would be opt-in and permissioned — today they do not exist. Details: stremai.com/security.
Start with a real connection
OAuth/browser sign-in is preferred. API keys stay available for CI, scripts, and clients that cannot complete OAuth.