Baton — Handoff de Sessão Limpo
blader/baton
Passe trabalho inacabado entre agentes sem perder contexto
Ver no GitHubSkill para passar trabalho em progresso entre agentes, sessões ou modelos através de um arquivo markdown verificado. Captura intenção, dead ends e próximos passos, grounded em estado real do repositório, não em narrativa do chat. Essencial para checkpoints e continuidade em projetos longos.
Instalação
npx convez-ai blader/baton1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Checkpoint antes de fim de sessão com trabalho incompleto
- Handoff para outro agente ou modelo continuar a tarefa
- Documentar dead ends e decisões para próximo executor
- Evitar re-derivação de contexto em sessões futuras
Veredito

Solução pragmática e bem-pensada para o problema real de continuidade entre agentes. A ênfase em verificação contra git (não chat) e na captura de dead ends é madura. Útil para qualquer fluxo de trabalho longo com múltiplos handoffs.
README
A tradução para o português deste README ainda está na fila.
Baton
Clean session handoffs. When you pass in-progress work to another agent — a fresh window, a future session, a different model — that runner starts with zero of your context. A baton is a single markdown file that lets them grab the work and sprint instead of re-deriving everything you already know.
Core principle
Capture what the next runner can't reconstruct from the code or git history — your intent, the dead ends you already ruled out, and the exact next step — grounded in verified repo state, not your chat narrative.
There are two sides to the skill: drop a baton (you're handing off) and grab a baton (you're picking one up).
When to use
Drop a baton when:
- A session ends with work unfinished and someone/something will continue it.
- The user says "hand this off", "pick up later", "pass this to another agent".
- You're running low on context and want to checkpoint before it's summarized away.
- You're about to dispatch the rest of the work to a separate agent/session.
Grab a baton when:
- Starting work in a repo where a prior session may have left one (check first).
Don't use for: a finished task (no handoff needed), or durable architecture rationale (that belongs in a long-lived design doc).
How it works
- Batons live in
.baton/at the repo root — local scratch, git-ignored, never committed. - Filename is
<YYYY-MM-DD>-<short-slug>.md; the next agent finds the latest withls -t .baton/. - The iron rule — verify before you write. A baton built from the chat story instead of repo reality is worse than none. Run
git statusandgit branch --show-currentfirst; the "State of play" section must reflect runtime truth, not the conversation. - The format is a fixed set of sections — Intent & Goal, State of Play (verified against git), Learnings & Landmines, Pointers, Next Steps, Open Questions — so every handoff has a consistent, scannable shape.
- The highest-value content is the dead ends already ruled out: naming what didn't work saves the next runner a full re-derivation.
Install
Claude Code
git clone https://github.com/blader/baton.git ~/.claude/skills/baton
Codex
git clone https://github.com/blader/baton.git ~/.codex/skills/baton
One-liner (auto-detect)
SKILLS_DIR="${CLAUDE_SKILLS_DIR:-${CODEX_SKILLS_DIR:-$HOME/.claude/skills}}" && \
git clone https://github.com/blader/baton.git "$SKILLS_DIR/baton"
Then restart your agent. The skill activates on handoff/resume triggers. You can also invoke it explicitly:
Drop a baton for the next session. Hand this off — write a baton. Check for a baton and pick up where it left off.
License
MIT