> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trynito.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Doctor and Update

> Diagnose install, credential, and integration problems with nito doctor, and stay current with nito update.

Two commands keep a working install healthy: `nito doctor` tells you what is wrong, and `nito update` keeps everything current.

## Doctor

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
nito doctor [flags]
```

`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 makes no model call. Add `--smoke` to send a **short, billable chat request**, which is the difference between "credentials look valid" and "a prompt actually reaches a model and comes back."

### Options

| Flag | Effect |
| :- | :- |
| `--smoke` | Add the short billable chat request. |
| `--repair` | Repair local Nito state and remove legacy harness integrations. |

Use `--smoke` when you want proof that a request round-trips. Use `--repair` when `doctor` reports a broken or stale integration and you want it cleaned up:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
# Local checks, no billable request
nito doctor

# Add a live request
nito doctor --smoke

# Fix local state and drop legacy integrations
nito doctor --repair
```

`--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

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
nito update [flags]
```

`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

| Flag | Effect |
| :- | :- |
| `--skip-binary` | Skip the package-manager binary upgrade and only refresh the integrations. |

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:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
# Upgrade Nito and refresh integrations
nito update

# Only re-sync integrations (binary already current)
nito update --skip-binary
```

## Recovery Order

When something is not working, this sequence resolves most problems:

<Steps>
  <Step title="Check">
    Run `nito doctor` and read what it flags.
  </Step>

  <Step title="Sign in">
    If it reports a credential problem, run `nito agent login` and check again with `nito agent status`.
  </Step>

  <Step title="Update">
    If the install or integrations are out of date, run `nito update`.
  </Step>

  <Step title="Repair">
    If an integration is still broken, run `nito doctor --repair`, then re-run the command that failed.
  </Step>
</Steps>

For harness-specific reconnection inside a chat, see [When Tools Do Not Load in a Chat](/plugin/commands/status-and-account#when-tools-do-not-load-in-a-chat).

## Related

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="wrench" href="/help/plugin/troubleshooting">
    Symptom-first fixes for common problems.
  </Card>

  <Card title="Update and Uninstall" icon="arrows-rotate" href="/plugin/get-started/update">
    Keeping Nito current and removing it cleanly.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.