Repository navigation
feat(threads): model change marker shows effort, fast mode and other parameters - #294
Merged
Merged
Conversation
Changing effort, fast mode, context window or any other model option left no marker in the transcript, unlike a model switch. The model change marker now records option-only changes too and renders them as "Model settings changed" with each option's old and new value, on web, mobile and in MCP thread reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Option-only changes no longer get their own "Model settings changed" divider. Every change is a "Model changed" divider whose two sides name the model and its parameters, labelled as the composer's traits picker labels them (e.g. "Claude Opus 5.5 High → Claude Opus 5.5 Max Fast"). The traits label builder moves to @t3tools/shared/model so mobile renders the same text. 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.
Switching models in a thread leaves a "Model changed" divider, but changing a parameter of the same model (effort, fast mode, context window, thinking, OpenCode agent/variant, and so on) left nothing in the transcript, and the divider never said which parameters either side ran with.
How
model_changeturn item is now recorded when the model or any of its options change, and it always renders as Model changed. Each side names the model and its parameters, labelled exactly as the composer's traits picker labels them, e.g.Claude Opus 5.5 High → Claude Opus 5.5 Max Fast, orClaude Opus 5.5 High → Claude Sonnet 5.5 Highfor a model switch.ultrathinkresolve to the default they dispatch as, and stale options the model doesn't offer are ignored. The orchestrator stays pure, so it compares raw values; if that records something the client can't resolve to a real difference, the row renders nothing.from/toModelSelection. The steer-restart path already compared full selections.buildTraitsTriggerDisplaymoved unchanged from the webTraitsPickerto@t3tools/shared/modelso mobile'sThreadModelChangeRowrenders the same text. Mobile's activity preview/inspector and the MCP thread text describe both selections with their options.docs/fork-differences.md.Screenshots
Same thread on Claude Opus 5.5 at High effort, composer changed before sending.
Verification
vp test runformodelChangeMarker.test.ts(option-only change recorded; explicit default and ultrathink produce no pending divider; composer-style labels) andTraitsPicker.test.ts, plus server orchestration/MCP suites, mobilethreadActivity*and websession-logictests.tsc-rs --noEmitpasses for shared, server and mobile. Web's only error is pre-existing, interminal/ghostty/surface.test.ts.🤖 Generated with Claude Code