Skip to main content
nito agent manages the credential the terminal uses and the default model your calls run on. Sign-in happens in your browser, and the credential is stored in your operating system keychain, never a password in the terminal.

​
Creating an Account

If you do not have a Nito account yet, start signup from the terminal. It opens your browser to the signup page:
Use --no-browser on a headless machine or over SSH, then open the printed URL wherever you have a browser. Once your account exists, sign in with nito agent login below.

​
Signing In

There is one credential for everyday use. How you create it depends on how you use Nito, and both paths open your browser for approval and store only a credential reference in your operating system keychain, never a password in the terminal. Using the plugin inside Claude Code or Codex? Sign-in is part of setup. Installing the host integration signs you in at the same time:
Setup opens your browser once. Sign in and approve, and your keychain credential is created. See Install in Claude Code. Using the terminal directly (nito ask, nito fusion, the MCP bridge)? Sign in with nito agent:
Both paths land on the same agent credential, so you do not sign in twice. nito agent status reports your profile, environment, authentication method, plan, and subscription state. Run it first whenever a command says you are not connected.
Nito never asks for a password in the terminal. Approval always happens in the browser, and only a credential reference is kept locally. On a headless machine or over SSH, nito agent login --method api-key --stdin reads an API key from standard input instead of opening a browser.

​
Signing In to the Gateway Directly

nito auth login signs the CLI in to the Nito gateway on its own, separate from the agent credential above. It targets the default Nito gateway, and --base-url points it at a specific one. Most plugin and terminal users only need nito agent login; reach for this when you are signing the CLI in to a particular gateway.

​
Browsing Models

List the models your account can use, with their privacy level and capabilities:
Each row shows the logical model ID (what you pass to --model), its privacy level, and what it supports. See Choosing a Model for how to pick one, and Models for the full catalog.

​
Setting a Default Model

The default applies to terminal calls that do not pass --model (for example a bare nito ask).
A per-call --model always wins over the default. The default does not change the model your harness runs, only the model your direct Nito calls use.

​
Options

Choosing a Model

How the saved default works with per-call overrides.

Nito CLI

Install, the command index, and the terminal front door.