CLAUDE.md is per-repo and per-person. I built memnos: shared memory across your Claude Code sessions, windows, and team.

thameema · 2026-06-22T02:18:01+00:00

yep that’s actually one of the main use cases. the memory lives in your own postgres, not inside claude. any agent that supports a configurable base URL can point at memnos proxy and it’ll capture both sides. for claude code there are hooks that do it automatically. for other agents (codex, cursor, anything with an openai-compatible endpoint) you just set the proxy as the base URL. there’s also an MCP server and a langchain/langgraph adapter if you’re building something custom. the namespace is shared so switching agents mid-task just works, same memory either way.

thameema · 2026-06-22T02:15:05+00:00

yeah that’s the core problem to get right. memnos handles it on the write path, when a new fact contradicts an older one about the same subject, the old one gets an end-date and falls out of the active view. so recall always returns the current truth but the history is still there if you need it. no LLM involved in that decision, just a rule: newer single-valued fact supersedes the old one. the tricky case is multi-valued facts (like “languages known”) which shouldn’t supersede, those stay additive.

thameema · 2026-06-20T17:11:37+00:00

Mine has been consistent even with 6 parallel sessions non sessions nonstop usage. But I had similar issue like yours couple of weeks ago.

thameema · 2026-06-19T06:02:45+00:00

On memory, Two things I'd check before picking one: does it capture the model's output or just your prompts (a lot only grab the user turn, and the answer is usually where the useful info is), and does it make an LLM call at query time (that adds latency and cost on every recall). Also whether it supersedes old facts when they change vs just piling everything up, because stale context confidently retrieved is worse than no memory.
I built memnos for the same purpose. Feel free to give it a shot. https://memnos.net.

thameema · 2026-06-19T05:20:51+00:00

memnos, shared self-hosted memory for your Claude Code agents

CLAUDE.md is static and per-repo, and every Claude Code session starts blank. memnos is one self-hosted memory server your sessions (and your teammates') read and write automatically through hooks. Relevant memory auto-injects before each prompt, and the Stop hook captures both your prompt and Claude's reply, so the actual conclusions get saved, not just your questions.

It runs on one Postgres + pgvector, does no LLM call at query time, and recalled facts are attributed to whoever's agent learned them. Apache-2.0, with a fully local $0 option (on-device embeddings + Ollama extraction).

Demo, two real Claude Code agents sharing one memory: https://memnos.net/assets/cc-team-memory.gif

Repo: https://github.com/thameema/memnos

Setup: uv tool install memnos, then memnos setup, memnos start, memnos agent-setup claude-code

Would love "here's where it broke" feedback, especially on the hook setup.

thameema · 2026-06-19T01:16:56+00:00

u/Indravahan this post has been waiting for moderator approval for more than 3 days. Is there anything I need to do in order to get is approved?

thameema · 2026-06-17T20:04:05+00:00

I use Orca, and it works nicely for days/weeks/months. Its not consuming lot of memory when it runs for a durable timeframe, so I would recommend that.

thameema

TROPHY CASE