Worktree and git stops
The first column is the text the board and kraft view show ID print. ... stands for text that varies. Kraft stops here instead of forcing git, so nothing is undone. In the worktree, run cd "$(kraft repo path ID)" first.
Find your reason
| The reason says | What happened | Fix |
|---|---|---|
the conflict in node <node> cannot be resolved ... | Rebasing onto the base branch hit a conflict nobody resolved. | Resolve it in the worktree, commit, then run kraft item retry ID. |
<task> [forge] hit a rebase conflict in node <node>: rebase onto <base> failed: ... | Kraft's own rebase, while it waited on CI or merged, hit a conflict in a fix-loop node with no on_conflict. The worktree is left clean. An escalation agent tries first when auto-escalation is on. | In the worktree, rebase onto the base branch, resolve the conflict and commit, then run kraft item retry ID. Added in 2.6 |
task failed in node <node>: <task> [forge] — rebase onto <base> failed: ... | The same conflict in a node with no fix loop. It stops as a failed task, not a conflict, and git's line is in the reason. An escalation agent tries first when auto-escalation is on. | In the worktree, rebase onto the base branch, resolve the conflict and commit, then run kraft item retry ID. Added in 2.6 |
untracked <paths> would be overwritten by the base branch; move or delete it, then retry, or git would not start the rebase onto the base branch ... | Kraft went to rebase the item onto its base branch, and git refused to start, so nothing was rebased. | Move, delete or commit the files git names, then run kraft item retry ID. See Git wouldn't start the rebase. |
<worktree> has a <name> in progress: inspect it, then delete ... | The worktree holds a rebase, merge, cherry-pick, revert, bisect or autostash, so Kraft wouldn't rebase or commit over it. | Look at the file the reason names before deleting it. See A git operation is in progress. |
<worktree> is not on <branch>; check it out by hand, then retry | The worktree's HEAD names another branch, so Kraft wouldn't commit, rebase or push from it. | Check that nothing of yours is on the named branch, run git checkout <branch>, then kraft item retry ID. |
origin/<branch> is at <sha>, which Kraft did not push and this worktree does not have ... | Someone pushed commits to the item's merge request branch, and Kraft's push would have overwritten them. Kraft's own earlier pushes no longer stop it here, even one it stopped before recording. | Run git pull --rebase origin <branch> to bring them in, then kraft item retry ID. |
the branch adds Git LFS files and this machine has no git-lfs ... Added in 2.5 | The item's new commits hold Git LFS pointers, and Kraft uploads their objects itself before it pushes, with git-lfs. Nothing was pushed. | Install git-lfs on the machine Kraft runs on, then run kraft item retry ID. |
origin no longer has <branch>, which Kraft pushed ... | The item's branch was deleted from origin, usually with its merge request merged or closed, and Kraft won't recreate it. | To publish the work anyway, run the two git update-ref -d commands the reason names in the item's worktree, then kraft item retry ID. Otherwise run kraft item abandon ID --reason "..." --yes. |
A reason that names <checkout>, your own checkout, for an item that runs in place Added in 2.1 | Kraft wouldn't force your checkout, or a task left it in a state Kraft won't repair. The stop kind is checkout. | Read the reason, fix what it names, then run kraft item retry ID. Clear a checkout stop lists every reason. |
Git wouldn't start the rebase
Nothing was rebased. Most often the base now tracks a file the worktree has untracked, such as a note or a script the agent never committed, and git won't overwrite it.
- Run
cd "$(kraft repo path ID)". - Look at the files git names, then move, delete or commit them.
- Run
kraft item retry ID.
A uv.lock the setup command wrote and nobody changed isn't one of these: Kraft sets it aside for the rebase. One that an older release recorded without a digest is kept in place, in case the agent edited it: see Coming from 1.4.
A git operation is in progress
The worktree holds a rebase, merge, cherry-pick, revert, bisect or autostash. A sandboxed worker can plant one to move one of your branches. A rebase of Kraft's own that was cut short (a server killed mid-rebase, or an abort that couldn't run) leaves one too.
- Look at the named file first. If you didn't leave it there yourself, delete it as the reason says.
- If deleting it leaves
HEADdetached, check the item's branch out again withgit checkout -f <branch>, as the reason names it. The branch still has the item's commits. - Run
kraft item retry ID.
Never run git rebase --abort, git merge --abort or --continue on it: that is what moves the branch.
Forge stops
Fix a work item that stopped because the forge refused its credentials, rate-limited it, couldn't be reached, or no longer matches the account the item first used.
Sandbox and Kit stops
Find the reason a sandboxed work item stopped, whether a sandbox with no network policy, the sandbox's memory limit, a Kit Kraft won't run, a workspace member Kraft can't check out, or a nested git repository Kraft didn't create, and the fix for each.