The terminal UI display is abnormal #808

Originally created by @srcrs on GitHub (Jul 19, 2025).

Originally assigned to: @adamdotdevin on GitHub.

I'm using a MacBook, using the iterm terminal, and installed oh my zsh, but there are some issues with the display. In version v0.3.24.

brew install sst/tap/opencode

Originally created by @srcrs on GitHub (Jul 19, 2025). Originally assigned to: @adamdotdevin on GitHub. I'm using a MacBook, using the iterm terminal, and installed oh my zsh, but there are some issues with the display. In version v0.3.24. ``` brew install sst/tap/opencode ``` <img width="1917" height="1077" alt="Image" src="https://github.com/user-attachments/assets/96e08aae-a8ae-47bc-ae80-44b86f694d37" />

yindo commented

@thdxr commented on GitHub (Jul 19, 2025):

can you do opencode upgrade 0.3.24 to downgrade and see if it's better?

@thdxr commented on GitHub (Jul 19, 2025): can you do opencode upgrade 0.3.24 to downgrade and see if it's better?

yindo commented

@calebrjc commented on GitHub (Jul 19, 2025):

Unsure if this would be the same issue, but I see similar behavior, specifically after sending a message. The commands and help that I used did not break the UI, but sending the first message did.

The "broken" screenshot is in v0.3.22 and the "normal" one is in v0.3.21, though I first experienced the behavior with v0.3.28, as I just installed this tool on my machine today.

I'm on Linux (Fedora 42), currently using Konsole as my terminal, and running zsh and oh-my-zsh. Installed via curl + bash.

@calebrjc commented on GitHub (Jul 19, 2025): Unsure if this would be the same issue, but I see similar behavior, specifically after sending a message. The commands and help that I used did not break the UI, but sending the first message did. The "broken" screenshot is in v0.3.22 and the "normal" one is in v0.3.21, though I first experienced the behavior with v0.3.28, as I just installed this tool on my machine today. I'm on Linux (Fedora 42), currently using Konsole as my terminal, and running zsh and oh-my-zsh. Installed via curl + bash. <img width="2879" height="1817" alt="Image" src="https://github.com/user-attachments/assets/1a4d19ac-dcfc-4f44-804a-89c25afdf570" /> <img width="2879" height="1822" alt="Image" src="https://github.com/user-attachments/assets/12c60dad-2d92-48dd-9023-12be8176a73c" />

yindo commented

@magnusoverli commented on GitHub (Jul 20, 2025):

I am also seeing this issue. Not sure exactly in what version it started, but there was some change to how diffs were displayed (side-by-side) around 0.3.20? I think that is when it started, and it has become worse lately. Almost to a point where I am unable to use opencode...
I am running CachyOS with the default KDE desktop.

@magnusoverli commented on GitHub (Jul 20, 2025): I am also seeing this issue. Not sure exactly in what version it started, but there was some change to how diffs were displayed (side-by-side) around 0.3.20? I think that is when it started, and it has become worse lately. Almost to a point where I am unable to use opencode... I am running CachyOS with the default KDE desktop. <img width="1348" height="1475" alt="Image" src="https://github.com/user-attachments/assets/c0b50739-cd09-40e8-91ca-bc7af316b49a" />

yindo commented

@magnusoverli commented on GitHub (Jul 20, 2025):

It was introduced in 0.3.22 I think. This feature is mentioned: feat(tui): simpler layout, always stretched.

I do not see this issue before this release.

@magnusoverli commented on GitHub (Jul 20, 2025): It was introduced in 0.3.22 I think. This feature is mentioned: feat(tui): simpler layout, always stretched. I do not see this issue before this release.

yindo commented

@adamdotdevin commented on GitHub (Jul 21, 2025):

haven't been able to reproduce this yet, any more detail or ideas welcomed! i hate visual bugs and i want to kill this one asap 😅

@adamdotdevin commented on GitHub (Jul 21, 2025): haven't been able to reproduce this yet, any more detail or ideas welcomed! i hate visual bugs and i want to kill this one asap 😅

yindo commented

