For agents: an index of these docs is at /docs/llms.txt, and this page as markdown is at /docs/troubleshooting.md.
Fix common problems
What to do when nothing builds, pull requests never merge, a ticket fails, or the background jobs or dashboard do not run.
Start here. Each failed row prints its fix.
dobby doctor✗ background jobs: not loaded: dashboard fix: dobby jobs installEvery row is in Doctor checks.
Nothing is building
dobby status| First line says | Do |
|---|---|
Paused at 95% of your week (your cap), resumes ... |
Wait for the reset, or raise pacing.weekCap. |
Paused: 5-hour window at 60% (pace cap), resumes ... |
Wait until that time. |
Builders paused by owner since ... |
Run dobby resume. |
Plan usage unknown ... |
Check the Claude sign-in row in dobby doctor. |
Running |
Check that tickets are queued with dobby list. |
Pull requests never merge
A fresh install keeps merges paused:
dobby resume mergesIf that is not it, look at the ticket. It may be waiting for you, or its review failed.
dobby show 41A ticket failed
dobby show 41dobby queue 41The first command shows why it stopped. Fix the ticket text, then queue it again.
Jobs fail after npx dobby-ai init
The jobs need a copy that stays.
npm i -g dobby-aidobby jobs installA job exits with "node: not found"
You changed Node or moved Claude Code after installing the jobs.
dobby jobs installJobs stop when you log out
sudo loginctl enable-linger $USEROn a Mac you only use over SSH
Log in on the Mac's screen once, or turn on auto-login. Then run dobby jobs install.
The dashboard does not load
dobby jobs statusIf dashboard is not loaded, run dobby jobs install.
Ask Claude to help
Copy Dobby's setup skill into your own Claude Code, then ask Claude about the problem.
dobby add skill