claude-code - 💡(How to fix) Fix [BUG] Fullscreen TUI default (~v2.1.150) breaks macOS VoiceOver / screen-reader access in Terminal.app

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…

Error Message

Error Messages/Logs

Root Cause

This is raised specifically as an accessibility regression caused by a default change, distinct from the general "I can't copy text" reports.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Since fullscreen TUI rendering became the default (around v2.1.150), Claude Code captures mouse events and takes over the terminal via the alternate screen, which prevents normal terminal text selection. This breaks both macOS VoiceOver and macOS Speak Selection, the built-in assistive features that read terminal content and selected text aloud. With fullscreen as the default, Claude Code's output cannot be read by either feature out of the box; it only works after switching to the /tui default mode.

This is raised specifically as an accessibility regression caused by a default change, distinct from the general "I can't copy text" reports.

What Should Happen?

VoiceOver reads the output content, and click-and-drag selection works so Speak Selection reads the selected text aloud, as both did before fullscreen became the default.

Error Messages/Logs

Steps to Reproduce

  1. Launch Claude Code in Terminal.app on a version ≥ 2.1.150 (fullscreen is the default).
  2. Let Claude produce some output.
  3. Attempt to read the output with VoiceOver

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.149

Claude Code Version

2.1.156

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

For VoiceOver and Speak Selection users, a default that takes over the terminal and captures the mouse means the tool's output cannot be read at all until an obscure command is discovered, which a new accessibility dependent user may never find. This is a hard barrier rather than a minor annoyance.

This new default may be controlled by a server-side feature flag rather than tied to a specific release. Related to https://github.com/anthropics/claude-code/issues/61936

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 [BUG] Fullscreen TUI default (~v2.1.150) breaks macOS VoiceOver / screen-reader access in Terminal.app