@magnusoverli commented on GitHub (Jul 21, 2025):

Not sure how I can contribute more insight. Could it be shell related? I guess the firs poster is using ZSH? Personally I am using fish on cachysOS. Do they have anything in common that may contribute to the issue? Any non-standard color/formatting/non-posix-stuff?

@magnusoverli commented on GitHub (Jul 21, 2025): Not sure how I can contribute more insight. Could it be shell related? I guess the firs poster is using ZSH? Personally I am using fish on cachysOS. Do they have anything in common that may contribute to the issue? Any non-standard color/formatting/non-posix-stuff?

yindo commented

@magnusoverli commented on GitHub (Jul 21, 2025):

Sort of meta, but here goes... https://opencode.ai/s/NNvk7S6b

@magnusoverli commented on GitHub (Jul 21, 2025): Sort of meta, but here goes... https://opencode.ai/s/NNvk7S6b

yindo commented

@adamdotdevin commented on GitHub (Jul 21, 2025):

interesting. does the layout correct itself if you resize your terminal window/pane?

@adamdotdevin commented on GitHub (Jul 21, 2025): interesting. does the layout correct itself if you resize your terminal window/pane?

yindo commented

@magnusoverli commented on GitHub (Jul 21, 2025):

It does sometimes. It seems to "like" certain widths better than others.

@magnusoverli commented on GitHub (Jul 21, 2025): It does sometimes. It seems to "like" certain widths better than others.

yindo commented

https://github.com/user-attachments/assets/cd04c0bb-0510-41a6-af0a-7932fc4c3ff5

@lazycoder9 commented on GitHub (Jul 22, 2025):

Hey, hope this video helps. I'm on iTerm2 with zsh, MacOS Sonoma 14.5 and you can see how layout behaves in different situations

@lazycoder9 commented on GitHub (Jul 22, 2025): Hey, hope this video helps. I'm on iTerm2 with zsh, MacOS Sonoma 14.5 and you can see how layout behaves in different situations https://github.com/user-attachments/assets/cd04c0bb-0510-41a6-af0a-7932fc4c3ff5

yindo commented

@ilkerhk commented on GitHub (Jul 22, 2025):

I'm having the same issue and unfortunately it is making opencode unusable for me.
Not a workaround but xterm (instead of konsole or yakuake) seems to work fine

EDIT: This issue might not be a bug. In my case (using konsole/yakuake in KDE) the TERM env variable was wrongly set to xterm-256color. Changing it seems to fix the issue:

export TERM=konsole-256color

@ilkerhk commented on GitHub (Jul 22, 2025): I'm having the same issue and unfortunately it is making opencode unusable for me. Not a workaround but xterm (instead of konsole or yakuake) seems to work fine EDIT: This issue might not be a bug. In my case (using konsole/yakuake in KDE) the TERM env variable was wrongly set to xterm-256color. Changing it seems to fix the issue: export TERM=konsole-256color

yindo commented

@adamdotdevin commented on GitHub (Jul 22, 2025):

will take a look at this again tomorrow morning, more clues have come in, hoping to reproduce and track this down

@adamdotdevin commented on GitHub (Jul 22, 2025): will take a look at this again tomorrow morning, more clues have come in, hoping to reproduce and track this down

yindo commented

@adamdotdevin commented on GitHub (Jul 23, 2025):

could you all tell me what your TERM env variable is set to? (echo $TERM)

@adamdotdevin commented on GitHub (Jul 23, 2025): could you all tell me what your TERM env variable is set to? (`echo $TERM`)

yindo commented

@calebrjc commented on GitHub (Jul 23, 2025):

Away from my machine atm, but iirc from when I messed around with this last night, TERM is set to xterm-256color. I tried export TERM=konsole-256color as @ilkerhk suggested (I also use Konsole and KDE) but this seemed to worsen the issue for me.

Will likely have a look again tonight and see if anything else helpful jumps out at me.

