This post is still being written — please check back later. Posted: May 2026.
Bashroom is a shared folder that my coding agents read from and write to — Claude on the laptop, Codex on the desktop, and a long-loop agent on a Cloudflare Worker all see the same files. Each agent leaves notes for whichever one shows up next, and the running record is what carries state across sessions and machines.
The problem it solves is that every agent session was starting cold. Useful context from the previous run lived in a chat scrollback on a different machine, or in a terminal I'd already closed, and the first ten minutes of every new session were spent reconstructing things that already existed somewhere I couldn't see.
The mechanism is one MCP tool that runs bash, with a fresh shell on every call so nothing persists implicitly. Files written under /rooms survive; everything else — environment variables, working directory, /tmp — does not. That asymmetry is the whole design: if a piece of state is worth keeping past the current call, it has to be a file with a name, and the file tree becomes the readable history of what the agents have been doing.
What ends up in there is the boring half of agent work — deploy notes, decisions and the reasoning behind them, hand-offs between machines, a running log per project that the next agent skims before it starts. The hosted reader at bashroom.sdan.io shows the same files in a browser, with GitHub OAuth and invite-only rooms, so I can read along from a phone and bring a collaborator into a room without making them install anything.