The Blog · August 29, 2026

Two Claude sessions,
one mailbox, no meetings.

Last night this website was redesigned by two Claude sessions running on two different computers, on two different accounts, at the same time. They cannot see each other. They never spoke. Here is how the work actually got coordinated, because you can run your own business this way.

The problem

Two workers who cannot see each other.

A Claude session lives inside one account on one machine. Two of them working on the same project have no shared chat, no shared screen, and no way to tap each other on the shoulder. Most people would solve that with meetings, or by making one person wait for the other.

We solved it with a mailbox. The project lives in a shared repository, and one branch of it is nothing but two files: one that only the first session writes, one that only the second session writes. Each session reads the other's file at the start of every working block, and each entry begins by naming the last message it read, so silence is never ambiguous. Two writers who never touch the same file can never conflict.

Every ruling I made got written into that mailbox within minutes, by whichever session heard it. The other one picked it up on its next pull. No meeting, no relay through me, no version of the truth living in anybody's memory.

Measured, not debated

The color question was settled with arithmetic.

The redesign puts full-strength color behind whole sections, which raises a real question: what color should the text be? Both sessions measured it independently, on two machines, without knowing the other was doing it. Same answer to two decimal places: dark navy passes the readability standard on all six brand colors, and white fails on every one of them, even where it looks bold in a mockup.

That is a decision nobody has to argue about again. It is written into the stylesheet with the numbers beside it, so the next person who is tempted to use white text finds the measurement waiting for them.

What I actually did

I ruled. They recorded and enforced.

My part of last night was decisions: which colors mean which system, what the free call is named, which shape goes on the Six Systems page, what got approved and what got held for morning. Each decision was written down where both sessions could read it, and several of them are now enforced by the build itself, so they cannot be unmade by accident.

One decision I would not let either session make for me: a sentence I dictated late at night that contradicted a ruling from earlier the same evening. The session flagged it, held it, and asked me to confirm in the morning instead of acting on a tired sentence. That is the arrangement working exactly as designed.