Skip to content
dobbyBeta

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.

Terminal
dobby doctor
Output
✗ background jobs: not loaded: dashboard
fix: dobby jobs install

Every row is in Doctor checks.

Nothing is building

Terminal
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:

Terminal
dobby resume merges

If that is not it, look at the ticket. It may be waiting for you, or its review failed.

Terminal
dobby show 41

A ticket failed

Terminal
dobby show 41
dobby queue 41

The 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.

Terminal
npm i -g dobby-ai
dobby jobs install

A job exits with "node: not found"

You changed Node or moved Claude Code after installing the jobs.

Terminal
dobby jobs install

Jobs stop when you log out

Terminal
sudo loginctl enable-linger $USER
On 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

Terminal
dobby jobs status

If 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.

Terminal
dobby add skill