mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-19 05:32:19 +03:00
0a74bfbdea
- canonical executable manifest (bin/cli/cli-manifest.mjs): run/configure/completion derive targets, aliases and --model wiring from one table; drift test cross-checks manifest x cliRuntime x UI catalog (tests/unit/cli/cli-manifest-drift.test.ts) - dashboard Codex generator converged to ~/.codex/config.toml (modern Codex v0.137+, verified against codex-cli 0.147.0): conservative merge, env_key auth (key never written), refuses invalid TOML, reports legacy config.yaml as migration note - omniroute run gemini: launcher over OmniRoute's /v1beta surface via GOOGLE_GEMINI_BASE_URL + isolated GEMINI_CLI_HOME forcing gemini-api-key auth (contract proven against @google/gemini-cli 0.50.0); ACP registration kept distinct - opt-in real smoke harness for upstream CLIs (RUN_CLI_SMOKE=1, credential by env NAME, redacted output): tests/integration/upstream-cli-smoke.int.test.ts - container-guard homologation for POST /api/cli-tools/apply (422 in container, dry-run preview allowed, host write passes) + docs; guard untouched - typecheck: omniglyphAdapter union narrowing, usageTracking typed signatures (UsageLike, no any), models.ts isValidModel params — typecheck:core and typecheck:noimplicit:core now clean - relay core (prior session of this effort): omniroute run for 6 CLIs, configure picker with per-context favorites/recents, contexts with optional keychain + 0600 fallback, provider CRUD with recursive redaction, completion updates, docs
297 lines
18 KiB
Markdown
297 lines
18 KiB
Markdown
---
|
|
title: "CLI Integrations — point any coding CLI at OmniRoute"
|
|
version: 3.8.40
|
|
lastUpdated: 2026-06-28
|
|
---
|
|
|
|
# CLI Integrations
|
|
|
|
OmniRoute ships a family of `setup-*` commands that configure a coding
|
|
CLI (Codex, Claude Code, OpenCode, Cline, …) to use OmniRoute as its backend — so
|
|
the tool talks to **one** endpoint and OmniRoute routes to the right provider with
|
|
auto-fallback. Each command reads the **live** model catalog from a running
|
|
OmniRoute (local or remote) and writes the tool's own config file on **your**
|
|
machine. The API key is referenced by an environment variable wherever the tool
|
|
supports it. Commands that persist a tool-local environment file are noted below.
|
|
|
|
There are also two launchers — `omniroute launch` (Claude Code) and
|
|
`omniroute launch-codex` (Codex) — that spawn the CLI with the right env injected,
|
|
without writing any config at all.
|
|
|
|
Provider onboarding is available from the same local/remote context. The
|
|
API-first commands below keep management authentication separate from provider
|
|
credentials and never print a credential in structured output:
|
|
|
|
```bash
|
|
omniroute providers add glm --credential-env GLM_API_KEY --name work
|
|
omniroute providers import ./providers.json --dry-run --json
|
|
omniroute providers auth openai
|
|
omniroute providers edit <connection-id> --default-model glm/glm-5.2
|
|
omniroute providers remove <connection-id> --yes
|
|
```
|
|
|
|
For scripts, prefer `--credential-stdin` or `--credential-env`; `--credential`
|
|
is retained for controlled local use. `providers remove` requires `--yes` on a
|
|
non-interactive terminal, and all five commands honor the active context or the
|
|
global `--base-url`/`--api-key` options.
|
|
|
|
For the one-time, hand-written base setup of the two richest integrations, see the
|
|
per-tool deep dives:
|
|
|
|
- [Claude Code configuration](./CLAUDE-CODE-CONFIGURATION.md)
|
|
- [Codex CLI configuration](./CODEX-CLI-CONFIGURATION.md)
|
|
- [Remote Mode](./REMOTE-MODE.md) — drive a remote OmniRoute (VPS / Tailnet) from your laptop
|
|
- [VS Code Copilot Chat](./VSCODE-COPILOT.md) — the OmniCopilot extension; it can also run these
|
|
`setup-*` commands for you from inside the editor
|
|
|
|
---
|
|
|
|
## Master table
|
|
|
|
Every command honours the **active context** (set with `omniroute connect`, see
|
|
[Remote Mode](./REMOTE-MODE.md)) or explicit `--remote <url> --api-key <key>` flags.
|
|
"Local vs remote" below means: with no flags it targets `http://localhost:20128`;
|
|
with `--remote` (or an active remote context) it fetches the catalog from that
|
|
server and writes the config locally.
|
|
|
|
| Command | Tool | What it writes | Key flags | Local vs remote |
|
|
| -------------------------- | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | --------------- |
|
|
| `omniroute setup-codex` | OpenAI Codex CLI | `~/.codex/<name>.config.toml` — one profile per compatible text model (`codex --profile <name>`) | `--remote` `--api-key` `--only` `--dry-run` `--port` `--codex-home` | Both |
|
|
| `omniroute setup-claude` | Claude Code | `~/.claude/profiles/<name>/settings.json` — one profile per matched model (`CLAUDE_CONFIG_DIR`) | `--remote` `--api-key` `--only` `--dry-run` `--port` `--claude-home` | Both |
|
|
| `omniroute setup-opencode` | OpenCode (openai-compatible) | `~/.config/opencode/opencode.json` — `omniroute` provider with every catalog model (`opencode -m omniroute/<model>`) | `--remote` `--api-key` `--only` `--model` `--dry-run` `--port` | Both |
|
|
| `omniroute setup-cline` | Cline | `~/.cline/data/{globalState,secrets}.json` (CLI mode) + prints VS Code extension settings | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--cline-dir` | Both |
|
|
| `omniroute setup-kilo` | Kilo Code | `~/.local/share/kilo/auth.json` (CLI) + merges `kilocode.*` into VS Code `settings.json` if present | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--auth-path` `--vscode-settings` | Both |
|
|
| `omniroute setup-continue` | Continue / `cn` CLI | `~/.continue/config.yaml` — `provider: openai` models, key via `${{ secrets.OMNIROUTE_API_KEY }}` | `--remote` `--api-key` `--only` `--dry-run` `--port` `--config-path` | Both |
|
|
| `omniroute setup-cursor` | Cursor | Nothing — prints the in-app steps (Cursor config is opaque SQLite) | `--remote` `--api-key` `--only` `--port` | Both |
|
|
| `omniroute setup-roo` | Roo Code | `~/.omniroute/roo-settings.json` (import doc) + sets `roo-cline.autoImportSettingsPath` if a VS Code `settings.json` exists | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--import-path` `--vscode-settings` | Both |
|
|
| `omniroute setup-crush` | Crush | `~/.config/crush/crush.json` — `openai-compat` provider, key via `$OMNIROUTE_API_KEY` | `--remote` `--api-key` `--only` `--dry-run` `--port` `--config-path` | Both |
|
|
| `omniroute setup-goose` | Goose | `~/.config/goose/config.yaml` (`GOOSE_PROVIDER`/`OPENAI_HOST`/`GOOSE_MODEL`) + prints env recipe | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--config-path` | Both |
|
|
| `omniroute setup-aider` | Aider | `~/.aider.conf.yml` (`openai-api-base` + `model: openai/<id>`) + prints env recipe | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--config-path` | Both |
|
|
| `omniroute setup-qwen` | Qwen Code | `~/.qwen/settings.json` — V4 `modelProviders.openai` array + `OMNIROUTE_API_KEY` in `~/.qwen/.env` | `--remote` `--api-key` `--model` `--yes` `--dry-run` `--port` `--config-path` `--env-path` | Both |
|
|
| `omniroute run <target>` | Runtime launch (generic) | Nothing — spawn `claude`/`codex`/`aider`/`goose`/`opencode`/`qwen` with the right env and args; Qwen uses a temporary isolated home | `--remote` `--base-url` `--context` `--provider` `--model` `--api-key` `--api-key-env` `--dry-run` `--json` `--port` `--profile` `--token` | Both |
|
|
| `omniroute launch` | Claude Code | Nothing — spawns `claude` with `ANTHROPIC_BASE_URL`/`ANTHROPIC_AUTH_TOKEN` injected | `--remote` `--api-key` `--token` `--profile` `--port` | Both |
|
|
| `omniroute launch-codex` | OpenAI Codex CLI | Nothing — spawns `codex` with the `omniroute` provider injected via `-c` flags | `--remote` `--api-key` `--profile` (`-p`) `--port` | Both |
|
|
|
|
Notes on flags (verified in the command source):
|
|
|
|
- `--remote <url>` — fetch the catalog from a remote OmniRoute (overrides `--port`
|
|
and the active context). `--api-key <key>` supplies the credential for that
|
|
server (defaults to the `OMNIROUTE_API_KEY` env var, or the active context's token).
|
|
- `--only <patterns>` — comma-separated substrings; keep only model IDs that match
|
|
(e.g. `--only glm,kimi`). Available on `setup-codex`, `setup-claude`,
|
|
`setup-opencode`, `setup-continue`, `setup-cursor`, `setup-crush`.
|
|
- `--dry-run` — print exactly what would be written without touching the
|
|
filesystem. Available on every `setup-*` command **except** `setup-cursor`
|
|
(which never writes a file).
|
|
- `--model <id>` — required (or picked interactively) for the tools that have no
|
|
model auto-discovery: Cline, Kilo, Roo, Goose, Qwen, Aider. Those tools
|
|
also accept `--yes` for non-interactive runs (which then requires `--model`).
|
|
`setup-opencode` takes `--model` to set the default top-level model.
|
|
- `--port <port>` — local OmniRoute port (default `20128`, ignored when `--remote`
|
|
is set). Present on all `setup-*` and both launchers.
|
|
- The two launchers (`launch`, `launch-codex`) accept `--profile <name>` to select
|
|
a profile written by `setup-claude` / `setup-codex`, plus pass-through args for
|
|
the underlying `claude` / `codex` binary.
|
|
|
|
The interactive picker is also shared by the setup recipes:
|
|
|
|
```bash
|
|
# Pick from the active local or remote model catalog and configure the target.
|
|
omniroute configure claude
|
|
omniroute configure opencode --provider glm
|
|
omniroute configure qwen --model qwen/qwen3.8-max-preview --yes
|
|
```
|
|
|
|
`configure` currently delegates to the tested recipes for `codex`, `claude`,
|
|
`opencode`, `qwen`, `aider`, `goose`, `cline`, `continue`, and `kilo`. IDE-only,
|
|
MITM, and guide-only catalog entries remain explicit `setup-*`/manual flows and
|
|
are not presented as launchable targets.
|
|
|
|
> `setup-opencode` is the **lightweight openai-compatible** OpenCode integration.
|
|
> There is also a richer plugin integration — `omniroute setup opencode` — which
|
|
> installs `@omniroute/opencode-plugin`. They are different commands; the table
|
|
> above documents `setup-opencode`.
|
|
|
|
---
|
|
|
|
## Local usage
|
|
|
|
With OmniRoute running on `localhost:20128`, just run the setup command for your
|
|
tool. The catalog is fetched from the local server.
|
|
|
|
```bash
|
|
# Codex: write a profile per matched model into ~/.codex/
|
|
omniroute setup-codex
|
|
codex --profile glm52 # use a generated profile
|
|
|
|
# Claude Code: write per-model profiles, then launch one
|
|
omniroute setup-claude
|
|
omniroute launch --profile glm52
|
|
|
|
# OpenCode: write the openai-compatible provider with all catalog models
|
|
omniroute setup-opencode
|
|
export OMNIROUTE_API_KEY=sk-... # referenced via {env:OMNIROUTE_API_KEY}, never on disk
|
|
opencode -m omniroute/glm/glm-5.2 "..."
|
|
|
|
# Tools without auto-discovery need an explicit model:
|
|
omniroute setup-aider --model glm/glm-5.2
|
|
omniroute setup-qwen --model qwen/qwen3.8-max-preview
|
|
|
|
# Preview without writing anything:
|
|
omniroute setup-continue --dry-run
|
|
```
|
|
|
|
Launch without writing any config at all (env-injection only):
|
|
|
|
```bash
|
|
omniroute launch # Claude Code → local OmniRoute
|
|
omniroute launch-codex # Codex CLI → local OmniRoute
|
|
omniroute launch-codex --profile glm52
|
|
omniroute run claude --model openai/gpt-5.4
|
|
omniroute run codex --model openai/gpt-5.4 --dry-run --json
|
|
omniroute run aider --model glm/glm-5.2 -- --message "reply OK"
|
|
omniroute run goose --model glm/glm-5.2
|
|
omniroute run opencode --model glm/glm-5.2 -- run "reply OK"
|
|
omniroute run qwen --model glm/glm-5.2 -- -p "reply OK"
|
|
|
|
# Explicit command path: pass through whatever comes after --
|
|
omniroute run claude -- --print-system-prompt "review this diff"
|
|
```
|
|
|
|
---
|
|
|
|
## Remote usage
|
|
|
|
Point any setup command at a remote OmniRoute with `--remote` + `--api-key`. The
|
|
catalog is fetched from the remote; the config is written on your local machine.
|
|
|
|
```bash
|
|
# OpenCode against a remote VPS, keep only glm/kimi models
|
|
omniroute setup-opencode --remote http://192.168.0.15:20128 --api-key oma_live_xxx \
|
|
--only glm,kimi
|
|
opencode -m omniroute/glm/glm-5.2 "..." # export OMNIROUTE_API_KEY first
|
|
|
|
# Codex profiles from a remote catalog
|
|
omniroute setup-codex --remote http://192.168.0.15:20128 --api-key oma_live_xxx
|
|
|
|
# Launch a CLI straight against the remote
|
|
omniroute launch --remote http://192.168.0.15:20128 --api-key oma_live_xxx
|
|
omniroute launch-codex --remote http://192.168.0.15:20128 --api-key oma_live_xxx
|
|
```
|
|
|
|
Instead of passing `--remote`/`--api-key` every time, log in once and let the
|
|
**active context** supply them automatically:
|
|
|
|
```bash
|
|
omniroute connect 192.168.0.15 # mints a scoped token, stores the context
|
|
omniroute setup-codex # ← now uses the remote catalog
|
|
omniroute setup-opencode # ← same
|
|
omniroute launch # ← Claude Code against the remote
|
|
```
|
|
|
|
See [Remote Mode](./REMOTE-MODE.md) for contexts, scopes, and token management.
|
|
|
|
---
|
|
|
|
## Base URL conventions (which tools want `/v1`)
|
|
|
|
OmniRoute exposes the OpenAI surface at `/v1`, the Anthropic surface at the root,
|
|
and a native Gemini surface at `/v1beta`. Each integration is wired to the form its
|
|
tool expects (verified in the command source):
|
|
|
|
| Integration | Base URL written | `/v1`? |
|
|
| -------------------------------------------------------------------------- | ---------------- | ------------------------------------------- |
|
|
| `setup-cline` (`openAiBaseUrl`) | root | No — Cline appends `/v1/chat/completions` |
|
|
| `setup-goose` (`OPENAI_HOST`) | root | No — Goose appends the path |
|
|
| `setup-aider` (`OPENAI_API_BASE`) | root | No — LiteLLM appends `/v1/chat/completions` |
|
|
| `setup-kilo`, `setup-roo`, `setup-continue`, `setup-crush`, `setup-cursor` | with `/v1` | Yes |
|
|
| `setup-claude` (`ANTHROPIC_BASE_URL`), `launch` | root | No — Claude Code appends `/v1/messages` |
|
|
| `setup-codex`, `launch-codex` (`model_providers.omniroute.base_url`) | with `/v1` | Yes |
|
|
| `setup-qwen` (`modelProviders.openai[].baseUrl`) | with `/v1` | Yes |
|
|
|
|
---
|
|
|
|
## Keeping native deps on update: `--include=optional`
|
|
|
|
When you update with `omniroute update` (after confirming, or with `--apply`),
|
|
OmniRoute runs the install with `--include=optional` baked in:
|
|
|
|
```bash
|
|
npm install -g omniroute@latest --include=optional
|
|
```
|
|
|
|
This is **not** a flag you pass to `omniroute update` — it is always applied by the
|
|
updater. It guarantees the `optionalDependencies` (`better-sqlite3`, `keytar`,
|
|
`tls-client`, the LLMLingua SLM stack) survive the update even if your npm config
|
|
has `omit=optional` set, which would otherwise silently drop the native SQLite
|
|
driver and OS-keyring binding. To preview the exact command without applying:
|
|
|
|
```bash
|
|
omniroute update --dry-run
|
|
# [DRY RUN] Would run: npm install -g omniroute@latest --include=optional
|
|
```
|
|
|
|
Other `omniroute update` flags (verified in source): `--check` (exit 1 if
|
|
outdated), `--apply` (install without prompting), `--changelog`, `--no-backup`,
|
|
`--yes`.
|
|
|
|
---
|
|
|
|
## Google Gemini CLI via `omniroute run gemini`
|
|
|
|
Contract verified against `@google/gemini-cli` 0.50.0: the CLI honors
|
|
`GOOGLE_GEMINI_BASE_URL` and issues `POST /v1beta/models/<model>:generateContent`
|
|
(and `:streamGenerateContent?alt=sse`) against it — exactly OmniRoute's native
|
|
Gemini surface (`/v1beta`). `omniroute run gemini` wires that automatically:
|
|
|
|
- `GOOGLE_GEMINI_BASE_URL` → the active OmniRoute base URL (root, no `/v1`);
|
|
- `GEMINI_API_KEY` → the resolved OmniRoute credential (option/env/context);
|
|
- a **temporary isolated `GEMINI_CLI_HOME`** whose `.gemini/settings.json`
|
|
selects `gemini-api-key` auth, so a stored Google OAuth session (Code Assist)
|
|
never overrides the OmniRoute-directed launch — removed after exit;
|
|
- `--model <id>` injection from `--provider`/`--model`.
|
|
|
|
```bash
|
|
omniroute run gemini --model glm/glm-5.2 -- --skip-trust -p "hello"
|
|
```
|
|
|
|
Gemini's workspace-trust guard still applies in headless mode — pass
|
|
`--skip-trust` (or trust the directory interactively) yourself; the launcher
|
|
deliberately does not bypass it. This launcher is distinct from the **ACP
|
|
registration** (`src/lib/acp/registry.ts`, `gemini --acp`), which remains the
|
|
agent-protocol integration for `/dashboard/acp-agents`.
|
|
|
|
---
|
|
|
|
## Real smoke sweep (opt-in)
|
|
|
|
Deterministic launch-plan regression runs in CI (`tests/unit/cli/run-command.test.ts`,
|
|
`tests/unit/cli/run-execution.test.ts`). To validate the REAL binaries against a REAL
|
|
OmniRoute server, an opt-in harness exists at
|
|
`tests/integration/upstream-cli-smoke.int.test.ts`. It never runs automatically
|
|
(every sub-test skips unless `RUN_CLI_SMOKE=1`), passes the credential by env-var
|
|
NAME (never by value), redacts key-shaped strings from any recorded output, skips
|
|
targets whose binary is not installed, and classifies failures as
|
|
auth / upstream / config instead of a bare boolean:
|
|
|
|
```bash
|
|
RUN_CLI_SMOKE=1 \
|
|
OMNIROUTE_SMOKE_BASE_URL="http://localhost:20128" \
|
|
OMNIROUTE_SMOKE_MODEL="<provider/model>" \
|
|
OMNIROUTE_SMOKE_API_KEY_ENV="OMNIROUTE_API_KEY" \
|
|
node --import tsx/esm --test tests/integration/upstream-cli-smoke.int.test.ts
|
|
```
|
|
|
|
Optional: `OMNIROUTE_SMOKE_TARGETS="codex,opencode,qwen"` restricts the sweep;
|
|
`OMNIROUTE_SMOKE_TIMEOUT_MS` overrides the 120s per-target timeout.
|
|
|
|
---
|
|
|
|
## See also
|
|
|
|
- [Claude Code configuration](./CLAUDE-CODE-CONFIGURATION.md) — the deeper Claude Code guide
|
|
- [Codex CLI configuration](./CODEX-CLI-CONFIGURATION.md) — the one-time `[model_providers.omniroute]` base setup
|
|
- [Remote Mode](./REMOTE-MODE.md) — contexts, scoped access tokens, driving a remote server
|
|
- [CLI Tools reference](../reference/CLI-TOOLS.md) — the full catalog of supported tools + dashboard pages
|
|
- [Setup Guide](./SETUP_GUIDE.md) — install methods and first-run onboarding
|