[BUG] PgUp/PgDn not scrolling — Scroll context activates (cursor hides) but viewport doesn't move on Windows

Open 💬 0 comments Opened Jul 14, 2026 by WangSilas

Environment

  • Claude Code version: v2.1.208 (also reproduced on v2.1.207)
  • Previous working version: pre-v2.1.207 (PgUp/PgDn worked before update)
  • OS: Windows 11 (Build 26200)
  • Shell: PowerShell 7
  • Terminal: Windows Terminal

Regression confirmed

PgUp/PgDn worked correctly before updating to v2.1.207. After the auto-update, they stopped working. Upgrading to v2.1.208 does NOT fix it. This is a regression.

Symptoms

Pressing PgUp or PgDn does NOT scroll the conversation content.

Key diagnostic finding: the terminal cursor disappears when PgUp/PgDn is pressed, confirming the Scroll context is activated and scroll:pageUp / scroll:pageDown actions are dispatched — but the Ink renderer fails to update the visible viewport.

What works

  • Ctrl+Home (jump to top)
  • Ctrl+End (jump to bottom)
  • Mouse wheel scrolling
  • Ctrl+o transcript mode

What doesn't work

  • PgUp — cursor hides, nothing moves
  • PgDn — cursor hides, nothing moves

Additional context

  • Happens both with CLAUDE_CODE_NO_FLICKER=1 and without it
  • PSReadLine has default ScrollDisplayUp/ScrollDisplayDown bindings for PgUp/PgDn, but these are dormant when Claude Code has stdin — confirmed NOT the cause
  • Periodic terminal freezes (2-5 seconds of complete unresponsiveness) also observed, possibly related to the Ink renderer's full-screen redraw behavior on Windows ConPTY
  • NOT the same as #12953 (no input history cycling occurs)
  • NOT the same as #65688 (this is CLI, not Desktop Cowork mode)

Likely root cause

The Ink renderer's scroll:pageUp / scroll:pageDown actions execute correctly (cursor hides = Scroll context activated), but the rendering pipeline fails to translate the new scroll position into visible output on Windows ConPTY. This is a rendering-layer bug that was introduced or exposed in v2.1.207.

View original on GitHub ↗