[DOCS] `claude agents` `@` directory picker docs omit registered git worktrees; v2.1.203 fix is not reflected in `agent-view.md`

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

The "Dispatch to a specific directory" subsection of agent-view.md (around the @<repo> bullet that describes what typing @ lists), plus the "Version history" table at the bottom of the same page.

Current Documentation

The "Dispatch to a specific directory" list at https://code.claude.com/docs/en/agent-view currently describes the @ directory picker as listing only two sources:

* Open claude agents in a parent directory and mention a child repository with @<repo> in the prompt. Typing @ lists git repositories one level below the launch directory, plus any directory that already has a session in the list. A directory whose name contains a space isn't listed.

The "Version history" table at the bottom of the same page skips from v2.1.202 (a /rename persistence fix) down to v2.1.200 (an older supervisor field-preservation fix) and never adds a row for v2.1.203.

The "How file edits are isolated" section on the same page documents registered git worktrees created elsewhere on the system:

* The session is already inside a linked git worktree, whether Claude created it under .claude/worktrees/ or you created it with git worktree add somewhere else

— confirming that linked worktrees registered with git worktree add are a real surface, even though the @ picker docs do not mention them.

What's Wrong or Missing?

A. The picker source list omits registered git worktrees

The v2.1.203 changelog records:

Fixed the @ directory picker in claude agents not showing registered git worktrees

Before v2.1.203, registered git worktrees (those created with git worktree add and listed by git worktree list, whether they live under .claude/worktrees/ or anywhere else on the same machine) did not appear in the @ directory picker when you launched claude agents from a parent directory. After v2.1.203 they are a third source alongside "git repositories one level below the launch directory" and "any directory that already has a session in the list."

The current bullet enumerates the pre-fix sources only. Nothing on the page tells a reader that registered worktrees are now listed, so a user who registered a worktree with git worktree add and then opened claude agents from the parent directory has no docs entry to explain why that worktree now appears in the picker.

B. The version history table has no v2.1.203 row

The version history table at the bottom of agent-view.md lists the v2.1.202 row but jumps directly to v2.1.200 for the next entry. The v2.1.203 picker fix therefore has no version-history marker, even though the same table already documents v2.1.202 and v2.1.200 changes in the same area.

Suggested Improvement

A. Update the "Dispatch to a specific directory" bullet to include registered git worktrees

Add a sentence so the picker source list matches v2.1.203 behavior. For example, replace:

* Open claude agents in a parent directory and mention a child repository with @<repo> in the prompt. Typing @ lists git repositories one level below the launch directory, plus any directory that already has a session in the list. A directory whose name contains a space isn't listed.

with:

Open claude agents in a parent directory and mention a child repository with @<repo> in the prompt. Typing @ lists git repositories one level below the launch directory, plus any directory that already has a session in the list and any registered git worktree under one of those repositories. A directory whose name contains a space isn't listed. {/ min-version: 2.1.203 */}As of v2.1.203 the picker also lists worktrees registered with git worktree add so you can dispatch into them without opening claude agents in the worktree directory first.

B. Add a v2.1.203 row to the version history table

Add a row above the existing v2.1.202 row in the "Version history" table at the bottom of agent-view.md. For example:

| v2.1.203 | {/ min-version: 2.1.203 /}The @ directory picker in agent view lists git worktrees registered with git worktree add, so you can dispatch into them without opening claude agents in the worktree directory first. |

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | ~294 | "Dispatch to a specific directory" bullet describing what the @ picker lists |
| https://code.claude.com/docs/en/agent-view | ~654 | "Version history" table — no v2.1.203 row |

Related docs that already describe registered worktrees:

The same page already mentions worktrees registered with git worktree add in the "How file edits are isolated" subsection, so the picker bullet can use the same terminology without introducing new vocabulary.

The user-facing CLI --worktree flag in https://code.claude.com/docs/en/cli-reference and the worktrees guide in https://code.claude.com/docs/en/worktrees both describe git worktree add and git worktree list as the supported way to create and inspect registered worktrees.

Version: Claude Code v2.1.203