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

# Troubleshooting

> The usual suspects - cold start, the daemon, empty recall, and how to diagnose.

Start here - it diagnoses the install and runtime state:

```bash theme={null}
pmb doctor
```

## First recall is slow

The first recall after a fresh boot loads the embedding model (\~1-2s, the model
is \~450MB). Warm it once:

```bash theme={null}
pmb warmup
```

The daemon also prewarms in the background on boot. Subsequent recalls are
\~35ms warm.

## Recall returns nothing

<AccordionGroup>
  <Accordion title="The daemon isn't running">
    Intents/extraction are warm-only. `pmb daemon status`; start it with
    `pmb daemon start` (or `pmb setup`, which pins it warm).
  </Accordion>

  <Accordion title="Nothing's stored yet">
    `pmb stats` to check counts. A young workspace is genuinely empty - index a
    project (`pmb index project .`) or capture a few notes.
  </Accordion>

  <Accordion title="The query was filtered as trivial">
    Auto-recall stays quiet on trivial messages by design. Use `pmb recall "…"`
    directly from the terminal to bypass the gate.
  </Accordion>
</AccordionGroup>

## Port already in use

The dashboard and the MCP HTTP server both default to `8765`. Current PMB
versions auto-skip the default dashboard port when it is already busy:

```bash theme={null}
pmb dashboard
```

Use an explicit port when you want a fixed address:

```bash theme={null}
pmb dashboard --port 18888
```

## Stray / duplicate warm processes

```bash theme={null}
pmb daemon kill-all   # stop the daemon + kill registered PMB processes, clear registry
pmb setup             # re-wire cleanly
```

## Still stuck?

```bash theme={null}
pmb doctor --strict   # non-zero exit on real problems
```

Open an issue on [GitHub](https://github.com/oleksiijko/pmb) with the `doctor`
output.