[BUG] Terminal jitter for ~10 seconds after confirming "yes" in planning mode (Claude CLI 1.0.35, iTerm2, macOS Sequoia)
Environment
- Claude CLI version:
1.0.35 (Claude Code) - Operating System:
macOS Sequoia - Terminal:
iTerm2 3.5.14
Bug Description
When choosing yes during planning mode, the terminal becomes visually unstable for approximately 10 seconds. The cursor jitters or redraws excessively before stabilizing. This occurs consistently after accepting the prompt.
Steps to Reproduce
- Run a Claude Code command that enters planning mode and prompts for confirmation
- Choose
yes and press Enter
3. Observe terminal behavior
Expected Behavior
Terminal should proceed smoothly and immediately after confirmation without any visual disruption.
Actual Behavior
After confirming with yes, the terminal jitters (cursor or screen redraw) for around 10 seconds before returning to normal. There are no visible errors or performance issues logged during this phase.
Additional Context
- Shell:
zsh(or replace with actual shell if different) - No CPU spikes observed during the issue
- Attached video demonstrates the behavior
Simple Jitter (10–20s)
Complex Jitter (Indefinite Duration — Consumes Token — Requires Manual Termination)
Common bug for me as well. Mainly while using MCP servers that use json structure within chat thread (sequentialthinking, etc).
common bug for me as well.
Found 2 possible duplicate issues:
- https://github.com/anthropics/claude-code/issues/2071
- https://github.com/anthropics/claude-code/issues/2390
This issue will be automatically closed as a duplicate in 3 days.
- If your issue is a duplicate, please close it and 👍 the existing issue instead
- To prevent auto-closure, add a comment or 👎 this comment
🤖 Generated with Claude Code
This issue has been automatically closed as a duplicate of #2071.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
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.