feat: add minimal scrub mode for prompt stability#5
Open
briankeefe wants to merge 1 commit into
Open
Conversation
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
MERIDIAN_OPENCODE_SCRUB_MODE=minimalfor users who need surgical fingerprint removal without rewriting prompt structure<env>/<omo-env>blocks and skip identity replacement in minimal modeWhy
Aggressive scrubbing is useful for avoiding Anthropic fingerprinting and Opus extra-usage gating, but it also changes prompt structure in ways that can destabilize some OpenCode execution flows. This adds an opt-in minimal mode so users can preserve execution-critical prompt structure while still removing the strongest third-party tells.
Validation
npm run buildMERIDIAN_OPENCODE_SCRUB_MODE=minimalrestored a previously failing OpenCode flow while keeping scrubbing enabled