[BUG] Terminal rendering fails completely on my system
Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened Mar 9, 2025 · closed Apr 4, 2025
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 0.2.32 (Claude Code)
- Operating System: macOS 15.3.1
- Terminal: iTerm2
$ node --version
v23.7.0Bug Description
Running claude blanks the terminal and nothing appears. Input is connected, and if I mash the return button then text does appear but it's always behind where it should be. It feels like a buffering issue: I'm constantly seeing what should have been rendered in the previous step.
Steps to Reproduce
- Run claude. Terminal is blank.
- Wonder what's going on, press enter.
- Welcome screen appears with the logo, but nothing else.
- Press enter again.
- Browser opens
- I click authorize in the browser and go back to the terminal, now I see "Browser didn't open? Use the url below to sign in: ... <url>"
etc.
Expected Behavior
Terminal should update correctly.
Actual Behavior
I always seem to be one user interaction behind in what I see.
Additional Context
I've not seen problems with any other terminal using app and my configuration is pretty standard (using oh my zsh though). It feels like a bug in the terminal rendering library, but I don't know what could trigger it.
7 Comments
+1 Also having this issue, downgrading to claude-code@0.2.32 fixes it.
+1 It only seems to work sometimes. I've tried disabling my zsh themes, to no avail.
I was able to reproduce my issue - it relies on
CIenvironment variable. That's why it only worked sometimes.unset CIand it works.I opened an issue with steps to reproduce on https://github.com/anthropics/claude-code/issues/677
I see this issue but I don't have $CI set in my environment. However, this might be enough to track down which library is causing the problem? Perhaps I have a different env var that causes the same issue?
The latest version appears to fix this.
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.