{"version":"2.1.280","anchor":"selected-model-can-now-be-synced-to-the-organizations-serve","canonical_anchor":"selected-model-can-now-be-synced-to-the-organizations-serve","heading":"Selected model can now be synced as the organization's server-side default","tier":"use","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/selected-model-can-now-be-synced-to-the-organizations-serve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Selected model can now be synced as the organization's server-side default\n\nYou can now push your selected model to become your organization's server-side default model\n\n**Unclear.** The finding does not say who can trigger this sync (e.g. only admins) or when exactly it fires relative to changing your model.\n\n**What**\n\n- A new code path sends a request to the server (`PATCH \/api\/organizations\/:orgUUID\/model_selector_state\/${scope}`) to save your currently selected model as your organization's remote default.\n\n- This only happens when the scope is `primary`, is `served`, and has an account scope, and it's skipped for `opusplan`\/`opusplan[1m]` since those selections aren't representable as a server-side default.\n\n- A new telemetry outcome value, `model_default_server_sync`, was added alongside existing model-related outcomes like `model_catalog_primary` and `model_env_default` to record when this happens.\n\n**Why**\n\nThis lets a model choice made in Claude Code propagate to the organization's server-side default, so the selection can be reflected elsewhere without having to reconfigure it separately.\n\n- Area: Models\n- Names: `\/model`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}