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.
Egregore (https://egregore.xyz). multiplayer cognition for Claude Code. been building this with my co-founder at curve labs.
there's a lot of good work happening on agent memory right now. but it's all single-player. your agent remembers what you did. it has no idea what your co-founder just spent four hours figuring out. we kept solving the same problems twice, or discovering decisions the other had made only when something broke.
the missing piece wasn't better memory. it was shared memory. not 'sync your notes,' but a layer where the act of one person working becomes context for the next person's session automatically.
egregore adds this shared cognition layer on top of claude code. your team shares tooling, knowledge, and skills that evolve with how you actually work. you get full visibility into what the organisation is doing, not through dashboards, but because the memory is right there when your agent starts a session. handoffs between team members, structured reflection on workflows, a knowledge graph that connects decisions to who made them and why.
we've been running on this internally for about a month and honestly the difference is hard to go back from. the organisation has its own continuity now. context stopped being something you maintained and became something that just accumulated from working.
terminal-first, git-native. we just launched and are looking for early alpha testers. if you're building with claude code in a small team, happy to give early access if you want to try it!
Thanks! really appreciate it! Shortly: We're trying to turn LACE into a curiosity engine instead of another note graveyard.
Right now you can clip fragments from the web, LACE auto-organises them into evolving research threads, builds a concept graph + summaries, and lets you chat with your own library (find bridge connections, pull related papers, or turn a cluster into an essay draft).
Where we're going: more “emergent” behaviour – high-signal rabbit holes (papers, videos, posts) based on what you’re actually working on, plus light collaboration so people can share drafts and reading lists around a question. The idea is that LACE keeps organising and resurfacing things for you, on the right time, instead of you fighting with folders/tags in Obsidian/Notion.
If that sounds fun, I'd love it if you can give it a spin and give us feedback. I'm on https://x.com/oyayla_ - if you can DM me I can also invite you to our Telegram group.
https://meetlace.ai - LACE, a self-organising research companion for long-horizon inquiry.
With LLMs, generating ideas and snippets is cheap; what’s hard is keeping track of fragments with their “why I cared” context over months. Most tools (Notion/Obsidian/etc.) assume you will do the work (folder/tag/linking) structure will maintain it forever. I don’t.
In LACE we:
– capture fragments from the web via a browser extension
– auto-cluster them into evolving “threads” / projects with summaries & reading lists
– maintain a graph of connections across threads (“topology of attention”)
– let you turn a cluster of fragments into an essay draft when you’re ready to share.
Stack is a fairly standard web app + LLM pipeline. Used neo4j's llm-graph-builder as a starting point.
The interesting bit is self-organising graph. treating fragments/questions/lines of inquiry as first-class objects and letting the system reorganise around them over time instead of fixed folders.
It’s in a small test phase right now. If you’re a researcher/writer/engineer/founder who constantly loses good ideas in your notes and want to try something opinionated in this space, I’d love feedback.