Support “Add to Codex Thread” for selected code in Jupyter Notebook cells
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
IDE Extension
What feature would you like to see?
I would like the Codex VS Code extension to support adding selected code
from Jupyter Notebook (.ipynb) cells directly to the current Codex thread.
Environment:
- macOS
- VS Code
- Codex extension version: 26.810.41047
- Microsoft Python and Jupyter extensions installed
Steps to reproduce:
- Open an .ipynb file in VS Code.
- Select code inside a Jupyter code cell.
- Right-click and choose “Add to Codex Thread”.
- Nothing is added to the Codex composer, and no error is displayed.
Expected behavior:
The selected code should appear as context in the current Codex composer,
including the notebook filename and preferably the cell identity.
Actual behavior:
The command has no visible effect.
Important comparison:
The same selected Jupyter cell code can be added successfully to VS Code’s
built-in Chat, so the notebook selection itself is working.
This feature is important for learning, data analysis, and notebook-based
Python workflows. Copying and pasting manually loses file and cell context.
Additional information
No response
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
Reproduce the issue in VS Code with an .ipynb file, selected cell code, and the “Add to Codex Thread” command, then trace that command's handling of notebook selections. Compare the working built-in Chat behavior and verify that the selected code reaches the Codex composer with the notebook filename and cell identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100