Baton

About

Baton is less about inventing a new agent and more about making existing CLI agents actually manageable. It gives each agent a real worktree, keeps the human in the loop with visibility tools, and wraps the whole thing in a local-first desktop interface.

Why It Is Hot Now

It is getting attention because more developers now run Codex, Claude Code, OpenCode, and similar tools in parallel, then discover that ordinary terminals are a poor coordination layer. Baton is a practical answer to that exact workflow mess.

Key Features

• Runs multiple coding agents at once, each on its own git worktree and branch.
• Adds built-in diffs, file search, content search, notifications, and browser preview.
• Includes an MCP server so agents can spawn more workspaces and coordinate tasks.

Real Use Cases

• Parallelizing feature work across several coding agents without file collisions.
• Reviewing agent output with clearer diffs and workspace-level visibility.
• Keeping local control while still giving agents structured orchestration tools.

Community Pulse

The strongest positive reaction is around worktree isolation because it solves a very real source of agent chaos. The recurring questions are about remote-device workflows, how far the orchestration can scale, and whether desktop-first tooling is enough for bigger teams.

Limits and Risks

Baton still depends on the quality of the underlying agents and on a developer who understands Git. The free tier also caps concurrent workspaces, and desktop-native tooling may not fit every team setup.

Alternatives

Natural alternatives include Agor, Multica, Warp or Antigravity style agent environments, and fully manual tmux plus git-worktree setups.

FAQ

• Who should try Baton first? Developers already using terminal-based coding agents who want more control than separate terminal windows can offer.
• What should teams validate early? Whether the desktop-first model, Git workflow, and concurrency limits fit how they actually build software.