nito doctor tells you what is wrong, and nito update keeps everything current.
Doctor
doctor checks your Nito installation, your stored credentials, and each harness integration, then reports what passed and what needs attention. Run it first whenever a command misbehaves.
By default it also sends a short, billable chat request to confirm end-to-end connectivity. That real request is the difference between “credentials look valid” and “a prompt actually reaches a model and comes back.”
Options
Use
--skip-smoke when you only want to inspect local state, or want to avoid the small charge. Use --repair when doctor reports a broken or stale integration and you want it cleaned up:
--repair changes local state and removes old integrations. Run a plain nito doctor first to see what it will act on, then re-run with --repair.Update
update upgrades the Nito binary through your package manager and refreshes the managed harness integrations so the plugin bundle and hooks match the new version.
Options
Run a normal
nito update to move to a new release. Use --skip-binary when the binary is already current (for example it was upgraded by your package manager directly) but you still want the integrations re-synced:
A Good Recovery Order
When something is not working, this sequence resolves most problems:1
Check
Run
nito doctor and read what it flags.2
Sign in
If it reports a credential problem, run
nito agent login and check again with nito agent status.3
Update
If the install or integrations are out of date, run
nito update.4
Repair
If an integration is still broken, run
nito doctor --repair, then re-run the command that failed.Related
Troubleshooting
Symptom-first fixes for common problems.
Update and Uninstall
Keeping Nito current and removing it cleanly.