CommandCodeAI / CommandCodeAI/command-code
Improve Korean (Hangul) input in the terminal — composing text is not visible
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Request
Korean (Hangul) input in the interactive prompt is hard to use: the IME composing (pre-edit) text is not shown in the input box, so you cannot see what you are typing until each syllable/word is committed. The same terminal works fine with Codex and Claude Code.
Please improve Hangul input handling in the terminal TUI so composing text is visible while typing.
Environment
- Command Code 1.56.0 (latest)
- macOS arm64 (Darwin 25.6.0)
- iTerm2 3.6.11,
TERM=xterm-256color,LANG=ko_KR.UTF-8, Korean 2-set IME
Steps to reproduce
- Run
cmdin iTerm2 with the Korean IME active - Focus the prompt input and type
한글 - No pre-edit is displayed while composing - only the committed text appears
Notes
dist/cli.mjshas no composition handling at all (isComposing,compositionupdate,preedit,markedText: zero occurrences), and the kitty keyboard protocol is pushed at startup (resolveKittyKeyboardwithdisambiguateEscapeCodes). There is no setting, config key, or env var to opt out.ctrl+g(external editor) is the only usable workaround right now.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the issue in the interactive prompt with the Korean 2-set IME, then inspect dist/cli.mjs and the startup path around resolveKittyKeyboard and disambiguateEscapeCodes. Trace how terminal input reaches the TUI and identify where composition events are handled. Done means Hangul pre-edit text is visible while typing and committed text still behaves correctly.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100