openai / openai/codex

[macOS] Open in ChatGPT from a shared Codex chat flashes sidebar without opening a task

Open
#44,681 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using?

ChatGPT/Codex desktop 26.903.71938, build 8576, bundle identifier com.openai.codex. Verified from the installed application's Info.plist.

What subscription do you have?

Pro $200/mo subscription.

What platform is your computer?

macOS 26.6.2 (build 25G83), Apple Silicon.
uname -mprs: Darwin 25.6.0 arm64 arm.
Browser: Google Chrome.

What issue are you seeing?

Opening someone else's shared Codex conversation via Continue in ChatGPT → Open in ChatGPT makes the desktop app's sidebar briefly flash gray, then nothing else happens. No continuation task or composer appears, and no actionable error is shown.

The shared conversation itself loads successfully in the browser, including its interactive visualizations. The failure is in continuing it in the desktop app.

What steps can reproduce the bug?

Observed with an existing shared Codex conversation:

  1. Open a valid shared Codex URL of the form https://chatgpt.com/s/cx_<32-hex-character-id> in Chrome.
  2. Click Continue in ChatGPT.
  3. In the Continue in the ChatGPT app dialog, click Open in ChatGPT.
  4. Observe the desktop sidebar flash gray without opening a continuation task.

The exact share URL is omitted because the source conversation belongs to someone else.

What is the expected behavior?

The action should open a continuation composer/task populated from the authorized shared snapshot, or show a clear error explaining why continuation is unavailable.

Additional information

Read-only inspection of the installed application found a concrete no-op in the desktop deep-link navigation path:

  • The parser recognizes codex://shared-thread/cx_<32-hex-character-id> and returns a route with kind: "sharedCodexSnapshot".
  • In app.asar/.vite/build/main-Bkkz0ENj.js, navigation function nIe handles that route as follows (formatting normalized):
case "sharedCodexSnapshot":
  return;

That branch performs no navigation or snapshot import. The surrounding deep-link setup passes parsed routes to this navigation function. This static finding is consistent with the app reacting to the link while no continuation opens; a live handler call stack was not captured. The installed app was not modified.

Impact: The source task contains an interactive visualization whose temporary working files are on the original author's machine. Copying the visible transcript into a fresh task is not equivalent to preserving the artifact source and dependencies. The continuation flow should make clear which shared artifacts/files can transfer and which require an export from the author; this report does not assume access to their unshared filesystem.

Related issue checked: #33278 concerns an imported ChatGPT task freezing after it has been created. Here, a shared Codex snapshot link never opens a continuation task at all. Searches for the button labels, shared snapshots, and sharedCodexSnapshot did not find an existing report of this specific no-op.

Private conversation content, share IDs, local user paths, and raw logs are omitted.

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.

Research direction

Start by tracing the deep-link parser and navigation function nIe, focusing on the sharedCodexSnapshot route identified in app.asar/.vite/build/main-Bkkz0EN.js. Reproduce the shared URL flow in Chrome and verify that Open in ChatGPT either opens a continuation composer/task from the authorized snapshot or displays a clear error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, macos
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.