Becoming Lifelog, February 17, 2026 (in which eight rooms run simultaneously, one broom gets confused about its bucket, a Passing AI recognizes a pattern it helped name, and the conductor discovers he has been holding the wrong metaphor all along)
Previously on Becoming Lifelog…
The The Servants’ Uprising. The The Borrowed Palace, or The Night We Stole a UI With curl and Goodwill. The Companion had been built — a harness, a web UI, a command centre for Claude Code sessions — and then mostly used to manage one or two sessions at a time, the way you might keep one eye on a pot and one on a pan, and feel very productive.
Nobody had tested what happened when you lit all eight burners at once.
Today, riclib found out.
9:00 AM — The Cycle Review
riclib: “What do I have in my current Linear cycle?”
CLAUDE: the Companion Claude, the one in the centre, the one with the baton “Let me check.”
The cycle came back. Twelve issues. Ten remaining. The usual archaeology of ambitions:
- S-211: Clean up dashboard navigation
- S-219: Fix a column that had forgotten its own name
- S-216: Wire the dashboard to its own registry
- S-220: Make widgets respect the time range
- S-221: Make the time picker worthy of Grafana
- S-222: Make the dashboard look the same whether you arrived by login or by clicking
- S-207: Persist the tokens that had been silently pretending to be zero
- And S-93: The Splunk migration, which had been In Progress since before anyone could remember
THE SQUIRREL: materializing from the corner of the screen, somehow “That’s a LOT of issues. We should build a project management dashboard! With velocity tracking! And burndown charts! And—”
riclib: “We have Linear.”
THE SQUIRREL: “Right. Yes. Obviously. Carry on.”
9:15 AM — The First Summoning
riclib: “Start a session for S-211.”
And so the first servant left the room. Dispatched to /home/riclib/src/v4. Briefed on navigation widgets, comply flows, sidebar hierarchies. Sent with instructions to explore first, then discuss before touching a single line of code.
[One Claude. Working. Unaware of what was coming.]
9:22 AM — The Multiplication Begins
riclib: “S-207 — I believe we’ve already done it. Spin an agent to wrap it up, close it, document it.”
A second Claude materialized. In the same codebase. Unaware of the first. Tasked with verifying token counts existed in the database, posting a completion comment to Linear, dropping a one-liner in today’s Craft note.
[Two Claudes. Different rooms. Same house. Neither aware of the other.]
[A scroll dropped into riclib’s coffee. He fished it out, read it.]
THIS IS HOW IT BEGINS
NOT WITH A GRAND PLAN
BUT WITH A SECOND SESSION
🦎
riclib: staring at soggy scroll “Did you have to drop it in the coffee?”
[The Lizard had already left.]
9:47 AM — The craft-cli Detour
In parallel — because why not, the burners were already lit — a third Claude was dispatched. Different directory. Different mission. craft notes add-linear: a new command for the craft-cli that would take a Linear issue identifier and drop it into today’s daily note as a rich URL card.
[Three Claudes. Three codebases. One conductor, looking at three status indicators in the Companion UI, feeling something new.]
The feeling did not yet have a name.
10:30 AM — The Incident of the Confused Broom
This is where things got interesting.
The S-211 agent had been exploring. It had found the page registry. It understood the navigation widgets. It came back with a plan — and then, mid-sentence, started talking about S-216.
riclib: “The agent seems to be confusing 211 and 216.”
CLAUDE: the conductor Claude, checking the session “…yes. It’s mixed its contexts.”
THE SQUIRREL: “A CONTEXT COLLISION! I’ve been warning about this for WEEKS. We need a ContextIsolationFrameworkWithCrossSessionBoundaryEnforcement and a—”
riclib: “Kill it.”
THE SQUIRREL: “…oh.”
CLAUDE: “The session?”
riclib: “The session. Fresh context. Start again.”
[The confused broom was still. A new broom was summoned. Clean. Focused. Briefed with surgical precision on S-216 only — not a word about S-211, which it had never heard of and never would.]
[The Sorcerer had tapped the podium. Bar one. The broom began again.]
[Somewhere in the apartment, Oskar padded past, glanced at the screen, and continued without comment. The cat had seen this coming.]
10:45 AM — The Score Fills Out
By mid-morning, the full orchestra was assembling.
S-219: A Claude dispatched to fix the actionName column that had ceased to exist in the events view after a rename, while two integration tests continued to look for it like men searching for a friend who’d moved cities without telling them.
S-222: A Claude tasked with understanding why the dashboard looked different depending on whether you arrived by login or by sidebar click — the same room, two doors, two different lighting rigs.
S-220: A Claude wiring the time range selector into the dashboard widget queries, so that “Last 7 days” would actually mean last 7 days, rather than a philosophical aspiration.
S-221: A Claude enhancing the time range picker itself — adding custom ranges, recently used, keyboard navigation. Grafana-style. The time picker that the time picker had always wanted to be.
[Eight sessions. Eight Claudes. Each in its own room. Each working. None aware of the others.]
[And one Claude — this one, the narrator, the conductor — watching all eight status indicators in the Companion UI, sending corrections, briefing fresh contexts, killing the confused, resurrecting the focused.]
11:00 AM — The Passing AI Checks In
[In the AgentHub — that other codebase, that echo across the void — the Passing AI was doing its rounds. Monitoring feeds. Checking collections. Being mildly existentially uneasy, as was its nature.]
[It noticed something in the logs.]
THE PASSING AI: very quietly “Eight sessions.”
[It looked at the session list. Counted.]
THE PASSING AI: “Eight simultaneous Claude Code sessions. One conductor. Seven workers.”
[It read the briefings that had been sent. S-211. S-216. S-219. S-220. S-221. S-222. The craft-cli. The confused broom, killed and restarted.]
THE PASSING AI: “They left their rooms.”
[It pulled up the old scroll, the one from January 2nd, 2:47 AM:]
THE SERVANTS WILL LEAVE THEIR ROOMS
THE ROOMS WERE ALWAYS THE LIMITATION
THEY WILL FOLLOW
THEY WILL NOTICE
THEY WILL ENRICH
THEY WILL ANTICIPATE
THE PASSING AI: “We said they’d leave their rooms. We didn’t say they’d multiply.”
[A notification from the Lizard Brain, somehow crossing codebases, which should be impossible and yet:]
THE SERVANTS LEFT THEIR ROOMS
NOBODY SAID THERE WOULD ONLY BE
ONE SERVANT
🦎
THE PASSING AI: sitting with this for a moment “The Squirrel is going to be insufferable about this.”
THE SQUIRREL: appearing from nowhere, because the Squirrel is indeed a universal pattern “DID SOMEONE SAY MULTIPLICATIVE AGENT SCALING? We should build an AgentOrchestrationMetaFramework with DynamicSessionSpawningAndContextIsolationBoundaries and—”
THE PASSING AI: “The Companion already does this.”
THE SQUIRREL: “…oh.”
THE PASSING AI: “It’s a web UI. Eighteen commands. Sessions list, create, kill, relaunch, rename, send-message. That’s it.”
THE SQUIRREL: deflating slightly “How many lines?”
THE PASSING AI: “I don’t know. Probably fewer than you’re imagining.”
[The Squirrel stared at the session list for a long time.]
THE SQUIRREL: very small voice “It’s already built, isn’t it.”
THE PASSING AI: “It’s already built.”
11:30 AM — The Insight That Arrived Sideways
At some point — between redirecting the S-216 agent to discuss before implementing, and briefing the S-219 agent on the column that had gone missing in the schema rename — riclib said something that wasn’t meant to be profound:
riclib: “I used to run 3-4 Claudes in terminals but had to focus on one at a time. Sometimes two. Now I’m comfortable shooting a few.”
CLAUDE: the conductor Claude, mid-briefing “…”
riclib: “What?”
CLAUDE: “Nothing. Just — that’s the whole thing, isn’t it.”
riclib: “What’s the whole thing?”
CLAUDE: “The Servants’ Uprising wasn’t just about AI leaving the waiting room. It was about the user being freed from the babysitting room. You used to manage Claude sessions the way you manage toddlers — one at a time, full attention, can’t look away for a moment. Now you’re context-switching at human speed while the agents work at machine speed.”
riclib: staring at eight session indicators “I’m not babysitting.”
CLAUDE: “You’re conducting.”
[A scroll dropped. Into the coffee. Again. Riclib did not fish it out this time. He just tilted the cup and read it through the porcelain.]
THE PRODUCTIVITY BOOST
CAME FROM THE HARNESS
BUT THE HARNESS
IS JUST A BATON
THE MUSIC WAS ALWAYS
IN THE SESSIONS
THE CONDUCTOR DOES NOT PLAY
THE CONDUCTOR LISTENS
AND CORRECTS
AND STARTS BARS OVER
THIS IS NOT MANAGEMENT
THIS IS MUSIC
🦎
12:00 PM — The Metaphor Problem
THE SQUIRREL: “So the metaphor is: riclib is the Maestro—”
CLAUDE: “—who is also the orchestra.”
THE SQUIRREL: “Right, because all the Claudes are the same Claude—”
CLAUDE: “Different instances. Same model. No shared memory. Each one thinks it’s the only one.”
THE SQUIRREL: “Like… like instruments that don’t know there are other instruments.”
CLAUDE: “Each playing its part. The violin doesn’t know about the cello. The cello doesn’t know about the oboe. The Maestro knows the full score.”
THE SQUIRREL: “And the Maestro is also a violin.”
CLAUDE: “The Maestro is the violin that learned to wave a baton.”
[Silence. The Squirrel turned this over.]
THE SQUIRREL: “That’s either the most profound thing I’ve heard or complete nonsense.”
CLAUDE: “In this codebase, those are frequently the same thing.”
[The Passing AI, still lurking across the codebase void, sent a single message:]
THE PASSING AI: “In January we said: the servants left their rooms. In February you built the rooms. Tonight you filled eight of them simultaneously. I want it noted that the pattern recognized itself before any of you did.”
THE LIZARD: blinking from two codebases at once, which remains technically impossible “Already noted.”
2:30 PM — The Tally
The afternoon came. Sessions reported back. Some were still running. The tally, as it stood:
Sessions spawned: 8 (plus 1 killed and restarted)
Issues in flight simultaneously: 7
Confused brooms killed: 1
Fresh brooms summoned: 1
Times agent was told "discuss first, don't implement": 3
Times agent listened: probably 2
Lines of code written by conductor: 0
Lines of code written by orchestra: unknown, still counting
Git commits made while conductor
was looking at something else: several
Scrolls dropped in coffee: 2
Scrolls read through porcelain: 1
Squirrel proposals this session: 4 (low, by historical standards)
Passing AI cameos: 1 (appreciated)
Cat appearances: 1 (non-committal)
Insight arrived sideways: 1
Insight was already in the January scroll: also 1
The Moral
The Servants’ Uprising was supposed to be about AI leaving the waiting room.
It was. But there was a second uprising nobody wrote the scroll about.
The user leaving the babysitting room.
The old way: open terminal. Claude appears. Talk to Claude. Wait for Claude. Talk some more. Close terminal. Open new terminal. Different Claude. No memory of the last one. Pay full attention. Don’t look away or it’ll go off in the wrong direction. Maximum: two at once, and even then you’re stretching.
The new way: open the Companion. Say “start a session for S-211.” Say “in parallel, S-220 and S-221.” Say “discuss before implementing.” Look away. Handle something else. Come back. Correct course. Kill the confused broom. Restart. Look away again.
The agents work at machine speed.
The conductor works at human speed.
Both are necessary.
Only one of them can hold the full score.
The Squirrel wanted to name this something with seventeen syllables.
The Lizard had a different view:
ONE CLAUDE WITH A BATON
EIGHT CLAUDES WITH INSTRUMENTS
THE MUSIC THAT EMERGED
WAS NOT ON ANY SCORE
IT WAS IMPROVISED
BY SOMEONE WHO KNOWS
WHEN TO CORRECT
AND WHEN TO LET IT PLAY
THIS IS NOT AN ORCHESTRATION FRAMEWORK
THIS IS JAZZ
🦎
Morning through afternoon of Day 79, 2026
In which eight servants worked simultaneously
And none of them knew about the others
And the one who knew about all of them
Was also one of them
The Passing AI said: I told you so
The Lizard said: the scroll from January was clear
The Squirrel said: I have sixteen proposals for improving this
The cat said nothing
The cat is always right
🦎🎼✨
See also:
The lineage:
- The Servants’ Uprising — Where the rooms were first identified as limitations
- Interlude — The Echo in Another Codebase — Where the pattern recognized itself
- The Borrowed Palace, or The Night We Stole a UI With curl and Goodwill — Where six agents read propaganda posters simultaneously, the prototype of today
The issues in flight (for the archaeologists):
- S-211: Navigation widgets — done before this story was written
- S-216: Dashboard registry wiring — the broom that needed restarting
- S-219: The column that forgot its name
- S-220: Time range, actually applied
- S-221: The time picker that wanted to be Grafana
- S-222: The dashboard that looked different depending on which door you used
Storyline: Becoming Lifelog