You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
EffortArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
Unclear It is not clear whether effort is now set for ultracode somewhere else.
What
A program controlling Claude Code can turn on ultracode through apply_flag_settings. When ultracode cannot be used, the error used to list three possible reasons together. It now gives the actual one:
the named model does not support it
dynamic workflows are off
Turning ultracode on explicitly now only sets it. It no longer also switches the session's effort level to extra-high (xhigh).
Why
The error now says which problem to fix. A host that turns on ultracode should not expect the effort level to change as a side effect.
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.
Confirmed sinceAnthropic's documentation has since written up apply_flag_settings, on Hooks reference.* A `set_model` request, or a model change in an `apply_flag_settings` request, from an [Agent SDK](https://code.claude.com/docs/en/agent-sdk/typescript.md#query-object) host or [Remote Control](https://code.claude.com/docs/en/remote-contr…hookssee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether effort is now set for ultracode somewhere else.
Anthropic's documentation agreesAnthropic's documentation has since written up apply_flag_settings, on Hooks reference.