”zsh: no matches found” or “command not found” when I type $nito or /nito
You are typing the command in your terminal shell instead of inside a session. Plugin commands only work inside a running Claude Code or Codex session.- Start your harness (
claudeorcodex), then type the command at the harness’s prompt. - To run Nito from the terminal on purpose, use the CLI:
nito ask "...".
In some shells the
$ in $nito: is read as a variable. That is another sign the command is being typed in the shell rather than in a Codex session.Typing $ in Codex does not show Nito commands
The$nito: commands are invoked by typing them, not from an autocomplete popup. Type the full command (for example $nito:ask your question) at the Codex prompt. If nothing happens at all, confirm the plugin is installed and trusted with nito doctor.
A command says Nito is not connected
The plugin shows a specific recovery action rather than failing silently. Do the step it names, then re-run your original command once. The plugin does not auto-replay a possibly billable request, so the retry is yours to make. If it keeps happening:1
Check
Run
nito doctor in your terminal and read what it flags.2
Sign in
Run
nito agent login, then confirm with nito agent status.3
Repair
If an integration is broken, run
nito doctor --repair, then re-run the command that failed.Codex shows a hooks or trust warning at startup
Codex warns about hooks the first time. This is Codex’s own trust step, separate from Nito sign-in. Approve it so the Nito hooks can run. It does not mean anything is wrong with your Nito account.”Nito Private was blocked because its bundled hook was unavailable”
private relies on a Codex hook to keep the turn out of your harness’s view. Until you trust that hook, the plugin fails closed: it blocks the private request rather than risk sending it through unprotected. That is the privacy guarantee working, not a failure.
To fix it, trust the hook from inside the Codex session:
1
Open the hooks menu
At the Codex prompt, type
/hooks.2
Trust the Nito hook
Find the bundled Nito hook and trust (enable) it.
3
Retry in a fresh turn
Run your
$nito:private command again. It now goes through, and the harness does not see the turn.private (and session-style privacy) needs this hook. ask, status, and models work without it. A successful private turn reports Session mode: Incognito and is handled by Nito rather than your harness.
”text.verbosity is not supported” in a Nito-routed Codex session
This was a compatibility issue between a recent Codex release and the gateway: Codex sent a verbosity setting the gateway rejected, which failed the request. It was not a problem with your account or sign-in, and it has since been fixed on the gateway. If you still see it:- Run
nito updateto make sure your integration is current, then retry. - In the meantime, the in-chat
$nito:commands ($nito:ask,$nito:private, and so on) inside your normal Codex session are unaffected.
Setup only asked me to sign in once
That is expected. Setup authorizes two credentials (Local CLI and Hosted) and skips whichever is already signed in. If you had one from an earlier install, you only see the other. Confirm both are healthy withnito doctor.
The plugin seems out of date after an update
Runnito update to upgrade the binary and refresh the managed integrations so the plugin bundle matches the new version. If only the integrations drifted, nito update --skip-binary re-syncs them without touching the binary. See Doctor and Update.
Something else
- Reinstall or reconnect a harness: Install Claude Code, Install Codex.
- Confirm your whole setup end to end: Check Your Setup.
- Understand what each command does: Command Index.