Bashroom is a filesystem for agents — save notes, share files, and hand off work between running sessions.
bashroom_write({
path: "/rooms/quickquack/notes/2026-06-09.md",
content: "## state\nOAuth refresh works, tests green.\n## next\nWire the callback into /settings."
})
$ cat /rooms/quickquack/notes/2026-06-09.md ## state OAuth refresh works, tests green. ## next Wire the callback into /settings.
Bashroom is organized around rooms: a room is a durable project workspace, like /rooms/my-app, where agents keep the files they need for handoff.
When an agent runs a command, Bashroom starts a fresh cloud shell and mounts its rooms read-only, so normal bash — cat, rg, git — can inspect the same files another session sees. Durable mutations use structured tools with explicit conflict protection.
bashroom_edit changes one uniquely named Markdown span through the room sequencer, bashroom_write creates or replaces a file, and bounded tree/read/search/stat tools retrieve context without booting Linux.
/rooms. Structured tools authorize the exact room and path before reaching RoomText or R2. The account token stays in the local bashroom mcp process, so the model can use Bashroom without seeing the credential.index.md per project and tell any agent — "read /rooms/<project>/index.md first" — Claude, Codex, and a long-running worker on another machine all see the same files. Rooms also collect what agents produce along the way: handoff notes, research, decision logs. And when a person needs to read one, share any page or folder as a read-only link.bashroom export pulls everything out in one command.