Skip to main content
Start here - it diagnoses the install and runtime state:
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:
pmb warmup
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. Run one on another port, e.g. pmb dashboard --port 18888.

Stray / duplicate warm processes

pmb daemon kill-all   # stop the daemon + kill registered PMB processes, clear registry
pmb setup             # re-wire cleanly

Still stuck?

pmb doctor --strict   # non-zero exit on real problems
Open an issue on GitHub with the doctor output.