[BUG] Text Garbling in Plan Mode Question Selection
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?
Bug Report: Text Garbling in Plan Mode Question Selection
Description:
When navigating through answer options during plan mode using AskUserQuestion tool, the text becomes progressively
garbled and unreadable as I move between options with arrow keys. Characters overlap and mix together, making the
interface unusable.
Environment:
- Claude Code version: 2.1.19
- OS: macOS Darwin 24.6.0
- Terminal: Terminal.app (default macOS terminal)
- TERM variable: xterm-256color
What Should Happen?
Expected Behavior:
Text should remain clear and readable while navigating options, with proper redrawing of the selection interface.
Actual Behavior:
Characters overlap and mix together, creating unreadable garbled text. The corruption worsens with each arrow key
press until the text is completely incomprehensible.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce:
- Start Claude Code in plan mode (Shift+Tab twice)
- Wait for Claude to present questions with multiple choice options
- Use arrow keys (up/down) to navigate between options
- Observe text rendering becoming increasingly corrupted with each navigation
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.19
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
What I've Tried:
- Reinstalled Claude Code via
brew install —cask claude-code - Verified TERM is set to xterm-256color
- Resized terminal window (provides temporary fix but issue returns)
- Issue persists across reinstallation
Additional Context:
The issue appears specifically in the interactive question selection UI during plan mode. Standard text output works
fine. Resizing the terminal window temporarily fixes the display but the problem recurs on the next question.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