VSCode extension crashes in Cursor when opening a conversation
Resolved 💬 4 comments Opened Dec 14, 2025 by benglewis Closed Dec 14, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the VS Code extension are you using?
0.4.51
What subscription do you have?
Business
Which IDE are you using?
Cursor
Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0
What platform is your computer?
MacOS (Darwin) 25.1.0 arm64 arm
What issue are you seeing?
An error has occurred
Codex crashed with the following error:
Codex process errored: Codex process is not available
thread 'tokio-runtime-worker' panicked at core/src/util.rs:21:9:
Custom tool call output is missing for call id: call_0YPo8yA8FuTb2CDuUaV53TiC
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
What steps can reproduce the bug?
Open an old conversation.
What is the expected behavior?
That the extension not crash.
Additional information
I expect the Cursor version upgrade may have something to do with it
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Does this occur as soon as the extension loads, or is there an action you need to do to repro the crash (e.g. start a new conversation or restore an older conversation)?
To diagnose this problem, it would be really useful to have the stack trace for the crash. Could you set the
RUST_BACKTRACEenv variable to1and then relaunch cursor? Then when you see the crash, you should see a full stack trace.This is likely the same bug as #7990, but I'll leave them both open until we have more confirmation.
It does indeed only happen when I open a specific previous conversation, in my case a conversation with
gpt-5.2-codex-max(on high reasoning)