[DOCS] Fullscreen docs omit the v2.1.191 fix that makes Cmd+click on links work in Ghostty over SSH/tmux

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/fullscreen

Section/Topic

The Use the mouse section, specifically the bullet describing Cmd+click / Ctrl+click on URLs and file paths, plus the What changes comparison table that summarizes the same gesture. The Use with tmux section is the natural place for an SSH/tmux-side caveat, since it already calls out other tmux-specific issues with fullscreen rendering.

Current Documentation

The What changes table says:

Cmd-click to open a URL | Cmd-click on macOS, Ctrl-click elsewhere | [Use the mouse](#use-the-mouse)

The Use the mouse bullet says:

Hold Cmd on macOS, or Ctrl on Linux and Windows, and click a URL or file path to open it. File paths in tool output, like the ones printed after an Edit or Write, open in your default application. Plain http:// and https:// URLs open in your browser. {/ min-version: 2.1.181 /}As of v2.1.181, a plain click without holding Cmd or Ctrl no longer opens links, matching native terminal behavior. In the VS Code integrated terminal and similar xterm.js-based terminals, Claude Code defers to the terminal's own link handler, which uses the same gesture.

The Use with tmux section only discusses wheel scrolling, alternate screen buffers, and iTerm2 tmux integration mode:

Fullscreen rendering works inside tmux, with three caveats. Mouse wheel scrolling requires tmux's mouse mode. If your ~/.tmux.conf does not already enable it, add this line and reload your config: ``bash theme={null} set -g mouse on ` Without mouse mode, wheel events go to tmux instead of Claude Code. Keyboard scrolling with PgUp and PgDn works either way. Claude Code prints a one-time hint at startup if it detects tmux with mouse mode off. Fullscreen rendering is incompatible with iTerm2's tmux integration mode, which is the mode you enter with tmux -CC. In integration mode, iTerm2 renders each tmux pane as a native split rather than letting tmux draw to the terminal. The alternate screen buffer and mouse tracking do not work correctly there: the mouse wheel does nothing, and double-click can corrupt the terminal state. Don't enable fullscreen rendering in tmux -CC sessions. Regular tmux inside iTerm2, without -CC`, works fine. tmux does not support synchronized output, so you may see more flicker during redraws than when running Claude Code directly in your terminal. If the flicker is noticeable, especially over SSH, run Claude Code in its own terminal tab outside tmux.

What's Wrong or Missing?

The docs currently imply that the Cmd+click / Ctrl+click URL gesture is universal inside fullscreen rendering. Claude Code v2.1.191 fixed a real bug where that gesture did not open links when Claude Code was running inside a Ghostty session that was forwarded over SSH, including Claude Code running inside tmux on the same remote host. After v2.1.191, the gesture works in that environment.

Nothing in the user-facing docs tells readers about the changed surface:

A. The Use the mouse bullet does not mention Ghostty over SSH/tmux

The bullet promises Cmd+click / Ctrl+click works "to open it" for URLs and file paths. It carries a min-version: 2.1.181 comment to mark the prior behavior change, but no equivalent marker for the v2.1.191 fix. A reader on a Ghostty-over-SSH session who upgraded past v2.1.191 has no in-page signal that this combination is now supported.

B. The What changes summary table does not mention the v2.1.191 fix

The Cmd-click row of the What changes table just says Cmd-click on macOS, Ctrl-click elsewhere, with no terminal-environment caveat. Users on Ghostty over SSH/tmux who hit the broken pre-v2.1.191 behavior have nothing in that summary to tell them it changed.

C. The Use with tmux section is silent on link clicking

The tmux section enumerates wheel scrolling, iTerm2 tmux -CC integration, and synchronized-output flicker. It does not mention that link clicks needed a v2.1.191 fix in Ghostty-forwarded sessions, so a reader who already knows about the other tmux caveats will not find the link-click caveat there either.

Suggested Improvement

Mirror the existing min-version pattern for the v2.1.181 plain-click change. Apply the same idea to the v2.1.191 Ghostty-over-SSH/tmux fix.

Append a sentence to the Cmd+click URL bullet:

Hold Cmd on macOS, or Ctrl on Linux and Windows, and click a URL or file path to open it. File paths in tool output, like the ones printed after an Edit or Write, open in your default application. Plain http:// and https:// URLs open in your browser. {/ min-version: 2.1.181 /}As of v2.1.181, a plain click without holding Cmd or Ctrl no longer opens links, matching native terminal behavior. In the VS Code integrated terminal and similar xterm.js-based terminals, Claude Code defers to the terminal's own link handler, which uses the same gesture. {/ min-version: 2.1.191 /}As of v2.1.191, this also works in Ghostty when Claude Code is running over SSH, including from inside a tmux session on the remote host.

Add a corresponding note in Use with tmux:

tmux does not support synchronized output, so you may see more flicker during redraws than when running Claude Code directly in your terminal. If the flicker is noticeable, especially over SSH, run Claude Code in its own terminal tab outside tmux. {/ min-version: 2.1.191 /}In Ghostty sessions reached over SSH, Cmd+click / Ctrl+click on URLs and file paths only started working in v2.1.191. Upgrade Claude Code with claude update if Cmd+click on a link silently does nothing in this configuration.

Optionally extend the What changes table footnote (or the Use the mouse link target) so the summary callout matches.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/fullscreen | 43 | What changes table row for Cmd-click URL opening does not mention the v2.1.191 Ghostty-over-SSH/tmux fix |
| https://code.claude.com/docs/en/fullscreen | 55 | Use the mouse bullet for Cmd+click / Ctrl+click on URLs and file paths only marks the v2.1.181 plain-click change, not the v2.1.191 Ghostty-over-SSH fix |
| https://code.claude.com/docs/en/fullscreen | 135-149 | Use with tmux section covers wheel scrolling, iTerm2 tmux -CC, and synchronized-output flicker, but does not mention the v2.1.191 link-click fix |
| https://code.claude.com/docs/en/changelog | 32 | Adjacent prior fix: v2.1.187 Fixed Cmd+click not opening URLs in fullscreen mode in Ghostty on macOS — same surface, different code path (local macOS Ghostty vs SSH-forwarded Ghostty) |

Total scope: 1 page affected (fullscreen), with a related prior fix in the same surface already in the changelog.

Related prior fix: Claude Code v2.1.187 fixed the same gesture for native Ghostty on macOS. v2.1.191 extends that coverage to Ghostty forwarded over SSH, including from inside a tmux session on the remote host. The Use the mouse bullet already uses min-version markers to record these per-version behavior changes, so adding a v2.1.191 marker follows the existing documentation pattern instead of inventing a new one.

Version context: Claude Code v2.1.191 changelog: Fixed Cmd+click on links in fullscreen mode for Ghostty over ssh/tmux.