Troubleshooting

Run e11 doctor first. Fix the named row, repeat the check, then return to your task.

The checkout does not converge

Read each refused row from e11 init. Confirm Node.js 24.15.0 or later, package access, and the Toolkit pin. Preserve exact managed ignore blocks. Add real acceptance commands to profiles.toml if init reports an empty profile.

node --version
e11 --version
e11 init
e11 doctor

A run does not plan

Check the selected initiative and committed source. Fix the paths or acceptance criteria named by the refusal.

e11 initiative show
git status --short
e11 run story <id> --plan-only

A run pauses or an attempt fails

e11 runs status <run>
e11 runs report <run>

Open the run page for worker output and gate evidence. Raise the ceiling for a cost pause. Correct the underlying failure before e11 runs retry <run> --work-item <id>. Read the refusal guide for the next step.

Landing refuses

Check out the target branch named by the refusal. Commit or set aside overlapping uncommitted files. If histories diverged, merge the run branch yourself and record the landing without --merge.

git status --short
e11 runs status <run>

The dashboard shows no work

e11 project list
e11 runs list
e11 dashboard --port 4711 --no-open

Confirm you opened the correct checkout. Add the checkout with e11 project add <path> before using --all-projects. Open the URL from the serving terminal. Check the connection badge and terminal when live updates stop.

An editor skill is missing

e11 init --ide claude-code,codex,opencode
e11 doctor

Reopen the editor’s skill list after init. Put custom changes in TOML overrides so a refresh preserves your settings.

Error codes lists stable refusal codes. Upgrading covers older checkouts.