Saving 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
What
Switching 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:
saved- the write completed and is confirmed.unconfirmed- the write couldn't be confirmed within the timeout becausesettings.jsonwas still being written.failed- the write failed, with the underlying error shown.
Why
Previously 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Cap the [effort level](/docs/en/model-config#adjust-effort-level) a session can use, leaving lower levels available. Any higher level runs at the cap instead, including one from `/effort`, the `/model` picker, `--effort`, [`CLAUDE_CODE_EFF…settings-reference see the edit
`effortLevel` accepts an [effort level](/docs/en/model-config#adjust-effort-level) name. It also accepts `"ultracode"`, which requests `xhigh` effort with [ultracode](/docs/en/workflows#let-claude-decide-with-ultracode) on. `applyFlagSetti…agent-sdk/typescript see the edit
A small documentation edit on Agent SDK reference - TypeScript touched a line naming /model after this was published.
Fixed /model opusplan[1m] being rejected with "Model not found"