[DOCS] /terminal-setup docs omit fullscreen scroll-sensitivity setup for VS Code, Cursor, and Windsurf

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/terminal-config

Section/Topic

Set up Shift+Enter with /terminal-setup and the related fullscreen scrolling guidance

Current Documentation

The terminal setup page currently says:

Run /terminal-setup within Claude Code to automatically configure Shift+Enter for VS Code, Alacritty, Zed, and Warp. The /terminal-setup command is only visible in terminals that require manual configuration. If you're using iTerm2, WezTerm, Ghostty, or Kitty, you won't see this command because Shift+Enter already works natively.

The fullscreen page currently says:

If mouse wheel scrolling feels slow, your terminal may be sending one scroll event per physical notch with no multiplier. Some terminals, like Ghostty and iTerm2 with faster scrolling enabled, already amplify wheel events. Others, including the VS Code integrated terminal, send exactly one event per notch. Claude Code cannot detect which. Set CLAUDE_CODE_SCROLL_SPEED to multiply the base scroll distance:

The commands reference currently says:

/terminal-setup | Configure terminal keybindings for Shift+Enter and other shortcuts. Only visible in terminals that need it, like VS Code, Alacritty, or Warp

What's Wrong or Missing?

Changelog v2.1.116 added a new user-visible behavior: Smoother fullscreen scrolling in VS Code, Cursor, and Windsurf terminals — /terminal-setup now configures the editor's scroll sensitivity.

The current docs still describe /terminal-setup as a newline/shortcut helper. They do not explain that it now also configures editor scroll sensitivity for smoother fullscreen scrolling in supported editor terminals, and they do not mention Cursor or Windsurf in the relevant setup pages.

As written, the docs leave users with only the manual CLAUDE_CODE_SCROLL_SPEED workaround on the fullscreen page, so users in VS Code-, Cursor-, and Windsurf-based terminals are unlikely to discover the new /terminal-setup behavior.

Suggested Improvement

Update the /terminal-setup documentation to describe both responsibilities of the command:

1. newline/keybinding setup where needed
2. editor scroll-sensitivity setup for smoother fullscreen scrolling in VS Code, Cursor, and Windsurf terminals

Suggested doc changes:

• Expand https://code.claude.com/docs/en/terminal-config to state that /terminal-setup can adjust editor scroll sensitivity in supported editor terminals, not just Shift+Enter behavior.
• Update the supported editor list anywhere /terminal-setup is summarized so Cursor and Windsurf are included where applicable.
• Add a cross-reference from https://code.claude.com/docs/en/fullscreen near CLAUDE_CODE_SCROLL_SPEED, clarifying when users should run /terminal-setup first versus changing CLAUDE_CODE_SCROLL_SPEED manually.
• If /terminal-setup changes a specific editor preference, document the affected setting and whether the change requires confirmation or reload.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/terminal-config | 34-39 | /terminal-setup is documented only as Shift+Enter setup for VS Code, Alacritty, Zed, and Warp |
| https://code.claude.com/docs/en/commands | 90 | /terminal-setup is summarized as keybinding/shortcut setup only |
| https://code.claude.com/docs/en/interactive-mode | 72-74 | Tip tells users to run /terminal-setup only to install Shift+Enter |
| https://code.claude.com/docs/en/fullscreen | 90-100 | Slow scrolling guidance points readers to CLAUDE_CODE_SCROLL_SPEED but not /terminal-setup or editor scroll-sensitivity setup |

Total scope: 4 pages affected

Source: Changelog v2.1.116

Exact changelog entry: Smoother fullscreen scrolling in VS Code, Cursor, and Windsurf terminals — /terminal-setup now configures the editor's scroll sensitivity

Windsurf does not appear in the current Claude Code docs mirror, so editor-specific users currently have no discoverable documentation path for this setup.