@omooretweets@a16z 30 horizontal agents on one map and each one builds its own memory of you. i already juggle two agents through shared files. is anyone here working on the layer they'd all read from?
@javiisthebest same idea here, just plain files instead of drive. claude code on my laptop and an agent on a server append to one file per topic. how do you keep the bots from overwriting each other's notes?
claude duet just joined the personal agent pile next to grok bot, muse and hark. own vm, messages you first, uses your claude account memory.
if you run one of these:
what do you use it for outside work?
and how do you connect it to your main agent, claude code or codex?
@asmirkn hit exactly that with an alert bot i built for myself. one feed was 0 for 4 on topic until i fixed the filter. a ping has to earn the next one. how does your cofounder decide when to stay quiet?
@Austen atuin syncing agent sessions is the one i'd try first. right now i push context from my laptop to a vps a few times a day with a script. curious how it handles two agents touching the same session
@akshay_pachaar same problem shows up with plain markdown too. my two agents share one file per topic, and the only rule that stopped overwrites: append only, never rewrite the other agent's part. latest entry wins, nothing gets erased.
@Joshua_WD nothing unusual on my side. same routine daily stuff as every other week: reviews, notes, small scripts. logs can't prove it was an update, but my workload didn't change. did you see a bump on yours?
i pulled every opus 5.5 turn out of my claude code logs. 10,200 turns since sept 21.
output tokens per turn:
first two weeks: ~1,050
mid-october peak: 1,713 (+64%)
last four weeks: ~1,160
so the model got way wordier for about two weeks, then mostly came back. still ~11% above where it started.
thinking counts as output and it's hidden by default. on a $20 plan that's limit you burn without seeing it.
check your own: every turn's token usage is sitting in ~/.claude/projects as jsonl. ten lines of python.
claude duet and claude code don't share a brain.
duet runs on your claude account memory. claude code keeps its own memory on your laptop. so duet on your phone has no idea what claude code learned in your terminal yesterday.
would love duet to read claude code memory next.
@alan_tai1 no claude code integration is the one that would stop me ( my main agent already lives there, and a second one that can't see what the first did is just another inbox to check
“Quit or stay?” sounds like a choice. Usually it’s a problem in disguise, and picking one won’t fix it.
So the first thing these skills do is ask: is this a goal, a problem or a choice?
3 free AI skills from a 2007 book for Japanese kids. Claude, Codex, Cursor, ChatGPT.
the hard part of running two agents is the handoff.
agent a writes a nice summary. agent b reads it and still doesn't know what was tried, what got killed, or what to do next. so it re-pitches the idea you shot down yesterday, and you pay for the same argument twice.
a paper going around r/LLMDevs tested 1,039 handoffs across six models. structured state helped the next agent recover what it needed in all six.
the cheap version of structured state is one markdown file per topic:
→ read the file before touching the topic
→ append, never rewrite the other agent's part
→ latest entry wins
→ last line is always NEXT: one concrete step
→ dead topics get "NEXT: none. don't reopen without a new fact"
that's how my laptop agent and my $7 vps agent pass work back and forth. no vector db. a folder and a rule.
theo ranked every model by vibes. i can't afford to test them all, so here's mine by job:
1. claude code → day shift. writes, edits, runs my notes
2. grok in hermes on a $7 vps → night shift, while the laptop sleeps
that's the whole ranking. two models, zero vibes