{"version":"2.1.265","anchor":"model-default-save-now-confirms-the-write-and-reports-failu","canonical_anchor":"model-default-save-now-confirms-the-write-and-reports-failu","heading":"\/model default-save now waits for and confirms the write","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/model-default-save-now-confirms-the-write-and-reports-failu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### \/model default-save now waits for and confirms the write\n\nSaving a model as your default via \/model now waits for the settings write to finish and reports if it failed or couldn't be confirmed\n\n**What**\n\nSwitching models and saving the choice as your default (via the model picker or `\/model ... default`) now waits for the settings write to actually complete, with a timeout, instead of assuming it succeeded right away. The confirmation message now reflects one of three real outcomes:\n\n- `saved` - the write completed and is confirmed.\n\n- `unconfirmed` - the write couldn't be confirmed within the timeout because `settings.json` was still being written.\n\n- `failed` - the write failed, with the underlying error shown.\n\n**Why**\n\nPreviously the UI could report a model as \"saved as your default\" before the write to disk was verified. Now the message only claims success once the save is actually confirmed, and tells you when it failed or is still in progress instead of silently assuming it worked.\n\n- Area: Models\n- Names: `\/model`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}