Kilo Code retry loop: reject repeats and check the diff

When Kilo Code repeats the same failed action, do not approve another identical write. Require approval for repeated failures, reject the repeated operation with feedback, and inspect the current diff before trying a smaller task. The reported retry loop has no verified universal fix; the controls below limit further actions while the cause is investigated.

Updated and sources checked: October 9, 2026.

Recognize the reported loop

A user report opened August 2, 2026 describes repeated reasoning and tool actions, including apply_diff, search_files and execute_command, on Kilo 7.4.17 with kilo-auto/balanced. The reporter used macOS and Nobara Linux, with Context7 and Puppeteer MCP tools involved. See Kilo retry-loop report 12772.

Manually stopping and continuing helped inconsistently in that report. Changing the model was also reported to help, but this is not an official fix or evidence that another model cannot loop. The report does not establish the cause or the frequency across Kilo users.

Require approval and reject the repeated action

Open Settings > Auto Approve. The doom_loop permission controls continuation after repeated failures; Ask pauses for approval, while Deny blocks the permission. For a controlled retry, choose Ask for doom_loop, edit and bash, so repeated failures, file edits and shell commands require a decision. See Kilo auto-approving actions guide.

At a permission prompt, choose Deny to expose the feedback field, describe what must change, then choose Reject to block that invocation and send the feedback. Enter posts the rejection; Shift+Enter adds a line. Turn off the highlighted shield button if runtime auto-approve is approving prompts automatically.

Project rules in .kilo/kilo.jsonc or .kilo/kilo.json are cached when the workspace loads. After editing those files, reload the VS Code window or start a fresh CLI session. Changing a rule in a running project does not guarantee the next prompt uses it.

Preserve the transcript and narrow the next request

Run /export in chat, or use History > Export session transcript for a local session, to save its complete history as Markdown. Inspect the export for secrets before sharing it. Reference the relevant file with @filename; @terminal includes the active VS Code terminal output in the sidebar. See Kilo chat interface guide.

Kilo recommends one focused task at a time and specific file context. Before that retry, preserve the changed files and compare the local diff. State the failed action, its actual output and one acceptance check. This comparison is diagnostic advice, not a documented repair for issue 12772.

/export

Change the model only as a controlled comparison

Use the model selector in the chat prompt area, or /models, to select the main model for the current session. Settings > Models also holds per-agent and global defaults. A manual selection takes precedence within that session and agent. See Kilo model selection guide.

Keep the task and file context unchanged when comparing models. Record the selected model, Kilo version, operating system and repeated tool output. A different result narrows the investigation; it does not prove the original model was the sole cause.

/models

How ShardStitch helps

ShardStitch can carry changed files, failed attempts and the next check into a fresh Kilo session or a supported handoff target. It cannot reject Kilo actions, stop a running loop or repair the extension. ShardStitch pricing.