Ori Hermes: Hermes with OpenRouter
Run ori hermes to use Hermes with every model, your org guardrails, and one bill on OpenRouter
❯
01──Bring your own agent
One command runs the agent CLI you already have, with OpenRouter credentials, models, and environment set up for you. Your workflow does not change.
02──Sign in instead of managing keys
ori uses OAuth against your existing OpenRouter login, so there is no key to create or paste.
03──Any agent, any model
Swap the model with --model, or with the agent's own model flag where it has one. Everything after the flags goes to the agent untouched.
04──Guardrails, on every agent
Set allowlists, budgets, and permissions in your OpenRouter dashboard; they apply to every harness.
05──One bill across agents
Usage and spend from every agent land in your OpenRouter dashboard, on one bill.
06──faq
ori harness runs the agent CLI you already use on OpenRouter. `ori claude`,
`ori codex`, `ori grok`, `ori hermes`, `ori opencode`, `ori pi`, `ori
prime-agent`, `ori cline`, `ori kilo`, `ori omp`, `ori muse`, `ori zcode`,
`ori unreal`, `ori crush`, and `ori droid` each launch the real agent with
OpenRouter wired in: your models, your org guardrails, one bill. `ori dsh`
sets up DeepSeek Harness the same way and launches its web server. the
commands stay the same.
no. ori signs you in with OAuth (PKCE) on your existing OpenRouter login, so
there is no new account and no key to copy or paste. your models, credits, and
org settings are there immediately.
Claude Code (`ori claude`), Codex (`ori codex`), Grok Build (`ori grok`),
Hermes (`ori hermes`), OpenCode (`ori opencode`), Pi (`ori pi`), Prime Agent
(`ori prime-agent`), Cline (`ori cline`), Kilo Code (`ori kilo`), omp (`ori
omp`), Muse Code (`ori muse`), ZCode (`ori zcode`), Unreal Agent (`ori
unreal`), Crush (`ori crush`), Factory Droid (`ori droid`), and DeepSeek
Harness (`ori dsh`) today, with more harnesses on the way.
ori runs the agent CLI that's already on your PATH. if it isn't installed, ori
prompts you with how to install it and offers to do it for you right away.
DeepSeek Harness runs as a web server rather than a TUI, so `ori dsh`
configures your DeepSeek Harness under `$DSH_HOME` to serve OpenRouter, then
launches `dsh web` and prints its URL. the OpenRouter credential reaches only
that server, so a `dsh web` you start yourself needs its own key.
yes. pass `--model` with any OpenRouter model id. Grok Build, Crush, and
Factory Droid take their own model flag instead: `ori grok -m`, `ori crush run
-m`, and `ori droid exec -m`, or their model picker. everything after the
flags is forwarded to the agent untouched, so your usual commands still work.
no. keep the same agent and the same commands and flags you know. ori sits
underneath and adds model choice, guardrails, and one bill.
allowlists, budgets, and per-workspace permissions live on your OpenRouter org
and apply on every request. a model or spend outside policy is blocked before
it runs, whichever agent made the call.
run: curl -fsSL https://openrouter.ai/labs/ori/install.sh | bash
yes. if you use OpenRouter MCP, run /install-ori-harness in your agent to get
started, or ask it to run curl -fsSL
https://openrouter.ai/skills/install-ori-harness and follow the instructions
in its output.
run: ori update
get started❯