[DOCS] `claude agents --effort ultracode` behavior for dispatched sessions is undocumented

Open 💬 0 comments Opened Jul 15, 2026 by coygeek

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/agent-view

Section/Topic

The Permission mode, model, and effort section, especially the claude agents dispatch-default flags and the meaning of --effort ultracode. The corresponding --effort flag and claude agents command entries in the CLI reference should also be aligned.

Current Documentation

The agent view page currently says:

To set defaults for every session you dispatch from agent view, pass any of --permission-mode, --model, --effort, or --agent when opening it: ``bash claude agents --permission-mode plan --model opus --effort high ``

The CLI reference similarly says that claude agents accepts --effort to set defaults for dispatched sessions. However, its --effort entry describes ultracode only as a value that starts the current session at xhigh effort with Ultracode enabled.

What's Wrong or Missing?

Claude Code v2.1.210 fixed claude agents --effort ultracode not reaching sessions dispatched from agent view; the value was silently dropped. The current documentation does not explain that ultracode is a valid agent-view dispatch default or that it applies to sessions launched after opening agent view.

This leaves an important ambiguity in the dispatch contract: a reader can see that --effort configures dispatched sessions and that ultracode is valid for the top-level CLI, but cannot determine whether claude agents --effort ultracode enables Ultracode (including automatic workflow orchestration) in each dispatched session. The omission is especially significant because the flag previously appeared to succeed while silently producing sessions without the requested setting.

Suggested Improvement

Update the agent view and CLI reference documentation to explicitly describe the ultracode dispatch behavior. Include an example such as:

claude agents --effort ultracode

State that, in Claude Code v2.1.210 and later, this sets the default for sessions subsequently dispatched from that agent view: each dispatched session starts with xhigh reasoning effort and Ultracode's dynamic-workflow orchestration enabled, subject to the model and workflow availability rules. Clarify how the setting appears in the agent-view footer and how to return to the normal effort default.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 474-504 | Effort behavior and claude agents dispatch-default flags |
| https://code.claude.com/docs/en/cli-reference | 28, 80 | claude agents command and --effort flag reference |
| https://code.claude.com/docs/en/model-config | 445-470 | Definition of Ultracode as xhigh plus dynamic-workflow orchestration |

Total scope: 3 pages affected

The behavior change is documented in Claude Code v2.1.210. The existing agent-view text documents ordinary effort defaults and settings-derived effort persistence, but not the special ultracode value or its propagation to dispatched sessions.

View original on GitHub ↗