[BUG] Terminal State Corruption during /memory Command
Resolved 💬 7 comments Opened Aug 13, 2025 by benceferdinandy-signifyd Closed Jan 3, 2026
Environment
- Platform (select one):
- [X] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.77
- Operating System: macOS 15.6
- Terminal: ghostty, contour, macos terminal
- EDITOR: vim, vim -u NONE, nano
Bug Description
When trying to navigate in /memory, the terminal state goes complete bonkers, the claude TUI seeps through, and nothing is showing in the right place:
<img width="2270" height="730" alt="Image" src="https://github.com/user-attachments/assets/c011bd20-a467-4410-8df4-82534cfdfb31" />
Steps to Reproduce
Open /memory move about a bit, observe that things are not good. Note that this also happens with vim -u NONE as EDITOR so it's not related to my vim config.
Expected Behavior
Terminal doesn't break.
Actual Behavior
Terminal breaks.
Additional Context
This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