Ori Harness - Run Your Agent on OpenRouter
This is setup documentation for Ori, a command-line launcher that runs coding agents like Claude Code, Codex, and OpenCode on your OpenRouter account. You sign in once with OAuth instead of managing separate provider keys, and every session inherits your OpenRouter models, credits, and organization guardrails.
- You sign in through OpenRouter with OAuth PKCE, so there's no API key to create or paste, and one login covers every supported agent.
- `ori harness setup` writes OpenRouter settings into each agent's own config so its desktop app and plain command both route through OpenRouter, and `ori harness reset` reverts that.
- Billing and guardrails stay on OpenRouter's side: workspace budgets, allowlists, and ZDR-only routing apply to all traffic, and usage shows up in normal OpenRouter billing with no separate Ori bill.
Ori is OpenRouter's command-line launcher for coding agents. You run `ori <agent>` instead of the agent's usual command, and Ori starts the agent with your OpenRouter credentials and org settings applied to that one session. It works with a long list of harnesses, including Claude Code, Codex, Cline, Kilo Code, OpenCode, Pi, Grok Build, Hermes, and DeepSeek Harness, and installs on macOS, Linux, WSL, and Windows PowerShell. Login is OAuth PKCE through your existing OpenRouter account, so there's no API key to create or paste. If you want OpenRouter to be the default for an agent's desktop app as well as its terminal command, `ori harness setup` writes the settings into that agent's own config, and `ori harness reset` undoes it. That setup only covers the listed harnesses, needs a saved `ori login` rather than a shell variable, and stops if your organization manages Claude settings, in which case you should use `ori claude` instead.
Model selection works the same way everywhere: pass `--model` with any OpenRouter model ID. Ori adds an `openrouter/` prefix automatically for Kilo Code and omp, which expect provider-scoped IDs, and defaults Kilo Code to `openrouter/auto` when you don't specify one. Pi, Prime Agent, and DeepSeek Harness get a richer integration: their in-session `/model` lists pull from your live OpenRouter catalog, and they add toggles for fast routing (`/fast`, or `/speed` on Prime Agent) and ZDR-only mode (`/zdr`). Grok Build and Muse Code get the catalog loaded into their model pickers but no toggles. The rest, including Claude Code, Cline, Codex, Hermes, omp, and OpenCode, have no hook for in-session changes, so Ori checks your `--model` value against the catalog at launch, corrects near-miss slugs with a notice, and passes unknown IDs through unchanged.
On the cost and control side, guardrails, allowlists, per-workspace permissions, and budgets are set on your OpenRouter organization and apply to every request regardless of which client sends it. Ori traffic bills through normal OpenRouter billing and shows up in Usage Accounting and Activity Export alongside everything else, so there's no separate Ori invoice to reconcile. The guide also includes a line that's easy to miss: for Claude Desktop specifically, you don't need Ori at all, since it connects to OpenRouter natively in gateway mode with an API key.