[BUG] Agent View: attached session scroll completely broken on macOS (Ghostty + Warp)

Status Fixed / completed
Reported on v2.1.143
Maintainer reply ✓ Yes — bogini
Activity 8 comments · opened May 17, 2026 · closed May 27, 2026
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

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

What's Wrong?

When a session is attached via Agent View on macOS, all built-in scroll mechanisms become unresponsive:

  • PgUp / PgDn (Fn+↑ / Fn+↓ on MacBook): no effect
  • Ctrl+O transcript mode: opens, but inside transcript view j, k, Space, b, g, G, Ctrl+F, Ctrl+B, PgUp, PgDn all fail to scroll
  • [ shortcut to dump conversation to terminal scrollback: inserted as literal text into input box

Any output longer than the viewport becomes effectively unreadable inside attached Agent View sessions.

What Should Happen?

Per documentation, fullscreen sessions should respond to PgUp/PgDn for half-page scroll, and Ctrl+O should open a functional less-style transcript viewer where j/k/Space/PgUp navigate normally. The [ shortcut should dump the conversation into the terminal's native scrollback buffer.

Steps to Reproduce

Two equivalent reproduction paths, identical outcome:

Path A:

  1. claude agents (open Agent View)
  2. Create a new session from the Agent View UI
  3. Press Enter to attach
  4. Generate output longer than the viewport, e.g. ask Claude: 请数 1 到 100,每个数字一行
  5. Try Fn+↑ (PgUp) → no effect
  6. Try Ctrl+O → transcript opens but j, k, Space, PgUp all do nothing
  7. Try [ → typed as literal [ into input box

Path B (same end result):

  1. Start a regular claude session
  2. Press on empty input to navigate into Agent View
  3. Re-enter the session
  4. Same scroll failure as Path A

Is this a regression?

I don't know — Agent View was introduced in 2.1.139, so this has been broken since the feature shipped (no prior working baseline I can confirm).

Claude Code Version

2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

macOS 26.4.1 (build 25E253)

Terminal/Shell

Other — primary: Ghostty 1.3.1; also reproduced on Warp (see Additional Information)

Additional Information

Cross-terminal repro (rules out terminal-side issue):

  • ✅ Reproduces in Ghostty 1.3.1 on macOS 26.4.1
  • ✅ Reproduces in Warp (latest) on the same machine

Control — regular claude (no Agent View) works as expected:

  • Classic mode + terminal native scrollback functions normally (Cmd+↑/↓, mouse wheel)
  • This confirms the issue is specific to Agent View's attached session rendering path, not the terminal or the PgUp key code

Key-code sanity check: Fn+↑ correctly emits ^[[5~ in cat -v outside Claude Code, so the PgUp escape sequence is reaching the application.

Related but distinct issues:

  • #59093 — TUI scroll buffer limited to ~10 lines (about buffer size in peek mode, not key responsiveness in attached mode)
  • #58925 — stale artifacts on Windows (Windows-specific rendering glitch, now closed)

Workaround: Avoid attaching via Agent View. Use regular claude sessions in separate terminal tabs. Use Agent View only for monitoring/dispatch (never Enter to attach).

View original on GitHub ↗

8 Comments

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/59633
  2. https://github.com/anthropics/claude-code/issues/58925
  3. https://github.com/anthropics/claude-code/issues/27242

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

linqibin0826 · 3 months ago

Cross-referencing #59633 (flagged by the duplicate-detector bot).

Partial overlap, but distinct scope:

#59633 reports that Ctrl+O transcript view's scroll keys (j/k/arrows/Ctrl+U/Ctrl+D/g/G/Home/End/PgUp/PgDn) are unresponsive in a plain claude session on Linux 2.1.138. That overlaps with one symptom in this report.

This issue adds:

  • Agent View attached session context (which #59633 cannot cover — they're on 2.1.138, before Agent View shipped in 2.1.139)
  • PgUp / PgDn failure in the main conversation view (outside transcript), specific to Agent View attached state
  • [ shortcut typed as literal text instead of dumping conversation to scrollback
  • macOS confirmation + cross-terminal repro (Ghostty 1.3.1 and Warp), complementing #59633's Linux data point

The Ctrl+O scroll failure may share a root cause with #59633, but the Agent View-specific failures (main-view PgUp, [ shortcut, attached-session entry paths) deserve to stay tracked here for maintainers to disposition.

Requesting this stays open pending maintainer review — opting out of the 3-day auto-close.

IkamG · 3 months ago

I am also experiencing this issue. Only with agents view

nzorndorf · 3 months ago

Same issue. Only with claude agents view.

bogini collaborator · 3 months ago

Addressed by a merged fix. Please reopen with a fresh repro if you still see this on a current version.

cades-cheehoo · 3 months ago

I used to use Ctrl+B [ to enter scrollable mode in tmux, in agent view this way is broken.

But I found I can use trackpad/mouse to scroll the content. Fn + Up/Down also work like PgUp/PgDown.

Need to change my habbit, but I feed this UX is better.

henricook · 3 months ago

Scrolling in claude agents (when inside an agent's session) is still broken for me on Terminator/Linux even running the version released yesterday. I don't have permissions to reopen this issue though.

Definition of broken: Using the mouse wheel starts scrolling command history, instead of the output.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.