baton
The handoff layer for AI coding agents

Keep the
work moving.

When one agent stops, Baton leaves the next one a clear place to pick up. Plans, progress and the next step stay with your project—not trapped in a session.

Add Baton to your workflow See how it works
CClaude Code
SESSION 08
passing work
⌘Codex
SESSION 09
ready to resume
PROJECT / .BATON SAVED
MHANDOFF.mdnow
Done · auth flow mapped
Next · wire the callback
Designed for the tools you already use
CClaude Code
⌘Codex
MAny MCP client
A clean handoff, every time

Context fades.
The work state stays.

Baton turns the “where was I?” moment into a simple project-level handoff. It records the intent and next move in plain files that people and agents can both read.

01 / Before you stop

Pass the baton

Your agent captures what’s done, what comes next, open questions and the files that matter.

02 / Saved with the project

Readable. Durable. Yours.

A human-readable HANDOFF.md, structured state and an append-only ledger live in the project’s .baton/ folder.

03 / When you return

Pick up with clarity

The next session reads the latest handoff and continues from the recorded state—even in a different MCP-capable agent.

Up and running in minutes

One tiny server.
A better handoff.

Run Baton through MCP, then tell your agents when to pass and pick it up. Your handoff stays in the project folder.

CLAUDE CODECODEXNODE 18+MIT LICENSE
01 — CONNECT THE MCP SERVER
# Claude Code
claude mcp add baton \
  -e BATON_AGENT=claude-code -- \
  npx -y github:timurabi3/baton-mcp

# Add to your agent instructions
At session start: baton_pick_up
Before stopping:  baton_pass
Leave a better starting point

Your next agent should start with momentum.

Small, open and built around the project you already have.

Explore Baton on GitHub