/cost command results do not render well in dark mode terminals

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 6 comments · opened Feb 24, 2025 · closed Mar 11, 2025
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Results for the /cost command do not render well in dark mode terminals. This is not an issue with other commands such as /help.

<img width="393" alt="Image" src="https://github.com/user-attachments/assets/c9720ede-d076-4449-bd4f-54e4a2b68a24" />

View original on GitHub ↗

6 Comments

bcherny collaborator · 1 year ago

Mind double checking you have dark mode set correctly?

claude config set --global theme dark or /config then set theme to dark.

abrinsmead · 1 year ago

I confirmed that I am already using the claude dark theme. I am using in iTerm2 with the SynthWave '84 color theme if that helps.

EDIT: This might be an issue with my iTerm2 color config. I don't see the issue in regular iTerm using a darker default profile like "Pro".

ghost · 1 year ago

I am seeing the same thing with the dark theme:

!Image

For reference these are my terminal settings (Gnome terminal on Debian)

!Image

They are slightly more legible if I change my terminal theme to something like solarized dark but it would be preferable to be able to edit claude's dark theme and tweak the colours.

(Superb tool otherwise. Thank you. This is a very minor gripe!)

abrinsmead · 1 year ago

@bcherny This is mostly a client-side issue. However, looking at the minified code, it can be fixed by replacing the only two .grey references with .secondaryText. The .secondaryText color is used more frequently in the app and displays correctly even if the user’s terminal profile is configured with a very dark "bright black."

igorkofman collaborator · 1 year ago

Should be fixed in the latest version!

github-actions[bot] · 1 year ago

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.