Cursor movement (Left arrow) causes characters to visually disappear in JetBrains JediTerm since v0.129.0

Open
#37,782 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Start by reproducing the cursor-movement regression in JetBrains Rider's JediTerm with Codex CLI 0.129.0 and compare it with 0.128.0. Trace the terminal rendering change introduced in 0.129.0, then verify that moving left preserves visible characters and the full input buffer; add or run a regression test if the relevant test entry point is found.

Written by the indexing model from the issue text.

Description

bug CLI TUI windows-os
What version of Codex CLI is running?

0.129.0

What subscription do you have?

pro

Which model were you using?

No response

What platform is your computer?

Windows 10.0.19045.6466

What terminal emulator and version are you using (if applicable)?

JetBrains Rider 2024.3.10 built-in terminal (JediTerm)

Codex doctor report

What issue are you seeing?

Cursor movement (Left arrow) causes characters to visually disappear in JetBrains JediTerm since v0.129.0

What steps can reproduce the bug?

Environment

  • Codex CLI: 0.129.0+ (broken), 0.128.0 (works)
  • OS: Windows 10.0.19045.6466
  • Terminal: JetBrains Rider 2024.3.10 built-in terminal (JediTerm)
  • Shell: cmd.exe / powershell.exe (both affected)

Reproduce

  1. Open Rider's built-in terminal
  2. Run codex
  3. Type test
  4. Press Left arrow key
  5. Character t visually disappears from screen
    (buffer content is intact — pressing Enter still submits full test)

Regression range

  • 0.128.0: works fine
  • 0.129.0: broken

Workaround

Downgrade to 0.128.0.

Note

Other TUI tools (Claude Code, etc.) render correctly in the same terminal,
so this is specific to Codex's rendering strategy change in 0.129.0.

What is the expected behavior?

No response

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.