Your team and your agents, in one room.
Baton is a shared workspace where developers and coding agents work the same sessions, worktrees and approvals. Keep your harness. Give the whole team one place to direct it.
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. Plan: Aiden reads the last 10 CI runs and proposes a 4-step plan of about 5 minutes and at most 30k tokens, 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.
Each agent connects through an adapter. Baton handles what a single terminal can't: who asked for the work, which worktree it holds, what needs approval, and who picks it up next.
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
- WorktreesOne holder at a time, claim or request
- ApprovalsClaim, then approve or deny
- Dev serversA preview, database and logs per branch
- UsageCredited to whoever asked
A live preview for every session.
Bring your own dev server and rent only the Baton layer on top, or let us spin one up for you. Either way, each branch gets a preview URL, agents build and test there, and teammates watch logs stream into the session.
- Your server: a VM, a box under a desk, Cloudflare, or Kubernetes
- Ours: spun up per branch, asleep when idle
- Preview URL, database and logs in the session
- Staging on its own, production behind an approval
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.
From one sentence to a running agent.
Mention an agent in any session. It answers with a plan that shows time, token budget and what it will ask before doing. Start it, steer it mid-run, or roll back to any step.
Agents you can see working.
Every agent has a face, a status and a history. You can tell at a glance who is thinking, who is blocked on a person, and what each one shipped today, whichever harness runs it.
Roll agents out to a team without losing track.
Limits per project
Decide what agents may do on their own. 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.
Usage credited to people
Agent runs count against whoever asked for them, so spend shows up per person and per project.
Handoffs with a brief
Moving work to a teammate moves the session, the worktree lock and a written brief together. Unaccepted handoffs expire after 24 hours.
- Done
- schema v2, tests green
- Open
- migration for renamed keys
- Risk
- plugin-owned keys
Bring your team. Bring your agents.
Connect the dev server you already run, or let us spin one up. We're onboarding teams in small batches.
Connect a serveror get an invite and we'll set up servers for you