CLAUDE.md vs StremAI
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.
Verified with Claude Code and Claude Desktop; Cursor, Codex, Windsurf, OpenClaw, and other MCP clients are supported or in active verification.
Markdown versionConcede first
CLAUDE.md and AGENTS.md are the right place for instructions you write: conventions, commands, repo policy, and review rules.
If that solves your workflow, keep it simple. StremAI is not a replacement for instruction files.
The difference is scope, not quality
Instruction files are authored by humans and read at session start. StremAI stores learned memories as agents work, then recalls only the relevant entries later.
Keep CLAUDE.md and AGENTS.md for the rules. Add StremAI when connected agents need to recall decisions, pitfalls, and handoffs across sessions, tools, or teammates.
When StremAI is not the right fit
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
Does StremAI replace CLAUDE.md or AGENTS.md?
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.
What should go in CLAUDE.md?
Put explicit instructions there: commands, conventions, repo rules, coding standards, and review policy.
What should go in StremAI?
Store learned memory: decisions, pitfalls, architecture notes, handoffs, and recurring context agents discover while working.
Start with a real connection
OAuth/browser sign-in is preferred. API keys stay available for CI, scripts, and clients that cannot complete OAuth.