Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix IME input issue on Windows: first character is not captured correctly when typing without focus [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18930•Fetched 2026-04-22 07:50:43
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
yuuuuuuuu25yuuuuuuuu25
Participants
yuuuuuuuu25yuuuuuuuu25
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.415

What subscription do you have?

Business

What platform is your computer?

Microsoft Windows 11 x64

What issue are you seeing?

The Codex App supports typing even when the input box is not focused (similar to ChatGPT). However, this behavior does not work correctly with Japanese IME input.

When typing Japanese text using IME (e.g. typing "さくら"), the expected input sequence is: s → a → k → u → r → a

However, when starting to type without focusing the input box first, the first character is not correctly handled by the IME.

For example: Typing "sakura" results in: sあくら

The first character ("s") is inserted as a raw character instead of being processed by the IME.

Steps to reproduce:

  1. Launch Codex App on Windows
  2. Make sure the text input field is NOT focused
  3. Start typing Japanese using IME (e.g. "sakura")
  4. Observe the resulting text

Expected behavior:

The input should be handled by the IME from the first keystroke, resulting in proper Japanese text (e.g. "さくら")

Actual behavior:

The first character is inserted as a raw Latin character, and the rest is processed by IME

Additional notes:

This seems to be related to how the app handles focus and key events before IME composition starts.

IME:

Microsoft IME (default Windows Japanese IME)

Reproducibility:

100%

https://github.com/user-attachments/assets/ad7b0e08-d9f8-4a4e-bd0c-987c1ef27d5c

What steps can reproduce the bug?

  1. Launch Codex App on Windows
  2. Make sure the text input field is NOT focused
  3. Start typing Japanese using IME (e.g. type "sakura")
  4. Observe the resulting text

What is the expected behavior?

The input should be handled by the IME from the first keystroke, resulting in proper Japanese text (e.g. "さくら").

Typing "sakura" should correctly produce "さくら" even when starting to type without focusing the input field.

Additional information

This issue also occurs in ChatGPT with the same behavior when typing without focusing the input field.

When typing Japanese using IME without focusing the input field first, the first character is inserted as a raw Latin character.

For example: Typing "sakura" results in: sあくら

This suggests that the first key event is being processed before IME composition starts.

IME: Microsoft IME (default Windows Japanese IME) Reproducibility: 100%

extent analysis

TL;DR

The issue can be fixed by ensuring the input field is focused before starting to type Japanese text using IME, or by modifying the Codex App to handle key events and IME composition correctly when the input field is not focused.

Guidance

  • The problem seems to be related to how the Codex App handles focus and key events before IME composition starts, suggesting that the app may need to be modified to handle these events correctly.
  • To verify the issue, try focusing the input field before starting to type Japanese text using IME and check if the input is handled correctly.
  • To mitigate the issue, users can manually focus the input field before starting to type Japanese text using IME.
  • The fact that this issue also occurs in ChatGPT with the same behavior suggests that it may be a more general problem with how these apps handle IME input.

Example

No code snippet is provided as the issue does not include enough technical details to suggest a specific code change.

Notes

The issue seems to be specific to the Microsoft IME on Windows, and it is not clear if it affects other IMEs or platforms.

Recommendation

Apply workaround: Focus the input field before starting to type Japanese text using IME, as this is a reliable way to ensure that the input is handled correctly, even if it does not fix the underlying issue with the Codex App.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#parallel task#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING