openai / openai/codex

[VS Code extension] Queued follow-up messages disappear below composer because scrollbar is hidden

Open
#41,469 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension windows-os
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.825.32147

Which IDE are you using?

VS Code 1.130.0 x64

What platform is your computer?

Windows x64

What issue are you seeing?

Queued user follow-up cards can move below the composer-area fold and appear to have disappeared. The queue is still present, but there is no visible indication that it is scrollable.

The shipped webview asset queued-message-list-ff63FdRy.js configures the queue container with all three of:

  • max-h-[30dvh]
  • overflow-y-auto
  • hide-scrollbar

The same class combination is present in the previous installed extension build, so this is reproducible UI behavior rather than lost model context.

What steps can reproduce the bug?
  1. Start a long-running Codex task in the VS Code extension.
  2. Send multiple follow-up messages while the task is running so they are queued.
  3. Interrupt the run so the queue is paused.
  4. Use a panel/composer height where the queued cards exceed 30dvh.
  5. Observe that older or newer queued user commands move below the internal fold and appear lost because the scrollbar is hidden.
What is the expected behavior?

Every queued user command should remain discoverable. When overflow exists, the UI should provide at least one clear affordance, such as:

  • a visible scrollbar;
  • automatic scrolling to the newest queued command;
  • an explicit expand/collapse control with a hidden-item count.

User commands must not appear to vanish while they are still queued.

Additional information

VS Code's Issue Reporter cannot submit this extension report because openai.chatgpt does not declare an issue-reporting URL. It reports: the extension cannot create an issue because no issue URL is specified. This GitHub tracker is therefore being used directly.

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 inspecting the shipped webview asset queued-message-list-ff63FdRy.js and locate the queue container using max-h-[30dvh], overflow-y-auto, and hide-scrollbar. Reproduce with several queued follow-up messages in the VS Code extension, then verify that queued commands remain discoverable whenever the list overflows through a visible affordance or equivalent behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, vscode
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.