{"version":"2.1.284","anchor":"effort-migration-no-longer-special-cases-ultracode","canonical_anchor":"effort-migration-no-longer-special-cases-ultracode","heading":"Switching models with \/model no longer treats ultracode effort levels specially","tier":"notice","area":"Effort","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/effort-migration-no-longer-special-cases-ultracode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Switching models with \/model no longer treats ultracode effort levels specially\n\nOn `\/model` switches, the effort level is now applied directly, including levels that came from ultracode, and ultracode state is no longer set\n\n**Unclear.** The overall effect a user will notice is not known.\n\n**What**\n\nEffort is how hard Claude reasons before answering. When you switch model with `\/model`, Claude Code now applies the effort level directly. Before, it skipped effort levels that had come from ultracode and recorded an ultracode setting in its state. Both of those special cases are gone, and the one-off step that moves users onto new effort defaults no longer considers ultracode either.\n\n**Why**\n\nChanging model may now change your effort level or ultracode state differently from before.\n\n- Area: Effort\n- Names: `\/model`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}