The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found several related PRs addressing similar issues. Here are the most relevant ones:

Directly Related (mentioned in the PR description):

1. PR fix: preserve thinking block signatures and fix compaction headroom asymmetry #14393 - fix: preserve thinking block signatures and fix compaction headroom asymmetry #14393

   • "fix: preserve thinking block signatures and fix compaction headroom asymmetry"
   • Addresses cause 1 by removing the differentModel guard entirely. The current PR takes a narrower approach (reasoning only) and also covers causes 2 and 3.

2. PR fix(provider): skip empty-text filtering for assistant messages in normalizeMessages (#16748) #16750 - fix(provider): skip empty-text filtering for assistant messages in normalizeMessages (#16748) #16750

   • "fix(provider): skip empty-text filtering for assistant messages in normalizeMessages (normalizeMessages() removes empty text parts between reasoning blocks, invalidating Anthropic thinking block signatures #16748)"
   • Related to cause 3 (empty reasoning parts filtering)

Related to thinking block and reasoning content filtering:

3. PR fix(opencode): filter empty text content blocks for all providers #17742 - fix(opencode): filter empty text content blocks for all providers #17742

   • "fix(opencode): filter empty text content blocks for all providers"
   • Addresses similar empty content filtering issues

4. PR fix(provider): drop empty content messages after interleaved reasoning filter #17712 - fix(provider): drop empty content messages after interleaved reasoning filter #17712

   • "fix(provider): drop empty content messages after interleaved reasoning filter"
   • Related to empty reasoning parts handling

5. PR fix(provider): preserve assistant message content when reasoning blocks present #21370 - fix(provider): preserve assistant message content when reasoning blocks present #21370

   • "fix(provider): preserve assistant message content when reasoning blocks present"
   • Directly relevant to preserving reasoning block integrity

6. PR fix: strip reasoning parts when switching to non-interleaved models #11572 - fix: strip reasoning parts when switching to non-interleaved models #11572

   • "fix: strip reasoning parts when switching to non-interleaved models"
   • Related to model switching and reasoning content

The PR's description already acknowledges the relationship with #14393 and #12131, indicating these are complementary approaches to the same underlying issue.

Thanks for updating your PR! It now meets our contributing guidelines. 👍

CI note

The e2e (windows) failure is unrelated to this change — it's a runner infrastructure issue (ECONNRESET / timeouts). The same failure appears on recently merged PRs (#21827, #21803, #21796) as well.

All code-related checks pass:

• ✅ unit (linux)
• ✅ unit (windows)
• ✅ e2e (linux)
• ✅ typecheck
• ✅ nix-eval

Happy to rebase or address any feedback if needed!

Rebased on latest dev and updated the PR:

• Removed the trimEnd() fix — already landed in tweak: rm processor .trim calls #21958
• Replaced the old normalizeMessages patch (which just preserved signed empty reasoning) with a more robust approach: empty text in signed reasoning messages is now replaced with "..." instead of removed. This keeps the array shape intact through the AI SDK's downstream filter and the API's non-empty text requirement.
• Two commits, each reviewable independently.

1. Model routing drops reasoning metadata (message-v2.ts)

The first one shows up when the current model doesn't match the model stored on the message, which can happen pretty easily with plugin-based routing. In that case, toModelMessages drops providerMetadata for every part, including reasoning parts. For Anthropic, that's where the thinking signature lives, so once that metadata is gone the next request is already broken.

The fix here is just to keep metadata on reasoning parts even when the model changes. Text and tool parts still keep the existing behavior. I was comfortable narrowing it that way because the metadata is already provider-scoped (anthropic: { signature }).

No you can't do this because a lot of models use anthropic messages api, for example minimax, if I started a session w/ minimax and then used anthropic models it would error, if this is due to "plugin based routing" I think ur plugin is bugged or we arent providing correct hooks for u

You're right — I went back and checked my sessions and differentModel was never actually true (same model throughout). This was a code-reading finding I didn't validate against real data. Dropping that commit and keeping just the empty text replacement fix.

Closing — the same issue was resolved upstream via #21370 (space substitution at message-v2.ts layer). Thanks for the review!