session opens a separate harness session in your current workspace that is powered entirely by a model through Nito. Unlike Private, it is meant to be lived in: it keeps your prompt history, transcripts, and project state, so you can work a task over many turns on a model through Nito instead of your harness’s default.
Syntax
- Claude Code
- Codex
--model, the session uses your saved default model. It does not accept an inline prompt or the Private-only options (--ephemeral-history, --skip-permissions).
Private vs. Session
They both route away from your harness’s default model, but they are opposites on persistence:
Use Private for a turn that should leave no trace; use Session for sustained work you want to keep, routed through Nito.
What Runs Inside a Session
A Nito session is a normal harness session with the model pinned to Nito:- Your harness’s native model picker works, restricted to eligible Nito chat models on the session’s privacy level so it cannot break the session’s guarantees.
- Your harness’s agents/subagents and tools work, running against the Nito catalog.
- Anonymous, Private, and Confidential models can power a session. An
:encryptedmodel cannot, because Encrypted is coming soon to the plugin and the client refuses it on every path, not only in sessions.
First-Release Notes
- Codex: wrapper-owned resume is not yet available. Transcripts and local state are retained in a dedicated Nito profile without changing your ordinary Codex configuration.
- Claude Code: the session runs with a dedicated local Nito profile. Some harness features that depend on the provider (for example newly-requested extended thinking and experimental betas) are disabled for this first release; visible assistant text and tool history are preserved.
- Exiting the session and launching your harness normally returns you to your ordinary model.