Warn on repeated tool batches before the doom loop trips - #909
Merged
TheGreatAxios merged 1 commit intoSep 11, 2026
Merged
Conversation
A model repeating an always-successful call saw only plain results until the guard killed the whole reactor, so the primary session wedged on the operator's next message. The second identical batch now gets a corrective note naming the repeated call, the tools on the wire, and the escape hatches; a tripped guard under doomLoopPolicy "fail-run" fails only the message run. manage_tasks answers repeat no-op updates distinctly.
TheGreatAxios
deleted the
cl-7681-doom-loop-guard-kills-the-run-with-no-warning-turn-identical
branch
September 11, 2026 06:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tool_searchmanage_tasksreturnsNo change: …when an update changes nothing, so repeat bookkeeping calls stop reading as fresh successdoom_loop; underdoomLoopPolicy: "fail-run"(primary session only) it fails the message run and returns the reactor to idle instead of wedging the session — workers keep the upstream shutdowndeps(doomLoopCorrectiveNote,doomLoopPolicy), ledgered invendor/intx-inference/PATCHES.mdVerification
bun run typecheck,bun run buildpass; vendored reactor suite green (178 tests), including new coverage for the warning turn and fail-runbun run test: 64 pre-existing environmental failures in git/GPG fixture tests (same on main under this sandbox); all touched areas passFixes https://linear.app/abklabs/issue/CL-7681/doom-loop-guard-kills-the-run-with-no-warning-turn-identical-no-op