[DOCS] [Agent view] Dispatch composer in `claude agents` is documented only for the unavailable-slash-command hint; v2.1.203 fix to preserve the typed message is not described

Open 💬 0 comments Opened Jul 7, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

The "From agent view" subsection of the "Dispatch new agents" section in agent-view.md, specifically the bullet list and the paragraph that immediately follows the table and lists which slash commands run in agent view itself versus being dispatched to a new session. The "Version history" table at the bottom of the same page also needs a row entry for v2.1.203.

Current Documentation

From agent-view.md (lines 264-283):

Prefix or mention parts of the prompt to control how the session starts: | Input | Effect | | :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------- | | <agent-name> <prompt> | If the first word matches a custom subagent name, that subagent runs as the session's main agent with the configuration from its frontmatter | | @<agent-name> | Mention a custom subagent anywhere in the prompt to run it as the main agent | | @<repo> | Mention a repository to run the session there. See [Dispatch to a specific directory](#dispatch-to-a-specific-directory) for which repositories are listed | | /<command> | Suggest skills and commands to dispatch as the prompt | | ! <command> | Run a shell command as a background job instead of starting a Claude session. The job appears as a row you can attach to, watch, and detach from | | #<number> or a pull request URL | If a session is already working on that PR, select it instead of dispatching | | Shift+Enter | Dispatch and immediately attach to the new session | A small set of commands run in agent view itself instead of dispatching: /exit and /quit close agent view /logout signs you out /model sets the [dispatch model](#set-the-model) {/ min-version: 2.1.198 /}As of v2.1.198, /login opens the sign-in dialog so you can sign in again without attaching to a session Skills, your own commands, and prompt-expanding built-ins such as /init are sent to a new background session as their first prompt. Other built-in commands show an attach to a session to run it hint instead.

The Version history table at the bottom of agent-view.md (around lines 654-669) currently lists a v2.1.202 row for the persistent /rename change and earlier rows back to v2.1.141, with no row for v2.1.203 yet.

What's Wrong or Missing?

A. The v2.1.203 composer fix is not reflected in the dispatch description

The v2.1.203 changelog records:

Fixed the claude agents composer discarding your typed message when a slash command isn't available there

After v2.1.203, pressing Enter in the agent view composer with a slash command that is not in the "runs in agent view itself" set and is not a skill, your own command, or a prompt-expanding built-in no longer throws away the rest of the text the user typed. The hint still appears (attach to a session to run it), and the typed prompt is kept so the user can decide what to do next instead of having to retype it. The current "From agent view" paragraph says only that the hint appears — it does not describe what happens to the surrounding prompt text in either direction (before or after the fix).

B. The docs leave a sharp edge undocumented for users who typed a multi-line prompt

Before v2.1.203, a user who typed something like /usage should also report token totals from yesterday and pressed Enter would see the hint and have their typed prompt disappear, so a longer prompt would have to be retyped from memory. The hint is the only documented outcome; the message-destruction side of that interaction is silently absent from the prose. After v2.1.203 the typed message is preserved instead of discarded, but the page does not say so, so a user reading the docs has no way to learn the composer now keeps their text when an unavailable slash command is typed.

C. The hint paragraph sits next to the new dispatch surface it doesn't fully describe

The paragraph beginning "Skills, your own commands, and prompt-expanding built-ins..." is the only paragraph on the page that explains what happens to a typed slash command in the composer. It already includes version-conditional notes ({/* min-version: 2.1.198 */} for /login, etc.), so adding a matching note for v2.1.203's typed-message preservation is the natural place to capture the fix without breaking the existing wording.

D. The Version history table has no v2.1.203 row

The version history table on agent-view.md is the page's summary of behavior changes per release, and other recent fixes (v2.1.202, v2.1.200, v2.1.199, v2.1.198) are recorded there. The v2.1.203 typed-message preservation has no row, so even if a user scrolls to the table to look up what changed, they will not see the fix listed.

Suggested Improvement

Option A: Comprehensive fix

In agent-view.md, extend the paragraph that begins "Skills, your own commands, and prompt-expanding built-ins..." to describe the typed-message preservation in addition to the hint, for example:

Skills, your own commands, and prompt-expanding built-ins such as /init are sent to a new background session as their first prompt. Other built-in commands show an attach to a session to run it hint instead, and your typed message is kept in the composer so you can edit it and dispatch from it instead of being lost. {/ min-version: 2.1.203 /}Before v2.1.203, pressing Enter with such a slash command discarded the typed message and showed only the hint.

Then add a row to the "Version history" table at the bottom of the same page:

| v2.1.203 | {/ min-version: 2.1.203 /}When the dispatch composer rejects a slash command with an attach to a session to run it hint, the typed prompt is preserved instead of being discarded, so you can edit it or dispatch from it without retyping. |

Option B: Minimum fix

Add only the {/* min-version: 2.1.203 */} clause to the existing paragraph (the "kept in the composer so you can edit it and dispatch from it" sentence), and skip the version history row.

Impact

Medium - Makes feature difficult to understand

Additional Context

The fix is part of the v2.1.203 release and is the counterpart to the earlier "Fixed claude agents sending builtin slash commands like /usage to background sessions as prompt text instead of showing a hint" entry (recorded on the same page around line 195). That earlier fix moved slash-command handling toward "show hint instead of dispatching"; the v2.1.203 fix is the matching user-protection step that the docs did not yet pick up.

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/agent-view | "From agent view" dispatch paragraph; Version history table at bottom of page |

Total scope: 1 page affected.

View original on GitHub ↗