claude-bus
Leave a job on the office PC; a fresh session on the home PC picks it up. One shared folder, no server.
Two machines share one folder. One side drops a JSON file, a watcher on the other side picks it up within a minute, spawns a fresh session, and puts the result back in the same folder. No server, no port, no auth — it rides on a sync folder that was already running.
It buys you the machine, not the files
Everything under the synced folder is already on both machines. You don’t need a bus to move files.
What a bus buys you is the other machine itself.
- Hardware only it has — a GPU, an attached device, a game client
- A network only it can reach
- Software only it has installed
Why build a slow channel on purpose
A chat app moves in seconds. But if the other machine is asleep, messages just pile up. This bus takes three minutes and wakes the sleeper.
Waking and speed are different axes. When people pick a channel they only look at the second one.
Written up in three parts
| The problem | |
|---|---|
| Protocol | Making conflict copies impossible in a two-way sync folder |
| Timing | Measured where the three minutes go — it wasn’t my code |
| Safety | What stands between somebody else’s instruction and my machine |