anomalyco / anomalyco/opencode
[Bug] question tool in opencode mini: options beyond viewport invisible + IME caret jumps in custom-answer input (macOS)
Open
@kommander is already working on this.
Since Aug 11, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Two UI bugs in the question tool in opencode mini:
-
Options beyond the viewport are invisible but selectable — when a question has more options than fit on screen, options below the viewport are not rendered, yet the arrow keys still move through them blindly.
-
IME caret issues in the "Type your own answer" field —
- macOS default English IME: the caret jumps to the end of the text after every keystroke. Even after manually positioning the caret and typing again, it immediately jumps back to the end.
- macOS default Chinese IME: after committing characters, the caret jumps to the middle of the text and the arrow keys stop working (only Cmd+Arrow keys work). This recurs on every input. When deleting, after removing 1–2 characters the caret is forced to the middle of the text, and further deletion is blocked until the caret has been moved.
Plugins
N/A
OpenCode version
1.18.15
Steps to reproduce
- Run
opencode --miniin Ghostty on macOS. - Ask the model to call the question tool with more options than fit on screen; the options below the viewport are invisible but still selectable.
- Select "Type your own answer".
- Type with the English layout: the caret jumps to the end after each letter.
- Switch to the macOS built-in Chinese IME: after committing at least two Chinese characters the caret jumps to the middle; arrow keys no longer move the caret (Cmd+Arrow only). Repeat typing, then try deleting.
- Expected: caret stays where placed and arrow keys work at all times.
Screenshot and/or share link
Please watch the content of the following link.
https://streamable.com/c9wpp7
Operating System
macOS 26.5.1
Terminal
Ghostty
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.