Your team and your agents, in one room.
A shared workspace, installed on your own server, where developers and coding agents work the same sessions, worktrees and approvals. You keep the harness you already use.
See Baton in action
An animated demo of the Baton app for Larkline, a made-up company. Ask: Maya asks the agent Aiden to fix a flaky checkout test, and Jordan suggests the cause. Steps: Aiden lays out four steps and Maya starts the run. Run: the steps complete one by one while terminal output streams into the session. Review: Aiden opens PR #482 with 20 of 20 runs green, requests Jordan's review, and the diff appears. Use the step buttons to jump the demo to a step.
Demo data from Larkline, a made-up company. One request becomes a reviewed PR without anyone leaving the session.Baton doesn't replace your agent. It gives it a team.
You keep the harness you already use. Baton adds what a single terminal can't: who asked, who holds the worktree, and who decides. Each harness checks with Baton's gate before it acts. How much reaches the gate depends on the harness; the security page lists it.
Run different harnesses in one project. Swap one out without changing how the team works.
- OpenClaw
- Hermes
- Grok Build
- Claude Code
- Codex
- SessionsPeople and agents in one thread
- WorktreesA lock, a queue and a handoff brief
- ApprovalsOne approver claims it
- LimitsAuto, Ask or Never, per project
- CreditEvery run is tied to a person
Installed on the server you already run.
Baton is a shared workspace on a machine you control. Developers and coding agents work the same sessions, worktrees and approvals there. You keep the harness you already use.
- Agents run as a non-root user, in a shared projects folder
- Baton's GitHub App mints short-lived tokens, each scoped to one repo
- Your code and your model keys stay on your server
- Beta onboarding is in small batches. Install steps are at trybaton.dev/install
- Sign-in
- Yours
- Agent user
- Not root
- Projects
- One shared folder
- GitHub
- Short-lived token, per repo
- Code and keys
- Not held by Baton
Start the day with what changed.
Needs you collects approvals, handoffs, review requests and mentions for whoever is signed in. A one-line brief on top says what agents finished overnight and what is waiting on people.
Agents you can see working.
You can see who is working, who is waiting on a person, and which harness is running. Claude Code, Codex, Grok Build, Hermes and OpenClaw share the same room.
Roll agents out to a team without losing track.
Limits per project
Decide what agents may do on their own. One project's settings might look like this. Ask turns an action into an approval. Never is a hard stop.
Approvals with one owner
Any approver can claim a request. Once claimed, only that person decides, so two people never approve the same push.
Runs credited to people
Every run is credited to the person who asked for it, in the session and in the project.
Handoffs with a brief
A worktree carries a lock, a queue and a written handoff brief. Needs you shows that handoff to the person who should pick it up.
- Done
- schema v2, tests green
- Open
- migration for renamed keys
- Risk
- plugin-owned keys
Bring your team. Bring your agents.
Baton is installed on your own server. Install it yourself from the install guide, or join the beta and we'll help you set it up in a small batch.