Install & run

From source

Build from the Rust workspace in ~/w/roder. The primary binary isroder, provided by crates/roder-cli.

cd ~/w/roder
cargo build --workspace
cargo test -p roder-cli
cargo run -p roder-cli

Configuration

Roder reads ~/.roder/config.toml and supports environment overrides for common defaults.

RODER_PROVIDER=codex RODER_MODEL=gpt-5.6-sol cargo run -p roder-cli
RODER_PROVIDER=xai RODER_MODEL=grok-4.5 cargo run -p roder-cli
RODER_PROVIDER=openrouter RODER_MODEL=x-ai/grok-build-0.1 cargo run -p roder-cli
RODER_PROVIDER=mock cargo run -p roder-cli

Provider API keys can be set through config or the provider-specific environment keys. The default distribution resolves OpenAI, Anthropic, Gemini, xAI, SuperGrok, OpenRouter, Codex OAuth, Kimi Code, web search, subagent, JSONL session, memory, embedding, and built-in tool extensions from that configuration. Kimi Code can also save a key throughroder auth login kimi-code --api-key.

Codex OAuth exposes the current GPT-5.6 Sol, Terra, and Luna catalog. Sol is the default Codex model, and Sol/Terra can use RODER_REASONING=ultra when you want maximum provider reasoning plus Roder's bounded proactive delegation mode.

Policy modes

The CLI accepts policy controls that flow into the runtime policy gate.

cargo run -p roder-cli -- --mode plan
cargo run -p roder-cli -- --mode accept-edits
cargo run -p roder-cli -- --yolo

App server

Start the local JSON-RPC control plane over stdio when building a desktop client, integration test, or automation wrapper.

cargo run -p roder-cli -- app-server
cargo run -p roder-cli -- app-server --mode plan