You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is how it looks in Alacritty 0.16.1 (1) on the same machine with the same configuration. I would strongly prefer to use the Terminal.app, however.
MacOS Terminal.app <= 2.14 is currently not working as it does not support true color and opentui does not have a fallback yet. It will come at some point, but for now there is no other way than to either upgrade to MacOS Sequoia (which is why it works for @rekram1-node) or use a terminal that supports true color.
This wasn't working properly for me even under macOS 26. I was able to fix it by telling Terminal to declare its terminal type as "xterm-256color" in Profiles -> Advanced -> TermInfo. I'd previously had it set to "xterm". (This also has the side-effect of causing terminal to set COLORTERM=truecolor in the environment, which actually makes it take the truecolor rendering path.)
Activity
agladysh commentedon Nov 18, 2025
Here is how it looks in Alacritty 0.16.1 (1) on the same machine with the same configuration. I would strongly prefer to use the Terminal.app, however.
ls-rajan-rauniyar commentedon Nov 19, 2025
@agladysh I had the same issue and switched from using Terminal to iterm2, and everything looks so great. I'd highly suggest that you do so.
rekram1-node commentedon Nov 19, 2025
What terminal version did this happen with and what theme was it @agladysh I can't replicate using macos terminal + opencode theme
kommander commentedon Nov 20, 2025
MacOS Terminal.app <= 2.14 is currently not working as it does not support true color and opentui does not have a fallback yet. It will come at some point, but for now there is no other way than to either upgrade to MacOS Sequoia (which is why it works for @rekram1-node) or use a terminal that supports true color.
ahmedasmar commentedon Jan 11, 2026
I'm on Sequoia and using Terminal 2.14 and have the same issue! how to fix it? I would rather stay with stock terminal for now.
kommander commentedon Jan 11, 2026
The only option you have for now then is to upgrade MacOS to Tahoe.
ahmedasmar commentedon Jan 11, 2026
kommander commentedon Jan 12, 2026
Not a guess, I know that the built-in terminal in Tahoe got improvements like true color support.
SeverinAlexB commentedon Jan 12, 2026
I just experienced this issue and upgrading to MacOS Tahoe worked
smilemonk commentedon Jan 25, 2026
me too … Mac+zsh+opencode=dark
ahmedasmar commentedon Jan 25, 2026
github-actions commentedon Mar 27, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
monroewilliams commentedon Jul 8, 2026
This wasn't working properly for me even under macOS 26. I was able to fix it by telling Terminal to declare its terminal type as "xterm-256color" in Profiles -> Advanced -> TermInfo. I'd previously had it set to "xterm". (This also has the side-effect of causing terminal to set
COLORTERM=truecolorin the environment, which actually makes it take the truecolor rendering path.)