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
My agent doesn't remember anything
My agent doesn't remember anything
Your agent may not be connected, or it may still have an old session open.
- Run
slowave doctorand look for your agent. - Run
slowave setupto reconnect. - Restart your agent.
Setup didn't find my agent
Setup didn't find my agent
Setup skips agents it can’t detect.
- Open your agent once so it creates its settings folder.
- Run
slowave setup --client <name>, for exampleclaude-code.
The dashboard won't open
The dashboard won't open
The dashboard runs in your terminal while it’s open.
- Run
slowave dashboardand use the address it prints. - If another copy is open, close it with Ctrl+C and try again.
- For a blank page, run
slowave doctor.
Services and updates
Slowave stopped after a restart or update
Slowave stopped after a restart or update
The background services may be stopped.
- Run
slowave start. - If that fails, run
slowave setupto register them again. - Restart your agent.
I still see the old version after upgrading
I still see the old version after upgrading
Old processes may still be running.
- Run
slowave setup. - Run
slowave restart. - Close and reopen your agents.
slowave: command not found
slowave: command not found
Your terminal can’t find the program.
- Run
pipx ensurepath. - Open a new terminal.
It's slow on first use
It's slow on first use
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
macOS
macOS
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.Linux
Linux
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.Windows
Windows
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
Database is locked, or something looks corrupted
Database is locked, or something looks corrupted
- Run
slowave stop. - Run
slowave doctor. - If the database is damaged, restore a backup.
A daily backup fails
A daily backup fails
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