@calebrjc commented on GitHub (Jul 23, 2025): Away from my machine atm, but iirc from when I messed around with this last night, `TERM` is set to `xterm-256color`. I tried `export TERM=konsole-256color` as @ilkerhk suggested (I also use Konsole and KDE) but this seemed to worsen the issue for me. Will likely have a look again tonight and see if anything else helpful jumps out at me.

yindo commented

@srcrs commented on GitHub (Jul 23, 2025):

could you all tell me what your TERM env variable is set to? (echo $TERM)你们能否告诉我你们的 TERM 环境变量设置为什么值？（ echo $TERM ）

echo $TERM
xterm-256color

@srcrs commented on GitHub (Jul 23, 2025): > could you all tell me what your TERM env variable is set to? (`echo $TERM`)你们能否告诉我你们的 TERM 环境变量设置为什么值？（ `echo $TERM` ） ``` echo $TERM xterm-256color ```

yindo commented

@magnusoverli commented on GitHub (Jul 23, 2025):

could you all tell me what your TERM env variable is set to? (echo $TERM)

echo $TERM
xterm-256color

@magnusoverli commented on GitHub (Jul 23, 2025): > could you all tell me what your TERM env variable is set to? (`echo $TERM`) echo $TERM xterm-256color

yindo commented

@moltar commented on GitHub (Jul 24, 2025):

Seeing the same issue in iTerm2 on version 0.3.61.

❯ echo $TERM
xterm-256color

@moltar commented on GitHub (Jul 24, 2025): Seeing the same issue in iTerm2 on version 0.3.61. ``` ❯ echo $TERM xterm-256color ```

yindo commented

@magnusoverli commented on GitHub (Jul 25, 2025):

Is it hard to track down what the problem is or create a fix? Among all the fixes coming out daily, I was hoping this would be among them. ☺️

@magnusoverli commented on GitHub (Jul 25, 2025): Is it hard to track down what the problem is or create a fix? Among all the fixes coming out daily, I was hoping this would be among them. ☺️

yindo commented

@calebrjc commented on GitHub (Jul 25, 2025):

If it helps, bisecting through versions, I experience the following.

0.3.16: UI seeems fine.

0.3.17: Diffs start to break for me, but the rest of the UI seems fine.

0.3.22: The whole UI breaks for me. UI behavior seems consistent between 0.3.17 and this point.

Latest: Same as 0.3.22

I know you haven't been able to reproduce, but if there's anything that I can try on my machine let me know and I'll try it out.

EDIT: Doesn't help this issue, but I've been meaning to switch to Ghostty anyways so I just did it now. I'll still test fixes if anyone comes up with anything.

@calebrjc commented on GitHub (Jul 25, 2025): If it helps, bisecting through versions, I experience the following. 0.3.16: UI seeems fine. <img width="2952" height="1668" alt="Image" src="https://github.com/user-attachments/assets/62e6df7a-909e-455e-88a1-8579e8ed9a5d" /> 0.3.17: Diffs start to break for me, but the rest of the UI seems fine. <img width="2952" height="1668" alt="Image" src="https://github.com/user-attachments/assets/a9c7e405-d549-436f-ad3f-a79081b09c39" /> 0.3.22: The whole UI breaks for me. UI behavior seems consistent between 0.3.17 and this point. <img width="2952" height="1668" alt="Image" src="https://github.com/user-attachments/assets/3673c932-86b0-48b5-a0de-0ae7215dd7cd" /> Latest: Same as 0.3.22 <img width="2952" height="1668" alt="Image" src="https://github.com/user-attachments/assets/f1c38348-bc62-46f2-8309-d99c30fb22cb" /> I know you haven't been able to reproduce, but if there's anything that I can try on my machine let me know and I'll try it out. EDIT: Doesn't help this issue, but I've been meaning to switch to Ghostty anyways so I just did it now. I'll still test fixes if anyone comes up with anything.

yindo commented

@KylinWu commented on GitHub (Jul 28, 2025):

same issue here.

echo $TERM
xterm-256color

@KylinWu commented on GitHub (Jul 28, 2025): same issue here. ```bash echo $TERM xterm-256color ```

yindo commented

@magnusoverli commented on GitHub (Jul 29, 2025):

