Menu
Run headless xAI Grok CLI turns over the iii bus — shell, file edits, and tools against any host directory — with verbatim event streaming and session resume.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | grok |
| description | Run headless xAI Grok CLI turns over the iii bus — shell, file edits, and tools against any host directory — with verbatim event streaming and session resume. |
The grok worker exposes the xAI Grok CLI as iii functions. One grok::run
call executes one headless Grok turn (grok --single <prompt> --output-format streaming-json) — the same agent the user runs in their terminal, with the
same XAI_API_KEY, filesystem, and working directory — in a chosen directory,
and returns the final result. Every Grok event mirrors
untouched onto the grok::events stream; a translated AgentEvent view lands on
agent::events, which is what the iii console renders.
Requires the grok CLI on the host with XAI_API_KEY in the worker
environment. When a turn needs a capability beyond Grok itself, add another iii
worker to the bus instead of bolting anything onto this one.
coder::* / shell::* calls
yourself: grok::run with prompt and cwd.session_id again and
the worker resumes the underlying Grok session with full context.grok::start returns
{session_id, started} immediately; follow grok::events (group_id =
session_id) for raw progress or agent::events for the rendered view;
interrupt with grok::stop.iii trigger <fn> --help); disable per turn with iii_context: false.grok CLI per turn — needs Grok installed and
authenticated (XAI_API_KEY); not available inside a bare container without
it.always_approve: true) so they don't block on an interactive
approval prompt. Set always_approve: false to let the CLI's approval
policy gate execution.grok::status (live: true)
before sending another grok::run for the same session_id; parallel
runs against one session race on the underlying session resume.agent::events carries whole-message frames; per-item progress detail
exists only on grok::events.grok::run — run one Grok turn and wait; accepts prompt (or a
messages array whose last user entry becomes the prompt), plus model,
cwd, always_approve, and iii_context; returns
{session_id, grok_thread_id, result, stop_reason, num_turns}.grok::start — same payload, returns {session_id, started}
immediately; progress arrives on the streams.grok::stop — interrupt the live run for a session.grok::status — point-in-time session view: live flag, status, turn
count.grok::sessions::list — every session this worker has run.