메뉴
Run headless OpenCode turns over the iii bus — file edits, shell, and search against any host directory — with verbatim JSON event streaming, session resume, and inline token usage and cost.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | opencode |
| description | Run headless OpenCode turns over the iii bus — file edits, shell, and search against any host directory — with verbatim JSON event streaming, session resume, and inline token usage and cost. |
The opencode worker exposes the OpenCode API as iii functions. One
opencode::run call executes one headless OpenCode turn — the same agent the
user runs in their terminal, with the same tools — in a chosen working
directory, and returns the final result, token usage, and cost. Every JSON
event OpenCode emits (step_start, text, tool_use, step_finish) mirrors
verbatim onto opencode::events; a translated AgentEvent view lands on
agent::events, which the iii console and the acp worker render.
Requires the opencode CLI on the host and an API key for the LLM provider you
use (e.g. ANTHROPIC_API_KEY, or opencode auth). When a turn needs a
capability beyond OpenCode itself, add another iii worker to the bus instead of
bolting anything onto this one.
opencode::run with prompt and cwd.session_id again and
the worker resumes the underlying OpenCode session (--session).opencode::start returns
{session_id, started} immediately; follow agent::events (group_id =
session_id) for the rendered view or opencode::events for raw JSON;
interrupt with opencode::stop.iii trigger <fn> --help); disable per turn with
iii_context: false.model as provider/model, agent as an
OpenCode agent name.opencode CLI per turn — needs OpenCode installed and a
provider key; not available in a bare container without it.opencode::run / opencode::start are not agent-callable without human
approval (they spawn a full agent with the host's shell + filesystem);
read-only introspection is allowed (see iii-permissions.yaml).opencode::status (live: true) before
another opencode::run for the same session_id.opencode::run — run one turn, wait; accepts prompt (or a messages
array), plus model, cwd, agent, iii_context; returns {session_id, opencode_session_id, result, stop_reason, usage, total_cost_usd}.opencode::start — same payload, returns {session_id, started} immediately.opencode::stop — interrupt the live run for a session.opencode::status — point-in-time session view: live flag, status, turns,
usage, cost.opencode::sessions::list — every session this worker has run.run::start_and_wait — alias for opencode::run under the entrypoint the
console and acp worker drive.Run Unix commands and structured filesystem ops from the iii engine: exec, background jobs, and a structured fs (ls/stat/mkdir/rm/chmod/mv/grep/sed/ read/write, jailed only if fs.host_roots is configured), all forwardable into a sandbox microVM.
Shared, adapter-backed key/value store addressed by scope and key, with a reactive `state` trigger so other functions can run on every create, update, or delete without polling.
Durable topic queues for iii: subscribe functions to topics, publish work asynchronously, retry failed deliveries with backoff, and inspect/redrive dead-lettered messages.
Mint isolated git worktrees for parallel agent work, track ownership in a cross-agent registry, and land finished branches back onto a target with a queued rebase, test gate, and atomic fast-forward merge.
Connect this engine to another iii engine over a long-lived WebSocket so functions call across the boundary. Wire stable ids with `forward:`/`expose:`; `bridge.invoke` is the ad-hoc escape hatch.
Drive Devin over the iii bus. Run the local Devin CLI agent (SWE-1.6) with the iii runtime context so it discovers and operates your mesh, or start and steer autonomous Devin cloud sessions through the REST API, with a passthrough to any Devin v1/v3 endpoint.