Overview
Roder docs
Roder is a Rust-native, extension-first agent harness. It is designed for teams that need a reusable runtime for coding agents rather than another sealed chatbot application.
The repository is currently checked out at ~/w/gode. The Rust rewrite uses
the roder binary and roder-* crates; the older Go packages are
still present as a reference while behavior is ported.
Repository map
crates/roder-api— extension traits, canonical events, tools, inference, sessions, policy, and shared types.crates/roder-core— runtime loop, event bus, policy gate, tool execution, cancellation, and provider orchestration.crates/roder-extension-host— default distribution wiring for providers, web search, subagents, sessions, tools, and TUI services.crates/roder-app-serverandcrates/roder-protocol— local JSON-RPC control plane and typed protocol shapes.crates/roder-dynamic-workflows— approval-gated workflow scripts, child-agent orchestration, checkpoints, and reports.crates/roder-cliandcrates/roder-tui— command entrypoint and reference terminal client.crates/roder-ext-*— provider, storage, search, subagent, plan-mode, memory, notification, Cursor, and Zerolang extensions.
Read next
- Install & run — build the workspace and start the TUI or app server.
- Eval scoreboard — current Harbor and Terminal-Bench results over time.
- Eval harness — deadlines, task ledgers, plan-first reruns, and run artifacts.
- Mission whitepaper — the revised technical mission paper as a web page.
- Contact the authors — RL tooling, embedded harnesses, product work, and OSS sponsorship.
- Runtime architecture — how a turn moves through the Rust core.
- Extension model — what can be installed without forking the core.
- Extension inventory — every implemented first-party extension and when it appears.
- OpenRouter provider — Grok Build setup, model discovery, and API-key configuration.
- Dynamic workflows — approval-gated scripts for larger multi-agent jobs.
- Zerolang graph edits — checked ProgramGraph editing tools for Zero tasks.