Repository navigation
Ask the model again when its reply holds its own markup, then remove it - #67
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <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
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 owner saw gpt-oss-120b write its own control tokens (
<|start|>,<|call|>and others) as the text of a reply, three times on "Draft the first section.": a search after a save, its reasoning and made-up searches, and a search in an answer's first call, so nothing ran or saved.retryingModelMarkupinsrc/server/ai/cloudflare.tssends the same request once more when a reply's text holds one of those tokens, at most once per model call. The reply carries both calls' tokens.This changes the transport, so it's one to note before the next measurement: the removed text no longer comes back with later messages, and a retried call sends a second HTTP request. The prompt, tools and generation settings are unchanged. No cause is isolated, and whether the retry usually works is unmeasured.
Checks:
npm run verifypassed locally (636 unit tests), with all three replies replayed intests/unit/cloudflare.test.ts. Not yet seen on the real model.