claude-code - 💡(How to fix) Fix [DOCS] `/terminal-setup` GPU acceleration disablement for VS Code/Cursor/Windsurf undocumented

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

The "Enter multiline prompts" section, specifically the /terminal-setup command description for VS Code, Cursor, and Windsurf terminals.

Current Documentation

From the terminal-config page:

For VS Code, Cursor, Windsurf, Alacritty, and Zed, /terminal-setup writes Shift+Enter and other keybindings into the terminal's configuration file. In VS Code, Cursor, and Windsurf it also sets terminal.integrated.mouseWheelScrollSensitivity in the editor settings for smoother scrolling in fullscreen mode.

From the commands reference:

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

Neither page mentions that /terminal-setup disables GPU acceleration.

What's Wrong or Missing?

As of v2.1.157, /terminal-setup now disables GPU acceleration in VS Code, Cursor, and Windsurf integrated terminals to prevent garbled-text rendering. This behavior change is documented in the changelog but not in the terminal-config or commands reference pages.

Users who run /terminal-setup may notice GPU acceleration is disabled without understanding why, and users experiencing garbled text may not know that /terminal-setup can resolve the issue — since the documentation only describes keybinding and scroll-sensitivity changes.

Suggested Improvement

Add a sentence to the /terminal-setup description on the terminal-config page (after the existing mouseWheelScrollSensitivity sentence):

It also disables GPU acceleration (terminal.integrated.gpuAcceleration) in the editor settings. GPU acceleration can cause garbled-text rendering in Claude Code's fullscreen mode in these terminals, so disabling it prevents display corruption.

Similarly, update the commands reference entry to mention GPU acceleration handling.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageSectionContext
https://code.claude.com/docs/en/terminal-configEnter multiline prompts (line ~32)/terminal-setup description omits GPU disablement
https://code.claude.com/docs/en/commands/terminal-setup rowCommand summary omits GPU disablement

Total scope: 2 pages affected

The changelog for v2.1.157 reports: "/terminal-setup now disables GPU acceleration in VS Code/Cursor/Windsurf integrated terminals to prevent garbled-text rendering." The terminal-config page already documents the keybinding and scroll-sensitivity changes that /terminal-setup applies; the GPU acceleration change belongs alongside those.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] `/terminal-setup` GPU acceleration disablement for VS Code/Cursor/Windsurf undocumented