Show HN: Egregore – Shared memory and coordination for multiplayer Claude Code(github.com)
github.com
Show HN: Egregore – Shared memory and coordination for multiplayer Claude Code
https://github.com/egregore-labs/egregore
5 comments
OP (oguzhan) here. Cem is also in the thread — he takes the mechanism-design / "how does it actually work" questions; I'll take the team-adoption, install, and ops questions.
Two things that didn't fit in the post:
What's an "egregore"? Old word for a group-level entity sustained by the people holding it together. We picked it because it's literally the technical thing we built. The name is a shibboleth; use whatever framing works for you.
Who this probably isn't for yet. If you're a solo developer, Claude Code by itself is likely enough — Egregore's weight only pays off when more than one person is writing into the substrate. We'd rather say that now than have you install it and bounce.
Ask us anything — install problems, mechanism-design questions, the "how is this different from X" comparisons, and whether any of this survives a real team that isn't us. Especially the last one.
Two things that didn't fit in the post:
What's an "egregore"? Old word for a group-level entity sustained by the people holding it together. We picked it because it's literally the technical thing we built. The name is a shibboleth; use whatever framing works for you.
Who this probably isn't for yet. If you're a solo developer, Claude Code by itself is likely enough — Egregore's weight only pays off when more than one person is writing into the substrate. We'd rather say that now than have you install it and bounce.
Ask us anything — install problems, mechanism-design questions, the "how is this different from X" comparisons, and whether any of this survives a real team that isn't us. Especially the last one.
Cool. Shared memory is critical - what core rules do you follow to have agents share memory but also have independent and relevant memory for their job that is unique?
we were essentially working on dynamic ontology systems (how to organize unstructured data given context / starting conditions dynamically). since december new capabilities that came around with opus 4.5 completely altered the nature of our work. but despite the radical increase in speed and ambition of our experiments, we were visibly diverging from a common vision. once we acknowledged that together, we decided to find ways to infrastructure mechanisms for convergence. first it was integrating the GitHub organization and repos we are working on, later we developed custom commands that would help us share research, request code reviews and even send each other spam through a tg connector we built for notifications :)
https://imgur.com/a/egregore-telegram-notification-LM0ldPV
we then realized we can integrate the agentic knowledge graph infrastructure we were building for the dynamic ontology research. our stack emerged very rapidly and one week in it was glaringly obvious that we should stop everything and get to working exclusively on this. the speed of accumulation of multi-agent context coupled with frontier model capabilities yielded wow moments one after another. for two months we implemented key features and improved core functionalities.
given our background in organization design and distributed systems, we knew that this was a primitive that should be spread widely and experimented with since there is no single good answer to how an organization should be designed. but it was clear to us that using agent harness form factor as an organization design substrate is incredibly promising given: speed of context accumulation, the continuity (handoffs) it enables between individuals and adaptability of the organization to changing (internal and external) conditions.
anyway, after couple months of wow-ing to our own creation we knew we had to get this out and face the moment of truth whether: we actually built something interesting or we are getting high off our own supply. so thats what we are doing today: we created a version of egregore — slash commands, git-backed markdown memory, Claude Code hooks — that is self-hosted and without dependencies (no knowledge graph etc) so that we can release it as a viable open-source primitive anyone can use and mutate according to their needs with their friends and colleagues.
what you can do with it today:
- `/invite` — onboard a teammate with the full accumulated context already in place - `/handoff` — pass a session on with reasoning and context preserved. the next person, future-you, or their agent picks up the thread without restarting - `/activity` — see what the team has actually been doing, synthesized from real sessions - `/deep-reflect` — cross-reference an insight against the organization's full memory - `/view` — render a shareable artifact from any slice of what the team knows
excited to have you all try, and get your feedback.