Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (omnizen-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

omnizen — CLI

One key. Every frontier model. Drop into the tools you already use — OpenCode, Claude Code, Cline, or any OpenAI / Anthropic-compatible SDK.

Install

# macOS / Linux / WSL
curl -fsSL https://omnizen.ai/install.sh | sh

# Windows (PowerShell)
irm https://omnizen.ai/install.ps1 | iex

# Or, directly with your package manager
npm install -g omnizen-cli
pnpm add -g omnizen-cli
yarn global add omnizen-cli
bun add -g omnizen-cli

# Or, zero-install — fetches on demand each time
npx omnizen-cli login

All install paths above need Node 20+ on PATH. A standalone native binary (no Node required) and winget install omnizen-cli / brew install omnizen are tracked as a follow-up.

omnizen login

Opens your browser, signs you in via Omnizen, and writes a default API key to ~/.omnizen/config.json (mode 0600). After that:

omnizen launch opencode      # spawns OpenCode with your key set
omnizen launch claude-code   # spawns Anthropic's Claude Code CLI
omnizen launch cline         # prints the env vars to export into VS Code

Commands

Command	What it does
`omnizen login`	OAuth-style device-flow sign-in. Browser-based, no key copy-paste.
`omnizen launch <tool>`	Run a supported tool with `OPENAI_API_KEY` / `ANTHROPIC_API_KEY` etc.
`omnizen whoami`	Print the signed-in user, the masked key, and the config path.
`omnizen logout`	Delete the local config. Rotate the key from the dashboard if needed.
`omnizen --version`	Print the installed CLI version.
`omnizen --help`	Print the usage summary.

Environment

Var	Effect
`OMNIZEN_APP_URL`	Override the gateway URL (default `https://omnizen.ai`).

Supported tools

Phase 1 ships these because the integration is verified against the gateway end-to-end. The list will grow as more get tested:

OpenCode — omnizen launch opencode
Claude Code — omnizen launch claude-code
Cline — omnizen launch cline (prints env vars; restart VS Code)

Need a tool that's not on the list? Run omnizen whoami to grab your key + base URL and set them yourself — any OpenAI/Anthropic-compatible client works against https://api.omnizen.ai/v1.

How it works

omnizen login calls POST /api/cli/auth/start to get a device_code (kept secret on disk) and a user_code (shown to you).
Your browser opens to omnizen.ai/connect?code=<user_code>. You sign in with Clerk, see the IP + UA of the CLI that asked, and click Approve.
The CLI polls /api/cli/auth/poll every 2s. As soon as the page approves, the poll endpoint returns your default API key + the gateway base URL, and the CLI writes them to ~/.omnizen/config.json.

The standard flow is OAuth 2.0 device-authorization-grant (RFC 8628). The CLI never opens a localhost listener — works fine on remote shells, inside containers, or behind firewalls.

omnizen-cli