tui rendering artifacting

the tui does not seem to be re-rendered of force-updated

also if u where to try and copy console log from when i build a project and paste (ctrl+v) a long snippet of error code/syntax the opencode will begin working before i even hit enter when i still am pasting error log/msg.

@xXT10Xx this seems terminal specific, which terminal are u using?

@rekram1-node

@xXT10Xx this seems terminal specific, which terminal are u using?

@rekram1-node
im on windows and have tried console, windows terminal and terminal inside of vscode.

@adamdotdevin

@adamdotdevin have u by chance fixed or looked into this?

I am on Windows as well, tried different terminals - the rendering seems broken, some sections/areas remain displayed when scrolling. It seems that it gets broken after the first prompt, while the response is streamed - some rows scroll the screen down as expected, some overwrite the last one.

Sorry to hear that, our windows support is lackluster hoping it can continue to improve in near future

i am getting the same issue too.

I just had this happen in Alacritty Windows too:

It seems to be something with the ANSI color sequences or line endings.

set NO_COLOR=1 fixes the artifacting and also the wonky mouse scrollback issues, but the tradeoff is that we lose color

Is there a possibility to see if this is BubbleTea 2 beta related?

we are about to ship a rewrite of the tui that wont be using bubbletea should resolve all this

Fantastic news.

we are about to ship a rewrite of the tui that wont be using bubbletea should resolve all this

Is this in a branch or a preview release? I'll pull it and try/verify on windows (and wsl).

@zendril

@zendril yes you can try it by running the following, it should always track to latest version of opentui branch:

bun x opencode-ai@opentui

FYI

I'm on windows, this seems like it is looking for linux/posix pathing.
Tried from inside git-bash but no difference.

error: interpreter executable "/bin/sh" not found in %PATH%

Bun failed to remap this bin to its proper location within node_modules.
This is an indication of a corrupted node_modules directory.

Please run 'bun install --force' in the project root and try
it again. If this message persists, please open an issue:
https://github.com/oven-sh/bun/issues

good to know ty

Took a bit of a look.

When I bun dev the opentui branch I get a message to check the log which says ERROR 2025-10-26T05:24:50 +241ms service=default name=Error message=getContextId cannot be used under non-hydrating context stack=Error: getContextId cannot be used under non-hydrating context

Adding --conditions=browser seems to get past that and allow the branch to run fine.

Made the following PR but take this with a grain of salt because this is the first time I've opened this codebase up.

#3453

As a follow-up, I built the windows exe from that PR (this build doesn't run ON windows, but ran the build on wsl to produce the opencode-windows-x64 binary) and was able to run that just fine.

Also ran the linux version and that worked ok too, so I don't think I broke anything with the PR change.

awesome thank you

Thanks for merging. Pulled the opentui branch with that merged in and bun dev seems to work fine.

Still getting error: interpreter executable "/bin/sh" not found in %PATH% when running bun x opencode-ai@opentui

I made another PR for that so that the package.json invokes a run.js that figures out whether it should be ./bin/opencode or ./bin/opencode.cmd

#3466

I know I hijacked this thread a bit.. but the combination of these two fixes makes the opentui branch usable on windows and should now support bun x opencode@opentui

no prob this is helpful, thank u

Navigation Menu

Repository navigation

tui rendering artifacting #1864

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

tui rendering artifacting #1864

Description

Activity

rekram1-node commented on Aug 12, 2025

AviseOffical commented on Aug 12, 2025

AviseOffical commented on Aug 15, 2025

gius commented on Aug 21, 2025

rekram1-node commented on Aug 21, 2025

mairs8 commented on Aug 25, 2025

JosXa commented on Oct 21, 2025

zendril commented on Oct 25, 2025

rekram1-node commented on Oct 25, 2025

zendril commented on Oct 25, 2025

zendril commented on Oct 26, 2025

rekram1-node commented on Oct 26, 2025

zendril commented on Oct 26, 2025

rekram1-node commented on Oct 26, 2025

zendril commented on Oct 26, 2025

zendril commented on Oct 26, 2025

rekram1-node commented on Oct 26, 2025

zendril commented on Oct 26, 2025

rekram1-node commented on Oct 27, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions