[BUG] Fullscreen renderer: cannot scroll at input prompt (mouse wheel, PgUp/PgDn, Ctrl+Home/End non-functional)

Open 💬 1 comment Opened Jun 23, 2026 by cscalfani

Preflight Checklist

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

What's Wrong?

When using the fullscreen renderer, scrolling through displayed content while waiting at an interactive prompt does not work via any of the documented methods except Ctrl+O. This is particularly problematic when reviewing a plan or long MCP output before responding.

Expected behavior

All of the above methods should scroll the displayed content while waiting at an interactive prompt.

Actual behavior

None of the above methods work. Only Ctrl+O (transcript mode) allows reviewing the content.

Environment

  • Claude Code: 2.1.186
  • macOS: 26.4 (Build 25E246)
  • Terminal: iTerm2 Build 3.6.11
  • Mouse reporting: enabled (iTerm2 Settings → Profiles → Terminal → Enable mouse reporting)
  • tmux: not in use
  • CLAUDE_CODE_DISABLE_MOUSE: not set

What Should Happen?

It should work as promised

Error Messages/Logs

Steps to Reproduce

  1. Launch Claude Code in fullscreen renderer mode
  2. Have a conversation long enough that earlier messages are off-screen
  3. Trigger a prompt that requires user input, e.g.:
  • Entering plan mode (a plan is displayed awaiting approval)
  • Running /mcp (MCP server list is displayed)
  • Any other interactive prompt with substantial output
  1. Attempt to scroll up through the displayed content using:
  • Mouse wheel / trackpad scroll
  • PgUp / PgDn
  • Ctrl+Home / Ctrl+End

Claude Model

_No response_

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.186

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