Context
By default, Nito receives only the prompt you type.context lets you opt into sending more, and check what the current setting is.
- Claude Code
- Codex
onlets futureaskcalls include a short, harness-generated summary of the relevant task or conversation. It is a generated summary, not a verbatim transcript.offreturns to prompt-only.statusreports the current preference.
What Is and Is Not Sent
- By default: only your prompt.
- With context on: your prompt plus a short generated summary, for
askonly. It does not affect Fusion, and it never changes your harness’s active model. - A per-call
--historyor--no-historyonaskoverrides this preference for that call.
Why It Is Best-Effort
The preference lives in your visible conversation state, so it is not durable. It can reset after things like a restart, sign-out, a new conversation, or a context compaction. Treat it as a per-conversation convenience, not a persistent account setting, and confirm it withcontext status when it matters.
Mode
- Claude Code
- Codex
mode reports how the current conversation is routed. By default your conversation is in explicit-ask mode: your harness stays primary and only reaches Nito when you run a Nito command. Fully Nito-routed work happens in a separate process you start with session; entering or leaving that cannot switch your current conversation or move hidden state into it.
