Provider seats & models
Local Codex seat, Anthropic policy-safe options, API keys, credits, and local models — what runs where.
Routes overview
On any host you choose how a turn is powered: a provider seat you signed into on that machine, a provider API key (BYOK), NOME credits, or a local model. NOME records which route ran each turn. It never silently falls back to a different route — if your chosen route can't run, NOME fails closed and tells you why.
Use provider seats on your own trusted computer or private workspace.
OpenAI Codex local seat
Sign in to the OpenAI Codex CLI on your own machine with its own flow (codex login). NOME detects the install and sign-in status through codex login status — exit codes only — and offers the seat as a route. When you pick it, NOME launches the Codex CLI on that machine to run the turn; you never open the Codex CLI yourself.
NOME cloud does not copy your ChatGPT/Codex subscription tokens. The sign-in stays in the Codex CLI's own config on your machine. The cloud-workspace Codex seat is not implemented — the seat runs only on a host where you signed in. Receipts record the auth lane and a provider-subscription cost lane, never the token.
OpenAI API and credits
For OpenAI without a seat, use an OpenAI API key (BYOK) and pay OpenAI directly, or use NOME credits on the managed lane. Both work on any host, including Cloud Workspaces. See BYOK & NOME Credits.
Anthropic: API, BYOK, and Vertex first
For Anthropic models, the supported routes are an Anthropic API key, BYOK, and Claude on Vertex. These are the policy-safe options and work on any host and in Cloud Workspaces.
NOME does not support Claude.ai / Claude Pro / Claude Max cloud login, and NOME does not store or copy Anthropic subscription tokens. Use an API key, BYOK, or Vertex for Anthropic in the cloud.
Claude Code local seat (policy-gated, host-local only)
A local Claude Code seat — running the Claude Code CLI you signed into on your own machine — is supported only as a host-local, policy-gated option. NOME detects sign-in status through the CLI's own claude auth status command (a status field, never credential material) and runs the turn on your machine.
It never runs in NOME cloud, it is gated by policy, and NOME never copies the Anthropic sign-in. If you don't have it enabled, use the API / BYOK / Vertex routes above.
DeepSeek, Vertex, and xAI
DeepSeek, Google Vertex, and xAI are available via API key (BYOK) or NOME credits, plus any OpenAI-compatible BYOK endpoint for custom or self-hosted models. They participate in the same run contract, receipts, and cost tracking as the built-in providers.
Local models
On a capable host, run a local model with no per-token cost and no network round-trip. On Apple Silicon, NOME MLX runs an on-device model after a one-time, login-gated download. Local runs use the same run contract and receipts; tool calls that require the network queue as deferred tasks until connectivity returns. Local execution consumes no NOME credits.
Seat policy summary
Quick reference for what runs where:
Codex seat · This Mac / owner-edge / your VM — supported, host-local; NOME stores status only.
Codex seat · NOME Cloud Workspace — not implemented; use credits or BYOK in the cloud.
OpenAI / DeepSeek / Vertex / xAI · API or credits — supported on any host.
Anthropic · API / BYOK / Vertex — supported on any host (policy-safe).
Claude Code seat · host-local — policy-gated, never in cloud.
Claude.ai / Claude Pro / Claude Max cloud login — not supported.
Ready to try it?
Open NOME