{"version":"2.1.284","anchor":"ultracode-unavailability-error-is-more-specific","canonical_anchor":"ultracode-unavailability-error-is-more-specific","heading":"Clearer error when ultracode can't be turned on, and it no longer forces top effort","tier":"notice","area":"Effort","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/ultracode-unavailability-error-is-more-specific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Clearer error when ultracode can't be turned on, and it no longer forces top effort\n\nWhen ultracode is unavailable, the error now names one reason, and turning it on no longer forces extra-high effort\n\n**Unclear.** It is not clear whether effort is now set for ultracode somewhere else.\n\n**What**\n\nA 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:\n\n- the named model does not support it\n\n- dynamic workflows are off\n\nTurning ultracode on explicitly now only sets it. It no longer also switches the session's effort level to extra-high (`xhigh`).\n\n**Why**\n\nThe 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.\n\n- Area: Effort\n- Names: `apply_flag_settings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}