[BUG] iTerm conversation history reappears after Command+K when running commands with long output
Resolved 💬 3 comments Opened Dec 12, 2025 by nmurphy4 Closed Dec 12, 2025
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When using Claude Code in iTerm2, the conversation history persistently reappears even after clearing the terminal with Command+K. This behavior is particularly problematic during compilation tasks.
The conversation history is re-rendered/redisplayed in the terminal, causing:
- Scroll position to jump to the beginning of the conversation
- Terminal to become cluttered with previously cleared content
- Poor user experience during iterative development tasks
Environment:
- OS: macOS (Darwin 24.6.0)
- Terminal: iTerm2
- Project type: SBT/Scala project
- Claude Code version: [you'll need to add this - run claude --version]
What Should Happen?
After clearing the terminal with Command+K, the conversation history should remain cleared.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce:
- Have a conversation with Claude Code with multiple exchanges
- Ask Claude to run a command that produces output (e.g., sbt compile)
- Clear terminal history with Command+K
- Ask Claude to run another command or continue working
- Observe that the previously cleared conversation history reappears
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.67
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