opencode-cli-runtime

opencode CLI Runtime

Use this skill when the user asks to delegate review, rescue, status, or setup work to the local opencode CLI.

The plugin delegates to opencode-companion, which wraps the local opencode executable. In a source checkout, the same runtime is available at plugins/opencode/scripts/opencode-companion.mjs.

opencode has no --sandbox flag. Read-only work runs on opencode's built-in plan agent (no file modifications). Write work runs on the built-in build agent (full read/write/execute). When OPENCODE_COMPANION_TRUSTED is set (path-delimited list), writes are only allowed under a listed workspace; otherwise writes are unrestricted and opencode's own build permission model applies.

Background jobs are stored under ${OPENCODE_COMPANION_DATA}/jobs/<workspace-hash>/, then ${CLAUDE_PLUGIN_DATA}/jobs/<workspace-hash>/, then the OS temp directory.

Commands

• Setup: opencode-companion setup [--json] [--auth-check]
• Review: opencode-companion review [--background] [--base <ref>] [--model <p/m>] [extra instructions]
• Adversarial review: opencode-companion adversarial-review [--background] [--base <ref>] [--model <p/m>] [extra instructions]
• Rescue: opencode-companion rescue [--background] [--write] [--continue] [--session <id>] [--model <p/m>] <task>
• Status: opencode-companion status [job-id]
• Result: opencode-companion result <job-id>
• Cancel: opencode-companion cancel <job-id>

Operating rules

• Return opencode-companion stdout/stderr verbatim for setup, status, result, and cancel.
• For reviews, do not inspect files yourself unless the user explicitly asks you to compare the output against local source.
• For rescue, prefer read-only delegation (plan agent) unless the user requests a write, fix, patch, implementation, refactor, create, delete, or similar file-changing task.
• --continue resumes the last opencode session; --session <id> resumes a specific one.