Bash output truncated: ctrl+o/ctrl+e don't fully expand output

Open 💬 18 comments Opened Feb 19, 2026 by sunnyszy

Description

Bash tool output is truncated in the conversation display. Pressing ctrl+o (expand) and ctrl+e does not reveal the full content — it remains collapsed.

Reproduction

Run a command that produces ~30-40 lines of output:

grep -i "load\|model\|neff" some-large-log.log 2>/dev/null | grep "NRT:" | head -40

The output renders as:

● Bash(grep -i "load\|model\|neff" ... | grep "NRT:" | head -40)
  ⎿  <first 3 lines shown>
     … +25 lines (ctrl+o to expand)

Pressing ctrl+o does not expand the remaining 25 lines.

Expected behavior

ctrl+o should expand all truncated lines so the full output is visible.

Environment

  • Claude Code CLI connected to Cursor IDE via /ide
  • Platform: Linux 6.8.0-1031-aws (Ubuntu 22.04)
  • gh version 2.87.0

🤖 Generated with Claude Code

View original on GitHub ↗

18 Comments

github-actions[bot] · 4 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/26685

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

sunnyszy · 4 months ago

This is general bash (e.g. grep here) instead of python.

robderon · 4 months ago

same problem under macOS 14.5 with zsh and python 3.12.3. here is what claude says about it :

me: output is truncated after a few lines and I cannot display them. ctrl+o does not show these lines                      
  ⎿  [Image 3]                                                                                                                              
                                                                                                                                             
claude: That's a Claude Code UI bug — the Ctrl+O expansion doesn't work for remaining lines during/after streaming. I can't fix that from my side. 
  You can report it at https://github.com/anthropics/claude-code/issues.       
tonglil · 4 months ago

ctrl+e does nothing

TrentonCasonSORS · 4 months ago

Still reproducible as of latest Claude Code (claude-opus-4-6, macOS Darwin 24.6.0, iTerm2, zsh).

Minimal reprex

Ask Claude Code to run this via the Bash tool:

seq 1 50

The output will truncate to something like:

● Bash(seq 1 50)
  ⎿  1
     2
     3
     … +47 lines (ctrl+o to expand)

Pressing ctrl+o does not expand the truncated lines. ctrl+e also has no effect.

The status bar shows Showing detailed transcript · ctrl+o to toggle · ctrl+e to collapse but neither shortcut affects the truncated tool output.

ThatDragonOverThere · 3 months ago

Still broken on v2.1.81 (Windows CLI). Now affecting agent output, not just Bash.

Agent returned a detailed verification checklist table + analysis. Middle section collapsed to "… +104 lines …" — Ctrl+O does nothing, lines are unrecoverable.

This was a quality gate verification for model training — the truncated content included validation thresholds and a TICK consensus analysis that I needed to review before approving the next pipeline step. Decision-relevant content silently hidden with no working expand mechanism.

v2.1.81 made this worse: "Improved MCP read/search tool calls to collapse into a single 'Queried {server}' line (expand with Ctrl+O)" — the collapsing is now more aggressive and extends beyond MCP/Bash to agent text output. Combined with Ctrl+O being broken, this is data loss.

A configurable collapseThreshold setting (or collapseToolOutput: false) has been requested in #31400, #33902, #34882, #37123, #37696. All closed as duplicates or ignored. This is now a functional regression, not a feature request.

ThatDragonOverThere · 3 months ago

Still broken on v2.1.85 (Windows CLI). Now co-occurring with paste truncation in the same message.

