openai / openai/codex

VS Code extension stops loading older chat history

Open
#44,029 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of the IDE extension are you using?

26.903.61454

What subscription do you have?

plus

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The latest Codex VS Code extension stops loading older chat history when I scroll back.

The Codex desktop app works correctly with the same account and can see all older conversations, so the history is not missing. This issue only occurs in the VS Code extension.

Please check the chat history pagination/loading behavior in the latest extension.

Rolling back may fix the issue, but older extension versions may not support the latest models such as GPT-6.

What steps can reproduce the bug?
  1. Open the Codex extension in VS Code.
  2. Open the chat history and scroll down to older conversations.
  3. The history stops loading at around last Sunday, and no older conversations appear.
  4. Open the Codex desktop app with the same account.
  5. Older conversations are available normally in the desktop app.
What is the expected behavior?

No response

Additional information

No response

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

First reproduce the issue in the VS Code extension by scrolling through chat history, then compare the results with the desktop app using the same account. Trace the extension's chat-history pagination or loading path; done means older conversations continue appearing beyond the current stopping point.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.