[BUG] IME candidate window not displayed in Claude Code interactive TUI

Resolved 💬 4 comments Opened Mar 5, 2026 by austin0204 Closed Apr 4, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When using an IME (Input Method Editor) inside the Claude Code interactive TUI, the candidate selection window does not appear. The IME works correctly in the same terminal outside of
Claude Code (i.e., in a normal shell prompt), but once inside Claude Code, the TUI seems to intercept keyboard events, preventing the IME from displaying its candidate/selection window.
This makes it impossible to type Chinese (or other CJK) characters directly in Claude Code.

What Should Happen?

The IME candidate window should appear normally inside the Claude Code TUI, allowing the user to compose and select characters, just as it does in the normal shell prompt within the same
terminal. Users should be able to type CJK characters directly without needing to rely on copy-paste workarounds.

Error Messages/Logs

Steps to Reproduce

  1. Open GNOME Terminal
  2. Confirm the IME (chewing / 新酷音, a Chinese input method) works normally in the shell — candidate window appears as expected
  3. Launch Claude Code (claude)
  4. Switch to the IME and attempt to type Chinese characters
  5. The IME candidate/selection window does not appear — unable to select characters

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.69

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Environment

  • OS: Ubuntu 24.04.4 LTS
  • Desktop: GNOME (X11)
  • Terminal: GNOME Terminal 3.52.0 (VTE 0.76.0)
  • IME Framework: IBus 1.5.29-rc2
  • Input Method: chewing (新酷音)
  • Claude Code Version: 2.1.69

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