Claude Code Adapter
The old claude-hook route now documents the current Machine-adapter model. RepoToire treats Claude Code as a provider runner: Claude can execute a bounded worker packet, while RepoToire owns write claims, evidence, gates, hazards, and precise traps.
Flow
# Inspect local Machine state
repotoire machine report .
# Run a bounded worker packet through the Claude adapter
repotoire machine spawn claude worker.json
# Join only after evidence and gates are available
repotoire machine join worker-42
What The Adapter Preserves
- Machine opcodes remain the stable workflow contract.
- Worker packets declare task intent, write claims, and completion requirements.
- Source-pipeline evidence records context, changes, and verification outputs.
- JOIN evaluates completion, evidence, verification gates, and scoreboard hazards.
- Precise traps stop stale or unsafe writeback with a clean restart point.
Trust Model
Commands are explicit. Networked provider calls are policy-gated. Beta onboarding maps these rules to your local CLI, macOS app, provider credentials, and team workflow.
See Also
- Claude Code integration - provider-adapter overview
- CLI overview - Machine commands
- Contact - request beta access