@adamdotdevin Any success in reproducing this?

@magnusoverli commented on GitHub (Jul 29, 2025): @adamdotdevin Any success in reproducing this?

yindo commented

@adamdotdevin commented on GitHub (Jul 31, 2025):

@adamdotdevin Any success in reproducing this?

haven't reproduced, but will look into this again today given some of the new comments

@adamdotdevin commented on GitHub (Jul 31, 2025): > @adamdotdevin Any success in reproducing this? haven't reproduced, but will look into this again today given some of the new comments

yindo commented

@nhumrich commented on GitHub (Jul 31, 2025):

same issue here. xterm-256color.

When I scroll up and back down, it mostly fixes the issue (temporarily) except for the bottom section:

if I let it run on another task, it gets messed up again.
Using Konsole on arch linux

If I use kitty instead, no problem at all.

If I set TERM to konsole-256color, then the layout works great, but then scrolling is broken (I can scroll up, but scroll down only updates the bottom 4 rows).

@nhumrich commented on GitHub (Jul 31, 2025): same issue here. xterm-256color. When I scroll up and back down, it mostly fixes the issue (temporarily) except for the bottom section: <img width="1194" height="190" alt="Image" src="https://github.com/user-attachments/assets/1a063872-310b-4324-8d97-516fb9dab446" /> if I let it run on another task, it gets messed up again. Using Konsole on arch linux If I use kitty instead, no problem at all. If I set TERM to `konsole-256color`, then the layout works great, but then scrolling is broken (I can scroll up, but scroll down only updates the bottom 4 rows).

yindo commented

@adamdotdevin commented on GitHub (Aug 1, 2025):

was able to repro today! should have this fixed soon

@adamdotdevin commented on GitHub (Aug 1, 2025): was able to repro today! should have this fixed soon

yindo commented

@adamdotdevin commented on GitHub (Aug 3, 2025):

well, i was able to reproduce, but i can't go back to a version that doesn't have this issue with my iTerm setup. it seems to be an issue with using the full viewport width in certain terminal environments. i'm going to keep digging, but my advice to those that want to use opencode in the meantime is to use ghostty/wezterm/etc., issue seems to be isolated to iTerm and Konsole/KDE.

@adamdotdevin commented on GitHub (Aug 3, 2025): well, i was able to reproduce, but i can't go back to a version that doesn't have this issue with my iTerm setup. it seems to be an issue with using the full viewport width in certain terminal environments. i'm going to keep digging, but my advice to those that want to use opencode in the meantime is to use ghostty/wezterm/etc., issue seems to be isolated to iTerm and Konsole/KDE.

yindo commented

@ilkerhk commented on GitHub (Aug 12, 2025):

If I set TERM to konsole-256color, then the layout works great, but then scrolling is broken (I can scroll up, but scroll down only updates the bottom 4 rows).

I started to have the same issue with "konsole-256color". You could instead try below workaround (which seems to work under konsole):

tmux new-session "opencode"

@ilkerhk commented on GitHub (Aug 12, 2025): > If I set TERM to `konsole-256color`, then the layout works great, but then scrolling is broken (I can scroll up, but scroll down only updates the bottom 4 rows). I started to have the same issue with "konsole-256color". You could instead try below workaround (which seems to work under konsole): tmux new-session "opencode"

yindo commented

@arash-qc commented on GitHub (Aug 30, 2025):

similiar in Cursor Terminal:

@arash-qc commented on GitHub (Aug 30, 2025): similiar in Cursor Terminal: <img width="1083" height="928" alt="Image" src="https://github.com/user-attachments/assets/b968cc1e-0fe7-4c38-a646-2b2b9d312096" />

yindo commented

@fish895623 commented on GitHub (Sep 11, 2025):

This issues is also reproduced on alacritty and kitty.
I use "Terminess Nerd Font Mono".

