{"version":"2.1.283","anchor":"client-data-can-now-switch-model-capabilities-off-as-well-as","canonical_anchor":"client-data-can-now-switch-model-capabilities-off-as-well-as","heading":"Model features that are on by default can now be switched off remotely","tier":"internal","area":"Configuration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/client-data-can-now-switch-model-capabilities-off-as-well-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Model features that are on by default can now be switched off remotely\n\nClient data can now turn off a model feature that is on by default, where before it could only turn features on\n\n**Unclear.** Where the client data comes from is not settled.\n\n**What**\n\nClaude Code decides which features each model supports. A set of client data can adjust those decisions. Before, it could only turn a feature on. Now, when a feature is on by default for a model, client data that sets it to `false` turns it off, and Claude Code logs that this happened.\n\nAn explicit off setting from the earlier lookup no longer cuts the check short. Any value that has been set is used as it is.\n\n**Why**\n\nFeatures that affect what Claude is told, such as `turn_updates` or `thinking_display_updates`, can now be switched off from outside the app, not just switched on.\n\n- Area: Configuration\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}