Can't use codex command with "Error: The cursor position could not be read within a normal duration" message

Resolved 💬 5 comments Opened Sep 28, 2025 by jayn2u Closed Nov 26, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.23.0

Which model were you using?

_No response_

What platform is your computer?

Linux 5.15.148-tegra aarch64 aarch64 & Linux 5.15.0-153-generic x86_64 x86_64

What steps can reproduce the bug?

  1. Login codex with using vscode extension.
  2. Use codex command in warp terminal

What is the expected behavior?

Hope to open just normal codex prompt ui.

What do you see instead?

"Error: The cursor position could not be read within a normal duration" message appears instead.

Additional information

Just only warp terminal can't open this codex cli. I think it might be the problem of warp, not codex cli.

View original on GitHub ↗

5 Comments

amittell · 10 months ago

I'm encountering the same error, in Warp.dev Codex is currently non-functional.

CXwudi · 9 months ago

My usage was funny, I try to run codex within Gemini CLI using the Gemini CLI new interactive shell

<img width="1478" height="906" alt="Image" src="https://github.com/user-attachments/assets/c02cadb7-8e38-4bdd-90eb-0fc4c3a7c76f" />

Meanwhile it works fine for claude

<img width="2560" height="1402" alt="Image" src="https://github.com/user-attachments/assets/acc41a18-c1d6-4cb4-97ab-007f4bab68f8" />

gokuldharan · 7 months ago

Still running into this!

etraut-openai contributor · 7 months ago

@gokuldharan, when this occurs, please use the /feedback slash command to upload your logs and session details and open a new bug report. We'll need that additional information to diagnose the problem.

yigitkonur · 6 months ago

same here!