Lower default --clone-threshold from 0.8 to 0.6#4
Merged
Conversation
Live A/B/C runs against the demo Clone token show predictor confidence sitting in the 0.72-0.80 band on real iteration context. With the 0.8 default, well-grounded predictions (PATCH/DELETE coverage after green tests, supertest follow-ups) were escalating to humans roughly 3 out of 5 times. Dropping the default to 0.6 lets the loop carry those predictions through while still gating against the truly low- confidence ones (~0.45 single-candidate replies, ~0.5 when the model explicitly flags lack of signal). Updated everywhere: setup-clone-loop default, stop-hook + ask-user- question-hook in-process fallbacks, manual e2e scripts, all test fixtures, README, and commands/help.md examples. Users who want stricter gating can still pass --clone-threshold 0.8. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Why
Live A/B/C runs against the demo token (5x per variant, identical scenario) show predictor confidence sitting in the 0.72–0.80 band on real iteration context. With the 0.8 default, well-grounded predictions (PATCH/DELETE coverage after green tests, supertest follow-ups) were escalating to humans roughly 3 out of 5 times.
Dropping to 0.6 lets those predictions carry through while still gating against the truly low-confidence ones (~0.45 single-candidate replies, ~0.5 when the model explicitly flags "no profile data").
What changed
Users who want stricter gating can still pass `--clone-threshold 0.8`.
Test plan
🤖 Generated with Claude Code