anomalyco / anomalyco/opencode
[Bug] Desktop question UI: Japanese IME confirm moves focus from custom input to option card
@Brendonovich is already working on this.
Since Sep 15, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
In the OpenCode Desktop question UI (options + free custom input at the bottom, question tool / "Type your own answer"), confirming Japanese conversion moves focus out of the text input.
After pressing Enter to confirm (kakutei) with Google Japanese Input, focus leaves the custom input and moves to the option card. Continuous Japanese input is interrupted. Text itself is preserved, but the caret is gone and typing cannot continue without re-clicking. This does not happen in the normal chat prompt input.
https://github.com/user-attachments/assets/0d1e72b7-b3e6-4035-a2a9-b950585efdd2
Observed in video:
- Inner textbox initially focused (blue outline + caret) with Google IME candidate window
- Typed
これはテストですnormally - After Enter to confirm conversion, focus moves to outer option card (outer blue outline, inner outline gone, no caret)
- Text is preserved (
これはテストですまだ打ちたいのに外れてしまいます) but typing cannot continue without re-clicking
Related but not identical: #35746 (Enter submits during IME composition in review panel), #38674 (Safari composition aborted), #6950 (fixed WebUI IME submit), #30393 (TUI custom answer cannot submit).
Plugins
blender MCP only (local, enabled)
OpenCode version
Desktop 1.18.30 / CLI 1.17.11
Steps to reproduce
- In OpenCode Desktop, trigger a question UI with multiple options + custom free input at the bottom
- Focus the bottom custom input ("Type your own answer" / "自分の回答を入力")
- Enable Google Japanese Input and type Japanese (romaji -> hiragana -> kanji conversion)
- Press Enter to confirm the conversion candidate
- Focus leaves the input and moves to the option card; continued typing does not stay in the input
Operating System
macOS 26.6.2 (Build 25G83), Apple Silicon (arm64), MacBook Pro
Terminal
N/A (Desktop App BETA)
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.