Restarting after an update keeps the model you picked instead of reverting to the default.
What's wrong with this entry?
When the CLI restarts itself, it now passes --model with the model you had selected, so an update relaunch or a renderer switch no longer drops you back to the default model.
- Appended next to the existing
--add-dir,--effortand--permission-modearguments. - Omitted when the selection is the default, when running a mantle deployment, or when it equals the configured fallback model.
- Applies to the auto-update relaunch ("Switching from … to latest") and to
/tuirenderer switching.
--model
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.238
Model and effort switch warning now checks whether the cache is actually warm
Both mention model