v2.0.0next

Troubleshooting

Where to look when a work item stopped, the server will not start, or a doctor row fails.

Find the message you are looking at in the first column, then follow its link.

Find your problem

What you seeGo to
A work item under Needs you, with a reason such as task failed in node ..., could not start ..., budget cap reached or stuck: ...Why did my item stop?
A sandbox, Kit, workspace-member or nested-repository reason, such as a process in the sandbox was killed by its memory limit or the Kit ... cannot be usedSandbox and Kit stops
no setup_command declared for ... on a first work itemno setup_command declared
no user.name configured in ...no user.name configured
... nothing registers it for Claude Code: ...nothing registers it for Claude Code
could not start ... with declares neither test_scopes nor test_command in repos.yamldeclares neither test_scopes nor test_command
task failed in node ..., and the log shows an authentication or login errorQuestions, failed tasks and logins
A work item that waits on CI or a review and nothing movesWaiting on CI or a review
kraft: command not foundkraft: command not found
kraft: refusing to start, or a port that is already in useKraft won't start: port already in use
A webhook or proxy gets 403 unexpected HostA webhook or proxy gets 403 "unexpected Host"
A kraft admin doctor row that prints FAIL or warnDoctor failures
A page that is not where you left it, or a theme that looks different, after an upgrade from 1.4Where the pages moved
A question about forges, harnesses, cost, platforms, specs, Kraft Lite or the permission gateFAQ
None of these matchesGetting help

In this section

Copyright © 2026