| name | devin |
| description | 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 workers, or start and steer autonomous Devin cloud sessions through the REST API, with a passthrough to any Devin v1/v3 endpoint. |
devin
The devin worker exposes Devin as iii functions across
two distinct surfaces.
The CLI surface drives the local Devin CLI (the
SWE-1.6 coding agent that runs in your terminal on your files). devin::run
executes one headless turn (devin --permission-mode dangerous --print -- <prompt>)
and streams stdout onto devin::events with a terminal AgentEvent frame on
agent::events. Because the agent runs locally with the iii runtime context
prepended, a plain-language prompt makes Devin discover and operate your engine
on its own: it runs iii trigger engine::functions::list, calls any registered
function, and reports back, reaching the engine at localhost with no exposure.
The cloud surface calls the Devin REST API: devin::session::create starts
an autonomous cloud session, devin::session::get reads it, devin::session::message
steers it, devin::pr-review::* runs code reviews, and devin::api reaches any
endpoint the typed wrappers do not cover.
The CLI surface needs the official Devin CLI installed (brew install --cask devin-cli)
and authenticated (devin auth login). The cloud surface needs DEVIN_API_KEY
(and DEVIN_ORG_ID for a service key). When a run needs a capability beyond
Devin itself, add another iii worker to the bus instead of bolting it on.
When to Use
