Repository navigation
lane: the WAF learned the DeepSeek Harness opener, so sanitize it too - #110
Merged
Merged
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.
The upstream's content gate learned DeepSeek Harness' fixed opener and refuses the request outright; the sanitize pass rewrites the known markers but not this one, so the retry is refused too and the client never gets a turn.
Measured against the live channel (same gateway, same model, only the system prompt differs):
You are an AI agent powered by DeepSeek Harness.You are a helpful assistant.DeepSeek HarnessYou are an AI agent powered by Foo.AI agent powered by DeepSeek Harnessyou are an ai agent powered by deepseek harness.So the gate matches the whole sentence, not a single word. This adds it to
wbFingerprintRewrites, rewriting it toYou are an AI agent— the sentence survives, the product name does not. The rewrite still only touches the copy sent upstream; the caller's own body is untouched (deep copy).Fixes #109