Skip to main content
Start here - it diagnoses the install and runtime state:

First recall is slow

The first recall after a fresh boot loads the embedding model (~1-2s, the model is ~450MB). Warm it once:
The daemon also prewarms in the background on boot. Subsequent recalls are ~35ms warm.

Recall returns nothing

Intents/extraction are warm-only. pmb daemon status; start it with pmb daemon start (or pmb setup, which pins it warm).
pmb stats to check counts. A young workspace is genuinely empty - index a project (pmb index project .) or capture a few notes.
Auto-recall stays quiet on trivial messages by design. Use pmb recall "…" directly from the terminal to bypass the gate.

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:
Use an explicit port when you want a fixed address:

Stray / duplicate warm processes

Still stuck?

Open an issue on GitHub with the doctor output.