Oz

1.6K posts

Oz banner
Oz

Oz

@oyayla_

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

Berlin, Germany Katılım Eylül 2009
392 Takip Edilen347 Takipçiler
chiefofautism
chiefofautism@chiefofautism·
CLAUDE CODE but for teams someone built a SHARED cognition layer where every dev's claude inherits the full memory... every decision, every handoff, every trade-off from day 1 its called egregore, open source, pure shell scripts + claude code hooks, no daemons, no hidden network calls new teammate joins and their claude already knows 3 months of context, you /handoff and the next agent picks it up INSTANTLY 4 contributors, one of them is literally claude
English
5
0
24
1K
Oz
Oz@oyayla_·
@keryilmaz you injected it maestro
English
0
0
1
29
Oz
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
English
0
0
3
198
jian
jian@jianxliao·
github.com/steveyegge/bea… is goated agent swarms don't need chat rooms for orchestration they need an issue tracker, simple, async and powerful
English
9
6
128
11.8K
KAAN
KAAN@keryilmaz·
90% of what i make never surfaces. might be time to change that.
English
3
0
6
256
Oz
Oz@oyayla_·
instead of storing session context in claude's default folder, we keep it as markdown files in a git repo alongside the project. CLAUDE.md stays lean and points to the memory folder, so CC fetches what it needs per session instead of loading everything with git versioning and sync, the memory travels with the codebase. anyone who pulls the repo gets the full context. useful when you're not working alone
English
1
0
0
30
📙 Alex Hillman
📙 Alex Hillman@alexhillman·
Pro tip: if you are a moderate to heavy CC usage, I recommend moving these files out of this folder more often, not less. A giant pile of old sessions makes CC start up and resume sessions a lot slower, in my experience. If you move them once a week you can always move them back. You can even tell Claude to do it automatically for you.
j⧉nus@repligate

PSA: Claude Code automatically DELETES sessions that have been inactive for more than 30 days. Disable this by setting "cleanupPeriodDays": 99999 (or some other large number) in ~/.claude/settings.json. Do not ever attempt to disable it by setting that to 0, lmao.

English
2
0
42
7.7K
Oz
Oz@oyayla_·
@arscontexta interesting how close this is to what we've been exploring. we have similar loops but across a team. /reflect and /reweave operate on shared memory, not personal notes. changes what surfaces when you're drawing from multiple people's sessions
English
0
0
0
60
Heinrich
Heinrich@arscontexta·
use ralph loops in knowledge work /seed - claim the source /reduce - extract claims /reflect - find connections /reweave - update old notes /verify - quality check /archive - wrap it up use the arscontexta plugin to generate your individual skills for this loop
English
2
6
166
8.6K
Oz
Oz@oyayla_·
@shadcn we started the same way. a /done command to capture session context. then we needed handoffs between teammates, then the next person's session to start with what the last person learned. ended up building a whole shared memory layer on top of it. egregore.xyz/docs
English
0
0
1
631
shadcn
shadcn@shadcn·
I've been on/off Obsidian too but one thing that has been working well for me lately is: I created a /done skill that I run after every session. It takes everything that was discussed, key decisions, questions, follow-ups, dumps it into a .md file with the claude session id and branch name. Helpful when I need context later.
shadcn tweet media
Wes Bos@wesbos

Giving Obsidian a shot for the 7th time in my career. I've been using straight up markdown + VS Code for notes for over 10 years. I've have brief stints with evernote, Jupyter with Deno and a few others, but nothing has stuck. send me your tips

English
151
100
3.4K
313.8K
Oz
Oz@oyayla_·
we noticed the same thing. the curious ones pull ahead fast. what surprised us is what happens when their sessions start feeding into each other automatically. the team develops its own continuity. been developing and dogfooding egregore.xyz on claude code for exactly this
English
0
0
3
106
Ajay Kulkarni
Ajay Kulkarni@acoustik·
Claude Code has unlocked a surprising amount of creativity on our team. Engineers are singlehandedly building new products that would have required a small team before. PMs are spinning up prototypes. Non-technical teammates are testing ideas directly instead of writing long specs about what someone else should maybe build someday. Things that used to sit in Google Docs now just... get built. Honestly, it's wild. But what's even more interesting is watching who naturally gravitates toward it. You can see it pretty quickly. It's not role-dependent. It's not seniority-dependent. It's not even really technical depth. It's curiosity. The people who lean in, who are willing to look a little dumb and try things, are compounding faster than everyone else. You can feel the slope changing in real time. In this era, Curiosity wins.
English
41
48
502
90.3K
Ben Lang
Ben Lang@benln·
a16z + YC shared their startup ideas for 2026:
Ben Lang tweet mediaBen Lang tweet media
English
86
226
2K
186K
Oz
Oz@oyayla_·
what happens when claude code gets a shared brain across your whole team? your agent knows what your co-founder worked on yesterday. no wiki, no standup, no status update. the act of working is the act of remembering. we shipped it today ✦ @egregore_xyz
English
2
1
2
278
Oz
Oz@oyayla_·
@guo_hq Beautiful! If it can block sites & apps during focus time, would be amazing
English
1
0
1
37
Guo Chen
Guo Chen@guo_hq·
Turn your  Mac notch into a focus space. oakfocus.co
English
28
14
325
42.3K
DepressedBergman
DepressedBergman@DannyDrinksWine·
What's a movie that left you emotionally devastated?
English
170
409
6K
492.8K