Two-Way Claude Code Integration
The platform launches a real Claude Code CLI session against a project’s own workspace folder — headless for routine stage generation, or interactive when a person wants to pair with it — and that session authenticates back through a project-scoped API token to read approved inputs, push backlog items, register artifacts and log trace links. Nothing is simulated.
- The platform can trigger Claude Code unattended, and a person can open the identical folder and pick up where the run left off
- A scoped, revocable token — not a shared credential — makes every write attributable and audit-logged
- A draft-then-push protocol lets people iterate freely before anything registers on the governed record





