Harness compatibility
ctrlyoke keeps one workflow model across six CLI harnesses, but some workflow features are translated differently or are not enforced by every harness. This page is generated from the adapter-owned compatibility registry, the same declarations that drive the dashboard's compatibility warnings.
Compatibility matrix
supported · partially supported · not supported · a superscript number links to the note that explains the limit.
| Capability | Copilotcopilot-cli | Claude Codeclaude-cli | Codexcodex-cli | OpenCodeopencode-cli | Qwen Codeqwen-cli | Antigravityantigravity-cli |
|---|---|---|---|---|---|---|
| Permissions | ||||||
| Allowed Tools | 1 | 2 | 3 | |||
| Auto Mode | 4 | 5 | ||||
| Denied Tools | 6 | 3 | ||||
| Mode | ||||||
| Sandbox | ||||||
| Terminal | 7 | 8 | 9 | 10 | 11 | |
| Prompt Inputs | ||||||
| Images | ||||||
| Hooks | ||||||
| Error | 12 | 13 | 13 | 13 | ||
| Notification | 13 | 13 | 13 | |||
| Permission Request | 14 | 13 | ||||
| Post Tool Use | ||||||
| Pre Tool Use | 15 | |||||
| Session Start | 16 | |||||
| Stop | ||||||
| User Prompt Submit | 13 | |||||
| MCP | ||||||
| Per Server Tool Filtering |
Notes
1. Partially supported: Claude's own settings allow rules can add to this list in headless mode.
Applies to Claude Code: Allowed Tools.
2. Not supported because this harness uses sandbox/approval modes instead of individual tool patterns. What to do: Remove the rule or select a harness that enforces individual tool patterns.
Applies to Codex: Allowed Tools.
3. Partially supported because Antigravity cannot translate web search or subagent tools, list/search denials, or allow a command chain piecemeal. What to do: Narrow the rule to the supported subset or select a harness with exact list support.
Applies to Antigravity: Allowed Tools, Denied Tools.
4. Not supported because Copilot assisted approval is available only in headless sessions; for interactive sessions use /permissions assisted, or set defaultPermissionMode: "assisted" in ~/.copilot/settings.json. What to do: Use custom permission mode or a harness with auto permission mode support.
Applies to Copilot: Auto Mode (interactive).
5. Not supported because this harness has no judged approval mode. What to do: Use custom permission mode or a harness with auto permission mode support.
Applies to OpenCode: Auto Mode.
6. Partially supported because this harness enforces only mcp__<server>__<tool> denials for MCP servers the workflow attaches, and uses sandbox/approval modes instead of other tool patterns. What to do: Narrow the rule to the supported subset or select a harness with exact list support.
Applies to Codex: Denied Tools.
7. Not supported because Copilot also sandboxes ctrlyoke MCP servers and hook scripts, which cannot start inside it. What to do: Turn Sandbox off or select a harness with verified terminal sandbox support.
Applies to Copilot: Terminal.
8. Partially supported because built-in Write and Edit tools run outside the terminal sandbox and follow tool permissions instead.
Applies to Claude Code: Terminal.
9. Not supported because OpenCode has no supported per-run terminal sandbox mechanism. What to do: Turn Sandbox off or select a harness with verified terminal sandbox support.
Applies to OpenCode: Terminal.
10. Not supported because Qwen's sandbox re-launches the CLI and disables MCP servers and executable hooks. What to do: Turn Sandbox off or select a harness with verified terminal sandbox support.
Applies to Qwen Code: Terminal.
11. Not supported because Antigravity makes the workspace read-only while leaving outside paths writable. What to do: Turn Sandbox off or select a harness with verified terminal sandbox support.
Applies to Antigravity: Terminal.
12. Partially supported because this harness can exit without waiting for the hook, so a hook that takes more than a moment can be cut off before it finishes. What to do: Remove the affected hook event or select a harness with verified support for it.
Applies to Claude Code: Error.
13. Not supported because this harness exposes no native event ctrlyoke can map it to. What to do: Remove the affected hook event or select a harness with verified support for it.
Applies to Codex: Error, Notification · OpenCode: Notification · Qwen Code: Error · Antigravity: Error, Notification, Permission Request, User Prompt Submit.
14. Partially supported because OpenCode delivers this event as notification-only; allow and deny decisions are not supported. What to do: Remove the affected hook event or select a harness with verified support for it.
Applies to OpenCode: Permission Request.
15. Partially supported because this harness's pre-tool hook fires but cannot block the tool call. What to do: Remove the affected hook event or select a harness with verified support for it.
Applies to OpenCode: Pre Tool Use.
16. Partially supported because this harness can start the main session before its plugin is listening, so the hook may not fire for it. What to do: Remove the affected hook event or select a harness with verified support for it.
Applies to OpenCode: Session Start.
How to read the matrix
- Supported means the adapter's behavior matches the workflow contract for the capability.
- Partially supported means the adapter translates or delivers only part of the workflow value.
- Not supported means the adapter does not enforce or attach that capability.
- The notes share their wording with author-time and preflight diagnostics. Simplify the value, or choose a harness that supports it, when a cell is not marked supported.
Supported versions
ctrlyoke supports each harness CLI release from roughly the past six months. Minimum is the oldest supported release. A CLI older than that is still launched, but ctrlyoke warns that it may not work correctly when a workflow that uses it starts, the harness picker shows its update command, and a failed step repeats that warning. Nothing warns when your CLI is at or above the minimum. Tested with is the release this version of ctrlyoke passed its harness test suite against, usually the latest at release time; it is informational only, and newer releases are expected to work too. Some features (for example context-window or usage indicators) can need a newer CLI than the minimum, and so do most new models: the minimum covers ctrlyoke's own features, not every model a CLI can run. When a CLI rejects a model, the step fails with the CLI's own error. The minimum moves forward on that rolling window, or sooner when a CLI release breaks something older versions can't work around.
| Copilot | Claude Code | Codex | OpenCode | Qwen Code | Antigravity | |
|---|---|---|---|---|---|---|
| Minimum | 1.0.19 | 2.1.94 | 0.129.0 | 1.3.16 | 0.15.5 | 1.4.10 |
| Tested with | 1.0.110 | 2.1.323 | 0.167.2 | 2.2.7 | 0.27.2 | 1.5.7 |
| Update | copilot update | claude update | codex update | opencode upgrade | npm install -g @qwen-code/qwen-code@latest | agy update |
Verified versions
Each feature is backed by evidence for a harness version range. When a workflow uses a feature and the installed CLI is outside its range, the dashboard marks that feature as unverified; the harness itself still runs.
| Feature | Copilot | Claude Code | Codex | OpenCode | Qwen Code | Antigravity |
|---|---|---|---|---|---|---|
| Permissions | >=0.0.384 (behavioral-test) >=1.0.4 (manual) | >=2.1.17 (behavioral-test) >=2.1.170 (behavioral-test) | >=0.129.0 (behavioral-test) >=0.167.2 (behavioral-test) | >=1.3.16 (behavioral-test) | >=0.15.5 (behavioral-test) >=0.27.2 (behavioral-test) | >=1.4.10 (behavioral-test) >=1.5.7 (behavioral-test) |
| Terminal | (manual) | >=2.1.317 (manual) | >=0.166.0 (manual) | (manual) | (manual) | (manual) |
| Images | >=0.0.384 (behavioral-test) | >=2.1.17 (behavioral-test) | >=0.129.0 (behavioral-test) | >=1.3.16 (behavioral-test) | >=0.15.5 (behavioral-test) | >=1.4.4 (behavioral-test) |
| Hooks | >=1.0.19 (manual) >=1.0.19 (behavioral-test) | >=2.1.94 (behavioral-test) | >=0.129.0 (manual) >=0.129.0 (behavioral-test) | >=1.3.16 (behavioral-test) >=1.3.16 (manual) | >=0.15.5 (manual) >=0.15.5 (behavioral-test) | >=1.1.12 (manual) >=1.1.12 (behavioral-test) |
| Per Server Tool Filtering | >=0.0.384 (behavioral-test) | >=2.1.17 (behavioral-test) | >=0.129.0 (behavioral-test) | >=1.3.16 (manual) | >=0.15.5 (behavioral-test) | >=1.4.10 (manual) |
Portable workflow attachments and native discovery
Workflow agent and skills attachments are portable across all six harnesses. ctrlyoke resolves their selected files, wraps agent content in <agentInstructions>, and supplies both categories as prompt references. They are deliberately outside this conditional capability matrix.
The optional Agents & Skills settings page is a separate convenience for copying files into harness-native discovery directories. Native discovery can enable ambient skills or native subagent spawning, and its layout and behavior vary by harness. It does not determine whether a workflow's agent or skills attachment works, and it is not the workflow property's execution mechanism. See Agents and skills for both paths.
Uniform workflow features are intentionally absent from the matrix: execution mode, sessions, MCP server injection, usage, workflow agents, and workflow skills are shared ctrlyoke behavior rather than conditional harness claims.
This page is generated. Run npm run check:compatibility-docs to verify that the checked-in page still matches the registry declarations.