VS Code extension regression: @ picker no longer shows previous conversations since 26.727.40816
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the IDE extension are you using?
26.727.40816
What subscription do you have?
plus
Which IDE are you using?
vscode
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
VS Code extension regression: @ picker no longer shows previous conversations since 26.727.40816
What steps can reproduce the bug?
-
Install VS Code Codex extension 26.721.41059.
-
Open Codex chat.
-
Type "@" followed by a keyword matching an existing conversation title, e.g. "@ntp".
-
Previous Codex conversations appear in the picker and can be referenced.
-
Upgrade the extension to 26.727.40816 or newer.
-
Repeat the same steps.
-
Previous conversations no longer appear in the @ picker.
What is the expected behavior?
Previous Codex conversations should continue to appear in the @ picker so they can be referenced as context, as they did in 26.721.41059.
Additional information
Starting with 26.727.40816, previous conversations are no longer available in the @ picker.
Downgrading to 26.721.41059 restores the feature.
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 regression in the VS Code Codex extension by comparing versions 26.721.41059 and 26.727.40816, using an existing conversation title such as “ntp” in the @ picker. Trace the extension’s conversation-picker and previous-conversation lookup entry points; done means matching conversations appear again in the newer version and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100