Open in Editor Often Requires Two Attempts and Is No Longer Directly Accessible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.831.21537
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
When using Open in → VS Code / VS Code Insiders / Cursor from a Codex thread, the selected editor frequently does not open on the first attempt.
On the first attempt:
- The submenu may show “Loading available apps…”
- Nothing opens
- There is no visible error
If I repeat the exact same action a second time, the selected editor usually opens correctly.
This happens across multiple chats/threads, so it does not seem specific to one project.
What steps can reproduce the bug?
- Open any Codex chat/thread.
- Click the ⋯ menu beside the thread title.
- Select Open in.
- Select VS Code, VS Code Insiders, or Cursor.
- Observe that the editor does not open on the first attempt.
- Open the menu again.
- Select Open in → the same editor again.
- The editor now opens successfully.
What is the expected behavior?
The selected editor should open on the first attempt without requiring the action to be repeated.
Additional information
- The issue happens across multiple Codex chats/threads, not just one.
- It occurs with VS Code, VS Code Insiders, and Cursor.
- On the first attempt, the Open in menu may remain on “Loading available apps…” or nothing happens.
- Repeating the exact same action a second time usually opens the selected editor successfully.
- No visible error message is shown.
- The issue is reproducible very frequently, often on almost every thread.
- This appears to be related to the Open in / app detection or launch flow, rather than a specific repository or project.
Environment
- Codex App version: 26.831.21537
- Platform: macOS
- Architecture: Apple Silicon / arm64
- OS: Darwin 25.6.0
- Plan: Plus
Related UI feedback
The Open in editor action is currently nested under:
⋯ → Open in → VS Code / Cursor
Since opening threads in an editor is a frequent action, it would be helpful to have a direct “Open in editor” action on the main thread/page, similar to the previous UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Open in flow from a Codex thread on macOS with VS Code, VS Code Insiders, and Cursor, focusing on the “Loading available apps…” state and the first launch attempt. Trace the app detection and launch entry points; done means the selected editor opens on the first attempt and the action is directly accessible as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- desktop, developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100