@cita-iris/agent-runner
v0.1.8
Published
Remote runner CLI that connects local Claude or Codex agent runtimes to an Iris server.
Maintainers
Readme
@cita-iris/agent-runner
Remote runner CLI for connecting local Claude or Codex agent runtimes to an Iris server.
The runner keeps model and tool execution on the local machine while the Iris server remains the control plane for chat sessions, runner tokens, tool callbacks, approvals, and audit events.
Install
Run it directly with npx:
npx -y @cita-iris/agent-runner connect --server https://ops.example.com --token <runner-token>Or install it globally:
npm install -g @cita-iris/agent-runner
iris-agent-runner connect --server https://ops.example.com --token <runner-token>The package exposes both iris-agent-runner and agent-runner binaries.
Usage
iris-agent-runner connect \
--server https://ops.example.com \
--token <runner-token> \
--runner-id macbook \
--provider claude \
--workdir /path/to/workspaceOptions:
--server: Iris server base URL. You can also setIRIS_SERVER.--token: runner token from the Iris server. You can also setIRIS_RUNNER_TOKEN.--runner-id: runner identity shown in Iris. Defaults to the local hostname.--provider:claudeorcodex. Defaults toclaude.--workdir: workspace used by the selected provider. Defaults to the current directory.--ca-file: trust a PEM certificate for self-signed tunnel endpoints.--insecure: disable TLS certificate verification for self-signed tunnel endpoints.
For SakuraFrp or other self-signed HTTPS tunnel endpoints:
npx -y @cita-iris/agent-runner connect \
--server https://frp-end.com:38235 \
--token <runner-token> \
--insecureProviders
Claude uses @anthropic-ai/claude-agent-sdk and exposes Iris tools through an in-process MCP server.
Codex uses codex app-server when available and falls back to codex exec --json.
Doctor
Check local prerequisites:
npx -y @cita-iris/agent-runner doctorThe doctor command checks Node.js, the WebSocket dependency, Claude Agent SDK availability, and Codex CLI support.
Security Notes
Keep runner tokens out of source control and shell history. Use placeholders such as <runner-token> in documentation and examples.
Iris approval and audit controls still run server-side. The runner forwards Iris tool calls back to the server instead of bypassing the server security model.
