mechabedo
Seven coding agents, one window, and one search box over everything any of them ever did.
One window over every coding agent you use
A harness is an agent mechabedo drives. All of them speak the same protocol here, so one conversation, one permission prompt and one queue serve every one of them.
Claude Code, Codex, OpenCode, Qwen Code, Hermes, maki
Each is a real process speaking the Agent Client Protocol. Nothing about a conversation is reconstructed; it is what the agent actually sent.mechabedo's own coding agent
The seventh is mechabedo itself, running against your gateway rather than a vendor's CLI.One loadout picks all four things at once
Which harness, which model, how hard it thinks, and what it carries.
Everything it ran is one search away
Every session is archived in one normalized format, whichever harness produced it and whether it started here or in a terminal.
The Logbook
Search across sessions, then read one in the workbench's own vocabulary rather than a second one.What earlier sessions settled
Memory records a directory carries, so the next session does not re-derive them.Your own code, searched by meaning
A per-project index an agent queries by what a declaration does rather than by a string it contains.
The surfaces around the session
An IDE, real terminals, a scratchpad, a token meter and a floating assistant, all in the same window and all open at once.
Monaco behind a real language client, over the directories your agents work in.
Several destinations open at once. Every open tab stays mounted.
As many real shells as you open, over the one socket the page already holds.
A page of characters laid out by hand rather than flowing text.
A floating assistant that sees and drives the app through the meta layer.
Ctrl+P over everything the app can do, scoped by prefix.
Reach it from anywhere, without opening a port
An installation dials out to a beam host you run. A browser anywhere reaches it through that host; the machine itself has no inbound route, no hostname and no certificate.
Connecting one installation
The host address, a slot token, a slot name. Nothing else.Running the host
Sizing, the proxy in front, the three kinds of secret, what to watch, and the failure table.Agentic workspaces in the cloud
A fleet of server-shaped installations, one slot each, provisioned and operated as infrastructure.
mechabedo is a session manager and chat client for AI coding assistants. It runs on your machine as a desktop app, on a server as a container, or as both at once with a tunnel between them.
Seven harnesses run under it on one protocol, because seven CLIs with seven interfaces is not a workflow, it is a tab problem. Chat, in-page tabs and one enhancement layer sit on top. Everything any of them ever ran lands in an archive you search rather than remember.
Start here
| If you want to | Read |
|---|---|
| Get it running and open a first session | Install and first run |
| Understand the window you are looking at | The window |
| Drive coding agents | AgentDeck |
| Know what picks the model | Loadouts |
| Find what an earlier session did | Logbook |
| Reach a machine that is not in front of you | Beam |
| Run this for other people | Operating |
Builds are on the product page, behind the passphrase you were given.