claude-code - 💡(How to fix) Fix [DOCS] Worktree docs omit mid-session command behavior for `/tui` and `/update`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/common-workflows

Section/Topic

Run parallel Claude Code sessions with Git worktrees — specifically what happens when you enter a worktree during an existing session, and which in-session commands continue to work after that transition.

Current Documentation

The worktree docs currently say:

You can also ask Claude to "work in a worktree" or "start a worktree" during a session, and it will create one automatically.

The commands reference currently says:

The table below lists all the commands included in Claude Code.

The fullscreen page currently documents only the environment-variable path:

Set the CLAUDE_CODE_NO_FLICKER environment variable when starting Claude Code:

CLAUDE_CODE_NO_FLICKER=1 claude

The setup page currently documents only the CLI update flow:

To apply an update immediately without waiting for the next background check, run:

claude update

What's Wrong or Missing?

A. Mid-session worktree behavior is underspecified

The worktree docs confirm that Claude can enter or create a worktree during an existing session, but they stop there. They do not explain whether the current conversation continues in place after the transition, or whether built-in in-session commands are expected to keep working once Claude has switched into the worktree.

B. /tui is not documented where users would look for it

The v2.1.116 changelog entry shows that /tui is intended to work after entering a worktree mid-session, but the reference docs do not describe /tui in the commands reference, and the fullscreen page only documents enabling fullscreen rendering with CLAUDE_CODE_NO_FLICKER=1 at startup.

C. /update vs claude update is not clarified

The same changelog entry refers to /update, but the public docs currently describe only claude update. If /update is a supported in-session command, it is undocumented. If the intended user path is only claude update, the docs should say so explicitly to avoid confusion when release notes mention /update.

Suggested Improvement

Add a short subsection under the worktree docs for entering a worktree during an existing session that explains:

1. the session stays in the same conversation after the worktree transition,
2. built-in session commands are expected to remain available after the switch, and
3. command-specific docs should be used for the exact behavior of those commands.

Then update the related reference pages:

• Commands reference: add /tui, and add /update if it is user-facing.
• Fullscreen page: mention that fullscreen rendering can also be entered from inside a session with /tui fullscreen.
• Setup/update docs: clarify whether /update is supported in-session or whether updates are only performed with claude update.

That would make the workflow described by the v2.1.116 changelog discoverable without forcing users to infer behavior from release notes.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 5 pages affected

Source: Changelog v2.1.116

Exact changelog entry text: Fixed /update and /tui not working after entering a worktree mid-session