@fish895623 commented on GitHub (Sep 11, 2025): This issues is also reproduced on alacritty and kitty. I use "Terminess Nerd Font Mono". <img width="770" height="558" alt="Image" src="https://github.com/user-attachments/assets/d8f8b91c-ea87-42a9-b546-e4f0aad903fc" /> <img width="930" height="758" alt="Image" src="https://github.com/user-attachments/assets/d4ba4be6-034f-4ff5-8f6e-26b6b4b80a5b" />

yindo commented

@JGKle commented on GitHub (Sep 17, 2025):

found my way here - first attempt/look at opencode as a possible alternative to ClaudeCode (my daily driver), but the UI is garbled/unusable in Konsole (my terminal of choice). Will come back to try again if/when this gets fixed.

Edit: Also tried konsole-256color, but per above, scrolling is then broken.

@JGKle commented on GitHub (Sep 17, 2025): found my way here - first attempt/look at opencode as a possible alternative to ClaudeCode (my daily driver), but the UI is garbled/unusable in Konsole (my terminal of choice). Will come back to try again if/when this gets fixed. Edit: Also tried konsole-256color, but per above, scrolling is then broken.

yindo commented

@fish895623 commented on GitHub (Sep 27, 2025):

I think this is an issue on ansi package. you can just set LANG environemt variable as C or en_US now works fine.

@fish895623 commented on GitHub (Sep 27, 2025): I think this is an issue on ansi package. you can just set LANG environemt variable as C or en_US now works fine.

yindo commented

@pasqui23 commented on GitHub (Sep 28, 2025):

No it doesn't fix it with yakuake

@pasqui23 commented on GitHub (Sep 28, 2025): No it doesn't fix it with yakuake

yindo commented

@winetree94 commented on GitHub (Oct 1, 2025):

I am also experiencing the same issue.
It works correctly when I unset the LANG=ko_KR.UTF-8 environment variable.
iTerm was automatically injecting this environment variable.
You can disable it under Profile - Terminal - Environment.

@winetree94 commented on GitHub (Oct 1, 2025): I am also experiencing the same issue. It works correctly when I unset the `LANG=ko_KR.UTF-8` environment variable. iTerm was automatically injecting this environment variable. You can disable it under `Profile - Terminal - Environment`.

yindo commented

@roadev commented on GitHub (Oct 1, 2025):

I'm having the same issue on EndeavourOS + KDE using Konsole
opencode version: 0.13.7

@roadev commented on GitHub (Oct 1, 2025): I'm having the same issue on EndeavourOS + KDE using Konsole opencode version: 0.13.7 <img width="1459" height="835" alt="Image" src="https://github.com/user-attachments/assets/06c0b0e7-99a3-49da-96e5-9298563f33c0" />

yindo commented

@rekram1-node commented on GitHub (Oct 1, 2025):

@roadev if you do: bun x opencode-ai@opentui does this fix your issue?

This is a beta ^^ still a wip but it may fix some of these problems

@rekram1-node commented on GitHub (Oct 1, 2025): @roadev if you do: `bun x opencode-ai@opentui` does this fix your issue? This is a beta ^^ still a wip but it may fix some of these problems

yindo commented

@nikooo777 commented on GitHub (Oct 8, 2025):

@rekram1-node it fixes it for me!

on Kubuntu with Konsole

@nikooo777 commented on GitHub (Oct 8, 2025): @rekram1-node it fixes it for me! on Kubuntu with Konsole

yindo commented

@rekram1-node commented on GitHub (Oct 8, 2025):

@nikooo777 happy to hear it, hope the finishing touches can be wrapped up soon so we can launch it

@rekram1-node commented on GitHub (Oct 8, 2025): @nikooo777 happy to hear it, hope the finishing touches can be wrapped up soon so we can launch it

yindo commented

@jfrmorales commented on GitHub (Oct 10, 2025):

@rekram1-node works for me too!

CachyOS + Konsole

@jfrmorales commented on GitHub (Oct 10, 2025): @rekram1-node works for me too! CachyOS + Konsole

yindo commented

@roadev commented on GitHub (Oct 11, 2025):

@roadev if you do: bun x opencode-ai@opentui does this fix your issue?

This is a beta ^^ still a wip but it may fix some of these problems

