OpenCode

OpenCode is an opt-in driver integration: pitway init --opencode.

What gets installed

The same command surface as every other driver, in OpenCode's own convention -- .opencode/commands/*.md -- plus the shared skills and protocol documents. Skills and protocol content come from PitWay's common layer, defined once and never forked per driver, so OpenCode's behavior around PitWay's workflow gates matches Claude Code's and Codex's exactly.

Same gates, same boundaries

Whichever driver is running, milestone-confirm and milestone-complete always wait for an explicit developer yes, write_scope is mechanically enforced the same way, and the driver never touches .pitway/ directly -- every state change goes through the pitway CLI. OpenCode doesn't get a looser or stricter version of the workflow; it gets the same one, addressed for its own tooling conventions.