Browse docs▾
Adapters & support
Coding OS is agent-agnostic by design, but how much it can enforce depends on which hooks a runtime supports. Here is exactly what fires where — no overclaiming.
| Runtime | Hook coverage | What that means |
|---|---|---|
| Claude Code | Full | Every hook fires — gates, skills, doc-anchors, and verification. The engineering loop is enforced end to end. |
| Codex (CLI & app) | Full | Full hook parity — Bash, file edits, MCP tool calls, prompt context, and session lifecycle all fire. Same gates, same enforcement. |
| Humans | Git hooks | Install the git hooks and the commit contract holds; the board and graph are agent-optional — ideal for mixed human/agent teams. |
Reference
- Claude Adapter — Deepening Checklist
- Claude Adapter Migration Guide — 2026-05
- Claude Adapter Rollback Guide
- Claude Adapter — Full Reference
- Claude Adapter — Architecture
- Codex AdapterCurrent contract for the OpenAI Codex adapter: execution backends, hook translation, capability bounds, dependency policy, and the path to full interactive parity.
- Claude Session-Options Builder (SSOT)