Skip to content

Recognize the server-fallback boundary marker by its signature alone - #678

Merged
ualtinok merged 2 commits into
mainfrom
fix/fallback-boundary-signature
Nov 9, 2026
Merged

ualtinok merged 2 commits into
mainfrom
fix/fallback-boundary-signature

Conversation

@antauth-alfonso

@antauth-alfonso antauth-alfonso Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Recognize the server-fallback boundary marker by its signature alone. Worker delivery rebased onto main; see the commit messages.


Summary by cubic

Recognizes server-fallback boundary markers by their signature, even when a context manager clears their thinking text. This restores valid fallback boundaries on replay instead of sending invalid thinking blocks to Anthropic.

  • Removes the internal marker when fallback is disabled or when requests are routed through an API key.
  • Adds regression coverage for cleared and original marker text.

Written for commit 74745ac. Summary will update on new commits.

View guided diff Turn on auto-fix

Restore or drop stored boundary markers regardless of reasoning text cleared by a context manager. Preserve signature decoding, validity checks and fallback policy behavior. Extend existing OC1/OC2 replay coverage to cleared text while retaining the original marker-text cases, and add enabled/disabled regression checks.
@ualtinok
ualtinok merged commit 74745ac into main Nov 9, 2026
16 checks passed
@ualtinok
ualtinok deleted the fix/fallback-boundary-signature branch November 9, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant