{"version":"2.1.175","anchor":"safer-model-change-handling-in-sdk-remote-sessions","canonical_anchor":"safer-model-change-handling-in-sdk-remote-sessions","heading":"Safer Model Change Handling in SDK\/Remote Sessions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.175\/e\/safer-model-change-handling-in-sdk-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.175","markdown":"### Safer Model Change Handling in SDK\/Remote Sessions\n\nThe `set_model` and session-initialization code paths now verify model names against the allowlist before applying them. If a model is not allowed, the change is rejected and the user sees an actionable warning message instead of the session silently using an unexpected model.\n\n**Evidence**\n\nUpdated `onSetModel` handler (search for `\"model-restricted-bridge-\"`)"}