Codex Cursor plugin times out when calling newConversation

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Problem summary: Codex extension in Cursor times out on starting a conversation
Environment:
Windows 11 x64 (10.0.26100)
Cursor 1.6.45
Codex extension 0.4.12
Codex CLI: 0.40.0 (npm global); extension is unpinned and should use bundled CLI
Auth: “Logged in using ChatGPT” in Codex; Git operations work

Symptom:
Opening the Codex sidebar or sending any prompt spins ~30–45s, then “Error starting conversation.”
Recent Codex.log shows handshake succeeds, but newConversation times out.
Relevant log snippet:
What works:

  • GitHub auth is fixed; git fetch origin succeeds.
  • MCP results appear in the log (recent conversations, auth status, config).
  • Codex CLI on PATH reports codex-cli 0.40.0; basic CLI commands work.

What I already tried:

  • Fixed previous GitHub environment 404 (now gone).
  • Removed Codex CLI path pin (extension should use bundled x86_64 codex.exe).
  • Backed up Codex config (C:\Users....codex\config.toml → .bak) to force defaults.
  • Updated/reinstalled the Codex extension; Reloaded Cursor.
  • Checked globalStorage for Codex (openai.chatgpt) – folder is missing (nothing to clear).
  • Still get timeouts on newConversation.

Questions for the community:

  • Is there a known issue in Codex extension 0.4.12 where newConversation times out despite MCP/auth working?
  • How can I confirm which codex.exe path the extension actually launches on Windows?
  • Any flags to enable verbose logging for the extension→CLI invocation?
  • Has anyone needed to allowlist the extension’s codex.exe separately in Windows Firewall to fix this?
  • Any other ideas?

Steps to Reproduce

  1. Launch Cursor and open my project
  2. Open Codex sidebar or send a prompt
  3. After ~45s: “Error starting conversation,” and log shows newConversation timeout as above

Screenshots / Screen Recordings

timeout.jpg
timeout.jpg523×174 22.6 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45 (system setup)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. We’ll investigate it.

3

Just circling back to this… the culprit with another extension conflicting with Codex. I disabled it and now Codex works.

4

Hey, glad you found the cause. Could you let me know which extension caused the conflict?