You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Session freezes when reading persisted-output tool-results file after large Bash output #18095
I have searched existing issues and this hasn't been reported yet
This is a single bug report (please file separate reports for different bugs)
I am using the latest version of Claude Code
What's Wrong?
Claude Code session freezes indefinitely when attempting to Read a tool-results file that was created from a large Bash command output (<persisted-output>).
When Bash output exceeds ~30KB, it gets saved to a tool-results file. When Claude then tries to Read that file, the session becomes completely unresponsive - stuck in "Perusing..." state. Escape key does not work, and Ctrl+C requires multiple presses to interrupt. Only recovery is force exit and claude --continue.
What Should Happen?
Claude should successfully read the tool-results file and continue processing normally.
Error Messages/Logs
No error message displayed. Session simply hangs with no output.
The last visible output before freeze:
● Read(~/.claude/projects/.../tool-results/toolu_xxx.txt)
Then nothing - no response, no error, just frozen.
Steps to Reproduce
Run a Bash command that produces large output (>30KB):
gh pr diff
Observe the output is saved to a persisted-output file:
Claude attempts to Read the persisted tool-results file to analyze the diff
Session freezes - no response, stuck state
Note: The freeze occurs specifically when Claude's Read tool attempts to access the tool-results file created from large Bash output. Tested with gh pr diff producing ~34KB output.
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.
Activity
github-actions commentedon Feb 27, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Mar 9, 2026
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.