Troubleshooting
Symptoms, likely causes, and the command that settles each one.
Start with rose doctor. It reports backends, store, hook wiring,
and whether the rose command is on your PATH.
| Symptom | Likely cause | Check / fix |
|---|---|---|
rose: command not found |
The CLI is not on PATH. Hooks are unaffected — they invoke the package by absolute path, so ROSE is still running. | rose install links it; or symlink bin/rose into
~/.local/bin yourself |
| Nothing is ever recalled | An empty store, or every match is already fresh in your context | rose tree for what exists; rose recall --prompt "…"
for what a given prompt would pull |
| Nothing is ever learned | No backend, no substantial turns, or the reflection backoff has grown | rose status — look at nudges and the miss rate;
rose events --kind nudge for when one last fired |
| Hooks never fire | Installed at project scope into a repo you do not work in — including ROSE's own clone | rose doctor shows where they are wired;
rose install --scope user fixes it |
| The wrong lessons keep appearing | Recall over-serving, the weakest part of the system today | rose trace --prompt "…" shows the model's verdict and reason
for every candidate |
| A lesson is wrong or out of date | It was captured from a situation that has since changed | rose conflicts, then
rose resolve <id> --drop |
| A bug in ROSE itself | — | rose report --about "…" writes a redacted report and prints
the gh command to file it. It sends nothing. |