User pasted agent output containing a structured table + task status. Two things happened simultaneously:

  1. Paste truncation (#5017): 89 lines of the pasted content silently dropped ("… +89 lines …")
  2. Output collapse (#26954): Remaining visible content subject to the same collapse behavior — Ctrl+O still does nothing

This means both the input and output paths are silently eating content. The user pastes a table → lines vanish. An agent returns a report → lines vanish. There is no reliable way to get structured information into or out of Claude Code when it exceeds ~50 lines.

v2.1.84 changelog: No fix for collapse or Ctrl+O.
v2.1.85 changelog: No fix for collapse or Ctrl+O. "Reduced UI stutter when compaction triggers" and "Fixed stale content bleeding through when scrolling up during streaming" — scroll improvements but not this.

Versions confirmed broken: v2.1.81, v2.1.83, v2.1.84, v2.1.85. At least 5 releases since the prior comment with zero progress on this.

The workaround remains "write to file instead of returning inline" — but that doesn't help when the user is the one pasting content that gets truncated.

System: Windows 11, Node.js, Claude Code v2.1.85

asportnoy · 3 months ago

Still reproducible in 2.1.111. It expands some of the more recent calls, but if I have to scroll up in chat history, it doesn't work at all and there's no way to expand those.

ccmilu · 2 months ago

+1 — this regression has been frustrating to live with.

Repro: latest version (v2.1.126), macOS, Ghostty.

  • Long agent outputs / bash results get auto-collapsed
  • Ctrl+O "expands" them only to current viewport height
  • Anything beyond is silently truncated — scrollback shows nothing

Before this regression I could just scroll up to see the full thing.
Now I have to either resize the window taller before expanding, or
ask Claude to dump the output to a file and less it. Both feel
like papering over what used to just work.

Looks like the fix for #46834 (scrollback duplication on resize)
broke this. Hoping #26954 gets prioritized — losing the ability to
review long tool outputs in-place is a real productivity hit.

heinosasshallik · 1 month ago

Still an issue on 2.1.143

olejorgenb · 1 month ago

Claude Code does a lot well, but the bugginess are killing me... I absolutely get that they close down third-party usage for their subscription... That's the only thing keeping me from moving to another harness where I at least can fix things myself (pi, opencode, etc.)

AgarwalPragy · 1 month ago

/tui fullscreen fixes this for me - claude runs in its own viewport which makes rendering a lot less buggy.

ccmilu · 1 month ago
/tui fullscreen fixes this for me - claude runs in its own viewport which makes rendering a lot less buggy.

Thank you for sharing; this actually solved my problem.

robderon · 1 month ago

Merci ! Pourrions nous échanger au tel dans la journée ?

Le jeu. 28 mai 2026 à 18:24, Jason Chang @.***> a
écrit :

ccmilu left a comment (anthropics/claude-code#26954) <https://github.com/anthropics/claude-code/issues/26954#issuecomment-4566121709> /tui fullscreen fixes this for me - claude runs in its own viewport which makes rendering a lot less buggy. Thank you for sharing; this actually solved my problem. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/26954?email_source=notifications&email_token=AHDRFJHFPGU2KXKBRWBMYRT45BR3PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGYYTEMJXGA42M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4566121709>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHDRFJFR33UVHFWMLDM7AV345BR3PAVCNFSM6AAAAACVXEPOGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNRWGEZDCNZQHE> . You are receiving this because you commented.Message ID: @.***>

--
Benjamin BEJNBAUM
@.***
+33 6 12 56 50 41

FelixIsaac · 1 month ago

Still an issue for me. 2.1.175. Doing /tui fullscreen helps but the issue remains.

alekpaul · 21 days ago

Still issue and same with just thinking process, I can't see the chain of thoughts

Leksat · 18 days ago

My workaround:

  • Log details to /tmp/claude.log via Claude Code hooks
  • Keep tail -f /tmp/claude.log in a separate terminal tab
bukzor · 10 days ago

Reproduced this outside the /ide path too — plain terminal (kitty terminal + tmux), Claude Code 2.1.201, Linux. Same symptom: Bash output collapsed, ctrl+o and ctrl+e (transcript:toggleShowAll per keybindings.json) have no effect, in or out of tmux, in both the main view and the transcript/message-selector views.

Found a workaround: setting "tui": "default" in settings.json (instead of "fullscreen", which is the current default) makes the full output render immediately, no ctrl+o/ctrl+e needed. So this looks specific to the fullscreen/no-flicker renderer — ctrl+e in the Transcript context appears to be a dead binding there regardless of terminal/multiplexer.

🤖 Generated with Claude Code