nito claude and nito codex open a harness session that runs entirely through Nito, from your terminal. They are the command line tool form of the in-chat session command: the harness runs normally, but every model turn goes to Nito instead of the harness’s own provider.
Each launcher runs in an isolated profile. Your ordinary Claude Code or Codex configuration, credentials, and history are not touched, and exiting returns you to your normal setup.
Fully Nito-routed sessions require a paid plan with full-session access enabled for your organization. See What Paid Unlocks.
Claude
-- is passed straight through to Claude Code.
Options
The privacy flags mirror the in-chat Private command. Read Private for exactly what each one does and does not guarantee:
--ephemeral-history is not the same as never writing to disk, and --skip-permissions is not a sandbox.
Codex
-- is passed straight through to Codex.
Options
nito codex is a Nito-routed session, so it needs only your Nito sign-in, not an OpenAI login. It does not accept the Private-only flags (--private, --ephemeral-history, --skip-permissions); those belong to nito claude.Choosing the Model
Both launchers require--model. List the certified session models available to your account with:
:encrypted model cannot, because Encrypted is coming soon and the client refuses it on every path, not only in sessions. See Models for the catalog and Privacy Levels for what each level reaches.
Relationship to the In-Chat Command
nito claude / nito codex and /nito:session / $nito:session open the same kind of isolated Nito-routed session. Use the plugin command when you are already in a chat; use the command line tool launcher when you want to start one from a script, an alias, or a fresh terminal.
Related
Session command
The in-chat equivalent and how sessions keep history.
Choosing a Model
Which models can power a session, and how to pick one.