VS Code: clicking .ipynb links opens raw JSON instead of the notebook editor
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Description
Clicking a notebook file link in a Codex response opens the .ipynb file as raw JSON in VS Code’s text editor. I have to manually reopen it with the notebook editor each time.
Steps to reproduce
- Ask Codex to create or reference a Jupyter notebook.
- Click the notebook link in its response.
- The file opens as raw JSON.
Expected behavior
Open .ipynb files in VS Code’s notebook editor, respecting the configured editor association.
Environment
- Codex extension:
26.908.40401 - VS Code remote extension host: Linux ARM64
Implementation detail
The installed extension’s file-link handler calls workspace.openTextDocument() followed by window.showTextDocument(). This explicitly selects the text editor. Using vscode.open or handling notebooks through the notebook API should allow the appropriate editor to open.
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 at the file-link handler described in the issue and inspect its use of workspace.openTextDocument() and window.showTextDocument(). Reproduce the link-opening steps with a .ipynb file, then verify that the configured VS Code notebook editor opens instead of the raw JSON text editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100