Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Dead keys break in VS Code Remote SSH terminal on Linux

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…

Fix Action

Fix / Workaround

The current workaround is CODEX_TUI_DISABLE_KEYBOARD_ENHANCEMENT=1 codex. The suspected follow-up is to skip crossterm keyboard enhancement flags for Linux VS Code terminals, not just the original WSL + VS Code path fixed by #18741.

RAW_BUFFERClick to expand / collapse

What issue are you seeing?

Follow-up to #13638: dead-key accent composition can still fail inside Codex when VS Code is attached to a native Linux host through Remote SSH. The new report in https://github.com/openai/codex/issues/13638#issuecomment-4458442938 reproduces this on an aarch64 Raspberry Pi + VS Code Remote SSH session, where the escape sequence ^[[13;1:3u leaks into the terminal and dead keys such as circumflex and grave do not produce accented characters.

What steps can reproduce the bug?

  1. Connect to a native Linux host through VS Code Remote SSH.
  2. Open the integrated terminal on that remote host.
  3. Run codex.
  4. Type a dead-key combination such as circumflex or grave followed by a vowel.

What is the expected behavior?

Dead-key composition should match the same VS Code terminal outside Codex.

Additional information

The current workaround is CODEX_TUI_DISABLE_KEYBOARD_ENHANCEMENT=1 codex. The suspected follow-up is to skip crossterm keyboard enhancement flags for Linux VS Code terminals, not just the original WSL + VS Code path fixed by #18741.

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…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Dead keys break in VS Code Remote SSH terminal on Linux