Install Noria, sign in to isolated accounts, and route your first native coding session.

Noria runs on your machine between your native coding clients and the accounts you sign in. A session stays with its assigned account until an applicable limit makes that account unavailable.

1. Install

npm install -g @amxv/noria
noria --version
noria --help

The npm installer downloads the native binary for your platform from GitHub Releases. macOS, Linux, and Windows each have amd64 and arm64 builds. If the download fails, installation can fall back to a local Go build when Go is available. You can also download the matching binary directly from a release.

Install the native codex or claude executable for the provider you want to use. Noria does not replace either client. Claude quota reads use the installed claude binary directly; no SDK or additional runtime installation is needed.

Node is only needed to invoke the npm installation shim. A directly downloaded Go binary can route both Codex and Claude without Node or npm. Existing provider subscriptions and explicit authorization to use each account are prerequisites; Noria does not create them.

2. Create your local configuration

noria init

The default home is ~/.noria; set NORIA_HOME before running Noria to use another location. Initialization creates private local configuration and a random gateway secret. The default gateway address is http://127.0.0.1:43119.

3. Add and sign in to your accounts

For Codex:

noria account add codex-work --provider codex
noria account login codex-work
noria account add codex-personal --provider codex
noria account login codex-personal

For Claude Code:

noria account add claude-work --provider claude
noria account login claude-work

Each login opens the provider’s native interactive sign-in flow for an isolated Noria account profile. You complete the sign-in yourself. Noria does not import your normal client credentials. One account is enough to start; automatic failover needs another usable account for the same provider and requested model.

Claude quota reads use a control-only process of the installed claude executable. Noria sends no user prompts or model calls for telemetry. The protocol remains experimental and may change with Claude Code updates. See accounts and authentication.

4. Check availability

noria doctor
noria account list
noria quota refresh

Quota refresh reads provider telemetry. It does not send a dummy prompt, redeem reset credits, or turn unknown quota into a full allowance. A failed or incomplete read needs attention; see troubleshooting.

5. Start the gateway

Keep this terminal open:

noria serve

In another terminal, use the same NORIA_HOME and start a client:

noria run codex --

Or:

noria run claude --

The wrapper supplies routing configuration to the child process. Your existing client home, conversation history, skills, and settings remain in place. It does not persistently rewrite your normal client configuration. See native client integration for transport details and manual setup.

6. Inspect the route

noria status
noria status --json

Status is local operational metadata, not a transcript viewer. A healthy session keeps its account even when another account resets or has more headroom. After a necessary switch, the new account’s cache warms naturally.

Read how scheduling works and security and privacy before relying on a multi-account pool. Noria preserves the requested model and does not enable a paid fallback. When every matching account is unavailable, it reports that honestly. Actual live multi-account validation has not yet been performed; see compatibility.