Skip to main content

Find your problem fast

Run slowave doctor first

Most problems show up in these two commands.
doctor checks your setup, database and agent connections. status --services shows whether Slowave’s background services are running.

Connection problems

Your agent may not be connected, or it may still have an old session open.
  1. Run slowave doctor and look for your agent.
  2. Run slowave setup to reconnect.
  3. Restart your agent.
Memory also builds slowly. A brand-new install starts empty.
Setup skips agents it can’t detect.
  1. Open your agent once so it creates its settings folder.
  2. Run slowave setup --client <name>, for example claude-code.
Cursor and Claude Desktop also need a manual step. Setup prints it.
The dashboard runs in your terminal while it’s open.
  1. Run slowave dashboard and use the address it prints.
  2. If another copy is open, close it with Ctrl+C and try again.
  3. For a blank page, run slowave doctor.

Services and updates

The background services may be stopped.
  1. Run slowave start.
  2. If that fails, run slowave setup to register them again.
  3. Restart your agent.
Slowave can take up to two minutes to start after an update.
Old processes may still be running.
  1. Run slowave setup.
  2. Run slowave restart.
  3. Close and reopen your agents.
Your terminal can’t find the program.
  1. Run pipx ensurepath.
  2. Open a new terminal.
Don’t install a second copy to fix this.
Setup downloads a small search model (about 45 MB, from Hugging Face) the first time. After that it works offline. Keep an internet connection until setup finishes. If it stopped early, run slowave setup again to resume. Your memory text stays on your computer.

Problems on your system

Services run in your logged-in desktop session. Run slowave status --services, then slowave start. Logs are in the logs_dir folder that status --services prints.
Slowave uses your user’s systemd. Check it with systemctl --user status slowave-daemon.service. Don’t use sudo. In containers or WSL without systemd, run services by hand.
Slowave uses Task Scheduler tasks that start with Slowave. Open Task Scheduler and check their last result. Company policy can block task creation. If so, ask your admin.

Data problems

  1. Run slowave stop.
  2. Run slowave doctor.
  3. If the database is damaged, restore a backup.
Don’t delete database files by hand.
Run slowave backup and read the error. Check that you have free disk space.

Get help

Open an issue at github.com/slowave-ai/slowave/issues. Include:
  • The output of slowave doctor
  • Your operating system and agent
  • What you expected and what happened
Check the output for private paths or project names before you post it.
More answers are in the FAQ.