Bug
When working in a long Claude Code session, the terminal only shows approximately 250 lines of history. The full session transcript exists on disk (this particular session is 158KB+ with hundreds of exchanges), but the terminal scrollback is hard-capped so users cannot scroll up to see earlier conversation turns. My local terminal history is set to 20000 lines and ONLY in Claude Code context am I seeing this cap.
Steps to Reproduce
- Have a long Claude Code session (500+ exchanges)
- End the session
- Revive it with
claude --resume or via telec sessions revive <id> --agent claude
- Try to scroll up in the terminal to see earlier conversation history
Expected Behavior
The full session history should be visible in the terminal scrollback, or at minimum there should be a way to page through the full transcript.
Actual Behavior
Only the last ~250 lines of the session are visible. Everything before that is cut off. The user cannot review what happened earlier in the session.
Impact
This makes revived sessions much less useful — the main reason to revive a session is to recover context from a prior conversation, but if you can't see what happened before the truncation point, that context is inaccessible.
Environment
- Claude Code v2.1.76
- macOS (Darwin 25.3.0)
- Terminal: tmux
Bug
When working in a long Claude Code session, the terminal only shows approximately 250 lines of history. The full session transcript exists on disk (this particular session is 158KB+ with hundreds of exchanges), but the terminal scrollback is hard-capped so users cannot scroll up to see earlier conversation turns. My local terminal history is set to 20000 lines and ONLY in Claude Code context am I seeing this cap.
Steps to Reproduce
claude --resumeor viatelec sessions revive <id> --agent claudeExpected Behavior
The full session history should be visible in the terminal scrollback, or at minimum there should be a way to page through the full transcript.
Actual Behavior
Only the last ~250 lines of the session are visible. Everything before that is cut off. The user cannot review what happened earlier in the session.
Impact
This makes revived sessions much less useful — the main reason to revive a session is to recover context from a prior conversation, but if you can't see what happened before the truncation point, that context is inaccessible.
Environment