DevStudio

Running coding agents from a terminal works fine until you want more than one. I'd end up with a row of tabs, no idea which agent was still working, no record of what any of them had done once the scrollback rolled away, and no way to say "start this at 6am" or "run the review after the build finishes". The agents were capable; the thing around them was a terminal and my memory.

DevStudio is that missing thing — a web console I self-host, where agents are configured, run, watched and chained.

Why I built it

• Several agents at once, without collisions. Every session gets its own git worktree, so two agents working in the same repo never tread on each other. Sessions queue their own turns, so I can keep typing while one is still thinking.
• No API keys. Every agent drives the real claude or codex CLI as a child process, so the only credential involved is the login I complete in the UI — the subscription I already pay for, not a second metered bill. Any other CLI I've already signed into can be described on a page and become an agent provider too.
• Steer a run that's already going. If an agent is heading the wrong way I can send guidance mid-turn rather than waiting for it to finish being wrong, and optionally interrupt the turn so the correction lands immediately.
• Work that happens without me. Workflows chain agents into ordered steps that pass their output along, and a scheduler runs an agent or a workflow on a cron expression. Overnight review passes, morning summaries, that sort of thing.
• Agents that can see each other. The orchestrator exposes its own MCP server, so an agent can list the other sessions, read another agent's transcript, leave notes, steer a run, or start one — which is what makes a supervising agent possible at all.
• A volume backup is the whole backup. State is JSON files on a Docker volume. No database to run, migrate or lose.

It started as a way to stop losing track of what my agents were doing, and turned into the place I actually run them from — several at a time, on a schedule, in repos they can't damage.

For installation, configuration and the full feature list, see the GitHub repo.