Oz

Co-founder @egregore_xyz @curvelabs / prev @lucidmindsai @Trees_AI

[Oz @oyayla_]

excited to release egregore today.

a shared cognition layer for teams and their agents. memory, context, and workflows your team owns and evolves. a primitive you mutate.

we built egregore with egregore. curious where your team takes it.

[egregore @egregore_xyz]

find the others.
egregore is now open source.

a shared mind for teams working with AI.

[Oz @oyayla_]

GStack: one mind, many roles
@egregore_xyz: many minds, one substrate

[Garry Tan @garrytan]

GStack is actually an egregore for agents if you really think about it

[Oz @oyayla_]

@patrickc @egregore_xyz it is. and its open source

[Oz @oyayla_]

view skill creates a context dependent HTML rendering from our generative UI library (we even have dark mode)

try it: https://t.co/peHdgCy1XG

[Oz @oyayla_]

this was obvious to us since we do all our work and communication within egregore

thats why we built /view months ago to render handoffs, sessions and various document types

[Thariq @trq212]

https://t.co/MXt5XS4xBX

[Oz @oyayla_]

@studiobakers brought the aesthetics that amplifies. @keryilmaz is the cook.

[Bakers Studio @studiobakers]

Some brands are bold, different, we had fun working with our friends over at @egregore_xyz

[Oz @oyayla_]

@mattpocockuk yeah /handoff is the right shape. it's basically the seed of org memory. once you stop using mktemp and write to a persistent substrate that other agents and humans share, sequential handoff becomes multiplayer memory.. https://t.co/peHdgCy1XG

[Oz @oyayla_]

In SF. Lets hang

[Cem F Dagdelen @CemFDagdelen]

SFies hmu

[Oz @oyayla_]

@cynthiamcgillis the trick is separating substrate from interface. skills live in a repo (versionable, auditable, mergeable). non-tech people don't touch the repo. they read/write through the agent runtime, which handles git. different roles, same substrate. (building @egregore_xyz , OSS)

[Oz @oyayla_]

@JqOnly totally. we landed on three coupling layers at different swap costs, not one Contract.. engine cheap, skills medium, substrate expensive. each reasserts its own mobility under load. Curious if you collapse them by design, or they reappear at team scale.

[Oz @oyayla_]

@victorcardenas and we open source'd ours: https://t.co/2PXFu5hxF7

[egregore @egregore_xyz]

find the others.
egregore is now open source.

a shared mind for teams working with AI.

[Oz @oyayla_]

every egregore needs a mat

[ethan /entropy @entropy_eq]

we do a little welcome mat

“oh cool, so this instead of a Notion like we talked about?” ✨

[Oz @oyayla_]

@entropyeq_ @egregore_xyz the mat is the moat

[Oz @oyayla_]

@0xdasha @chiefofautism /invite is the partnership. DM us what you have in mind

[Ole Lehmann @itsolelehmann]

my friends at egregore just came out of stealth

i work with a lot of different people, and shared context between teams is THE biggest pain point

check them out, open source, ultra based team, i'm hyped for their product!!!!

[egregore @egregore_xyz]

Ex dispersis, unum

[Oz @oyayla_]

@keryilmaz you injected it maestro

[Oz @oyayla_]

@egregore_xyz in action. been dogfooding it for a while now and still amazed. launching for all very soon.

[KAAN @keryilmaz]

running egregore!

[Oz @oyayla_]

@jianxliao this + one layer up: Beads is what an agent remembers. @egregore_xyz is what the team remembers. The org graph persists even when individual agent contexts reset. open-source v soon