Claude Code Digest — 2026-04-02 00:36:46
What the docs reveal
The TUI Ambition
Anthropic added a strict configuration requirement to the interactive fullscreen mode. Mac developers using iTerm2 must now enable "mouse reporting" in their application profiles. This toggle transforms Claude Code from a rigid text stream into a responsive interface, unlocking mouse wheel scrolling, click-to-expand widgets, and precise text selection.
Standard terminal emulators capture mouse output to manage native scrolling and basic block highlighting. By demanding raw mouse data, Anthropic explicitly bypasses the terminal emulator to handle all user interface interactions internally. Engineering teams rarely demand profile changes unless the architectural payoff justifies the friction. Here, Anthropic chose to sacrifice zero-configuration onboarding to achieve an IDE-like experience inside the shell.
The Support Ticket Reality
This specific documentation update almost certainly arose from an influx of bug reports. When developers launch a fullscreen terminal tool, they expect intuitive cursor controls. Users undoubtedly voiced frustration over broken scrolling mechanics while reading large codebase diffs. Others likely struggled to copy generated code snippets because the terminal intercepted their click-and-drag motions, resulting in malformed selections. Documenting the iTerm2 profile requirement serves as Anthropic's preemptive strike against degraded user experiences.
The Developer Mandate
Check your iTerm2 settings before your next coding session. Without raw mouse reporting, Claude Code's fullscreen mode devolves from an interactive assistant into a static obstacle. Navigating sprawling context windows will require tedious keystrokes. Extracting optimized code blocks will become a fight against standard terminal highlighting. Flip the configuration switch, restart your terminal session, and reclaim command of the interface.