release v0.1.46 - #192
Closed
ranxianglei wants to merge 2 commits into
Closed
Conversation
Session 01a02542 re-issued a byte-identical no-op compress 3,849 times (5h13m): the kernel hides failed compress calls from the sent view, so at cap the visible context stops changing and a deterministic model can never observe its failure. Two defenses: - Tool-side circuit breaker: once the turn burned MAX_COMPRESS_ATTEMPTS failed/no-op attempts, re-submitting an exact already-failed range set is refused without executing anything (no stateFor/processTurn/save). - Post-cap STOP message: while the newest outcome is a failure, every context fire re-injects a count-bearing stop instruction — visible in headless mode and varying per new failure, so the sent view never sits at a fixed point. Failed outcomes now carry their call's parsed ranges (from the assistant toolCall block) to key the breaker.
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.
Changes since v0.1.44
KEEP_LAST_ORPHANED0 → 2 — the newest two orphaned compress call+result pairs stay visible in the sent view. This removes the fixed-point precondition behind issue fix: modelContextLimit 反映模型真实上下文窗口，移除 150K 硬上限 #9's infinite no-op compress loop: failures are observable again and each new failure changes the view.vand CI's check missed it — fix(ci): tolerate missing 'v' in release branch name, warn on near-miss #189 fixes that). Skipping to 0.1.46 for a clean monotonic bump; merge fix(ci): tolerate missing 'v' in release branch name, warn on near-miss #189 before this so publishes work.Preflight (against the real 0.0.32 from npm)
npm install(lockfile refreshed — acp-kernel pinned 0.0.32)npm run typechecknpm run buildMerge order: #189 → this. acp-kernel 0.0.32 is already live on npm.