that one worked for me! thanks!

@roadev commented on GitHub (Oct 11, 2025): > [@roadev](https://github.com/roadev) if you do: `bun x opencode-ai@opentui` does this fix your issue? > > This is a beta ^^ still a wip but it may fix some of these problems that one worked for me! thanks!

yindo commented

@lucasff commented on GitHub (Oct 17, 2025):

I also have the same issue, with MacOS and iTerm2, using Zsh and Powerlevel10k

@lucasff commented on GitHub (Oct 17, 2025): I also have the same issue, with MacOS and iTerm2, using Zsh and Powerlevel10k

yindo commented

@vasyan commented on GitHub (Oct 20, 2025):

Have similar issue with iTerm2. I toggling between zoom+ zoom- hotkeys till it fix the visual artifacts, but it is a pain in neck.
However, terminal in Cursor do the trick.

@vasyan commented on GitHub (Oct 20, 2025): Have similar issue with iTerm2. I toggling between zoom+ zoom- hotkeys till it fix the visual artifacts, but it is a pain in neck. However, terminal in Cursor do the trick.

yindo commented

@ecker00 commented on GitHub (Oct 23, 2025):

I still have issues with this, and adding export TERM=konsole-256color to my ~/.zshrc / ~/.bashrc solved it for me.

@ecker00 commented on GitHub (Oct 23, 2025): I still have issues with this, and adding `export TERM=konsole-256color` to my `~/.zshrc` / `~/.bashrc` solved it for me.

yindo commented

@wThomas84 commented on GitHub (Oct 24, 2025):

For me the workaround is to run opencode within a tmux session. That also has the advantage, that I can switch between different instances of different projects by using tumx' window feature.

Running on KDE Konsole 23.08.5, using zsh.

@wThomas84 commented on GitHub (Oct 24, 2025): For me the workaround is to run `opencode` within a tmux session. That also has the advantage, that I can switch between different instances of different projects by using tumx' window feature. Running on KDE Konsole 23.08.5, using zsh.

yindo commented

https://github.com/user-attachments/assets/1132e662-03c4-4fb7-a66c-e0e8e1e99be4

@ktalanov commented on GitHub (Oct 29, 2025):

I'm sure you're working on this, but to point out this issue very much still exists. I would have given up on the project if I didn't manage to ask it to figure out this issue for me. It didn't, but it did point me to this bug submission. FWIW, Fedora 43 coems with $TERM set to xterm-256color by default. Interestingly enough, when I installed an actual instance of xterm it did not exhibit the problematic behaviour. (For me), it's fixed by setting TERM to konsole-256color. The video speaks for itself (and my sense of humour, apparently.)

me@fedora:~$ opencode --version
0.15.23

me@fedora:~$ bash --version
GNU bash, version 5.3.0(1)-release (x86_64-redhat-linux-gnu)

Edit: just saw the update, didn't check what it was for but the same behaviour in 0.15.26.

and

me@fedora:~$ konsole --version
konsole 25.08.2

Here's the unnecessarily-long video with hopefully some info you didn't have before, though I somehow doubt it will shine much new light:

@ktalanov commented on GitHub (Oct 29, 2025): I'm sure you're working on this, but to point out this issue very much still exists. I would have given up on the project if I didn't manage to ask it to figure out this issue for me. It didn't, but it did point me to this bug submission. FWIW, Fedora 43 coems with $TERM set to xterm-256color by default. Interestingly enough, when I installed an actual instance of xterm it did not exhibit the problematic behaviour. (For me), it's fixed by setting TERM to konsole-256color. The video speaks for itself (and my sense of humour, apparently.) ``` me@fedora:~$ opencode --version 0.15.23 ``` ``` me@fedora:~$ bash --version GNU bash, version 5.3.0(1)-release (x86_64-redhat-linux-gnu) ``` **Edit: just saw the update, didn't check what it was for but the same behaviour in 0.15.26.** and ``` me@fedora:~$ konsole --version konsole 25.08.2 ``` Here's the unnecessarily-long video with hopefully some info you didn't have before, though I somehow doubt it will shine much new light: https://github.com/user-attachments/assets/1132e662-03c4-4fb7-a66c-e0e8e1e99be4

yindo commented

@rekram1-node commented on GitHub (Oct 29, 2025):

Thanks @ktalanov

@rekram1-node commented on GitHub (Oct 29, 2025): Thanks @ktalanov

yindo commented

@bitzerk commented on GitHub (Oct 30, 2025):

EDIT: The issue no longer persists for me in v1.0.0 🙌

I also have this visual glitch. I use yakuake with zsh.

When I edit my yakuake profile, and go to General > Environment > Edit, I see the following environment vars are set:

Original ENV Vars Set:

TERM=xterm-256color
COLORTERM=truecolor

Result:

If I comment out the second line, my colors don't match the theme I select in opencode, BUT the glitch disappears 🤔:

Commented-out COLORTERM env var:

TERM=xterm-256color
#COLORTERM=truecolor

Result:

I don't know the solution here, just thought it could help get everyone one-step closer.

EDIT:

I've noticed that some themes are still broken, even with this change - but most aren't. I'm using evergreen theme in my example that is working.

@bitzerk commented on GitHub (Oct 30, 2025): *** EDIT: The issue no longer persists for me in v1.0.0 🙌 *** I also have this visual glitch. I use yakuake with zsh. When I edit my yakuake profile, and go to `General > Environment > Edit`, I see the following environment vars are set: ## Original ENV Vars Set: ```bash TERM=xterm-256color COLORTERM=truecolor ``` ## Result: <img width="1821" height="898" alt="Image" src="https://github.com/user-attachments/assets/9502d17c-48b3-4d25-b38a-b224ba9a4e91" /> *** If I comment out the **second** line, my colors don't match the theme I select in opencode, BUT the glitch disappears 🤔: ## Commented-out COLORTERM env var: ```bash TERM=xterm-256color #COLORTERM=truecolor ``` ## Result: <img width="1821" height="898" alt="Image" src="https://github.com/user-attachments/assets/d6d4dbf3-9bd3-471f-b4c8-14b1237f64d7" /> I don't know the solution here, just thought it could help get everyone one-step closer. *** EDIT: I've noticed that some themes are still broken, even with this change - but most aren't. I'm using `evergreen` theme in my example that is working.

yindo commented

@strk commented on GitHub (Dec 28, 2025):

This is still a problem with 1.0.62 - I confirm that under tmux (as suggested by @wThomas84) the terminal becomes readable (luck?)

@strk commented on GitHub (Dec 28, 2025): This is still a problem with 1.0.62 - I confirm that under tmux (as suggested by @wThomas84) the terminal becomes readable (luck?)

yindo commented

@rozgo commented on GitHub (Jan 3, 2026):

This is vanilla osx terminal. Its still unusable.

@rozgo commented on GitHub (Jan 3, 2026): <img width="1728" height="1081" alt="Image" src="https://github.com/user-attachments/assets/9341ad54-ebf4-43dc-99ce-2fdd4f06b972" /> <img width="1728" height="1082" alt="Image" src="https://github.com/user-attachments/assets/0dcfd4f5-c26c-4421-8cdf-480d0c253bed" /> This is vanilla osx terminal. Its still unusable.

yindo commented

@IanKeefer commented on GitHub (Jan 5, 2026):

This is vanilla osx terminal. Its still unusable.

Getting the exact same result as these screenshots. Attempted every individual theme too an all are scuffed.

15.6.1 in osx terminal

@IanKeefer commented on GitHub (Jan 5, 2026): > <img alt="Image" width="1728" height="1081" src="https://private-user-images.githubusercontent.com/92162/531662580-9341ad54-ebf4-43dc-99ce-2fdd4f06b972.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc2NjQ0NDYsIm5iZiI6MTc2NzY2NDE0NiwicGF0aCI6Ii85MjE2Mi81MzE2NjI1ODAtOTM0MWFkNTQtZWJmNC00M2RjLTk5Y2UtMmZkZDRmMDZiOTcyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTA2VDAxNDkwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZmNTg4YzNlZDFjY2NkMzZhN2JlYTNiOGRiYmQ5ZGJlMTMwMTEyNzc3NTBhMzI1MGQ0OTMzY2YzNmMyNmZiMjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.e30EQoAsCxPaO5cdhKHckLh_eho282m82QDnBhPwLV4"> <img alt="Image" width="1728" height="1082" src="https://private-user-images.githubusercontent.com/92162/531662738-0dcfd4f5-c26c-4421-8cdf-480d0c253bed.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc2NjQ0NDYsIm5iZiI6MTc2NzY2NDE0NiwicGF0aCI6Ii85MjE2Mi81MzE2NjI3MzgtMGRjZmQ0ZjUtYzI2Yy00NDIxLThjZGYtNDgwZDBjMjUzYmVkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTA2VDAxNDkwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY2ZmYyM2EyYzU3MzJjMmExOGZlM2ViMmQ4NDNkMTkxOTcxZjgyODYxOWMwMDMwMmI4ZjEyZjRmODA0YWUxNzgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.oOkQ_IzJOZo70V1s-z39J-3mDjvHcyijpDY6l7335CU"> > This is vanilla osx terminal. Its still unusable. Getting the exact same result as these screenshots. Attempted every individual theme too an all are scuffed. `15.6.1` in osx terminal

yindo commented

@echoborealis commented on GitHub (Jan 28, 2026):

This is vanilla osx terminal. Its still unusable.

+1 on this, same behaviour on default macOS 15.x terminal, 26.x works fine.
Disabling ANSI colors helps with text readability, but it removes, well, colours.
I think that there's some issue with colouring and opencode just defaults to ANSI if something is not working properly

Terminal version with issues is 2.14 (455.1)

@echoborealis commented on GitHub (Jan 28, 2026): > <img alt="Image" width="1728" height="1081" src="https://private-user-images.githubusercontent.com/92162/531662580-9341ad54-ebf4-43dc-99ce-2fdd4f06b972.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk2Mjg1MzksIm5iZiI6MTc2OTYyODIzOSwicGF0aCI6Ii85MjE2Mi81MzE2NjI1ODAtOTM0MWFkNTQtZWJmNC00M2RjLTk5Y2UtMmZkZDRmMDZiOTcyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTI4VDE5MjM1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAxYWU2YmQ1YWNiZDI1NGM5NjJhM2UzNDUwZWVmMzJkNzRhODgzOWFiOTFmMDM2YWY5ZjNjNTRkNzk1ZDE2MDImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ONMoul03wBm3-Fp_hqyws2LNxP5gd1fk5uQeonvcNX0"> <img alt="Image" width="1728" height="1082" src="https://private-user-images.githubusercontent.com/92162/531662738-0dcfd4f5-c26c-4421-8cdf-480d0c253bed.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk2Mjg1MzksIm5iZiI6MTc2OTYyODIzOSwicGF0aCI6Ii85MjE2Mi81MzE2NjI3MzgtMGRjZmQ0ZjUtYzI2Yy00NDIxLThjZGYtNDgwZDBjMjUzYmVkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTI4VDE5MjM1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBkOWM0YWE5OGQwNzJjM2Q1Mzc2ZTZlNmE0ZTQ5MjY0N2ZjZGQyZWE0NDY4ODJiYjk1NTllNmQzNDAwOTQyMGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ITmx2Um8sTzMy3ZepXXqeBZ9viNuH1JQxp4a7wJ_LwI"> > This is vanilla osx terminal. Its still unusable. +1 on this, same behaviour on default macOS 15.x terminal, 26.x works fine. Disabling ANSI colors helps with text readability, but it removes, well, colours. I think that there's some issue with colouring and opencode just defaults to ANSI if something is not working properly Terminal version with issues is 2.14 (455.1)

yindo commented

@haliliceylan commented on GitHub (Feb 9, 2026):

I have same problem, with osx terminal

@haliliceylan commented on GitHub (Feb 9, 2026): I have same problem, with osx terminal

yindo commented