Sebastian Herrlinger
Sebastian Herrlinger
The only option you have for now then is to upgrade MacOS to Tahoe.
Not a guess, I know that the built-in terminal in Tahoe got improvements like true color support.
Interesting workaround. @Hona you think that makes sense? Could bring that in opentui.
Will be fixed in the next release.
Can you try running the debug version like `OC_NO_KITTY_KEYBOARD=1 bunx opencode-ai@snapshot-kmdr-debug`? Or try it in a terminal that does not support kitty keyboard, like Alacritty. I need to know if...
Could you try `bunx opencode-ai@snapshot-kmdr-debug` again if that input issue still happens in the terminal it happened before?
Weird. Did you try without any plugins, like without OMO?
I want to get to the bottom of this. Can you get the opentui examples app from [https://github.com/anomalyco/opentui/releases/download/v0.1.72/opentui-examples-v0.1.72-windows-x64.zip](https://github.com/anomalyco/opentui/releases/download/v0.1.72/opentui-examples-v0.1.72-windows-x64.zip) and run the "Keypress Debug Tool", type a few characters that cause...
Sorry, so many windows issues, I mixed that up:[ https://github.com/anomalyco/opentui/releases/tag/v0.1.72](https://github.com/anomalyco/opentui/releases/tag/v0.1.72) - there are releases of the example app for all platforms.
Is that happening when exiting with ctrl+c from the error boundary screen or just always? This only has been an issue on windows so far.