Skip to content

Code-OSS (upstream): a contributed session's queued messages are dropped on Reload Window #253

Open

Description

@merecdesperez44323-lab

Upstream Code-OSS behaviour, noted for the Studio (A10 RCA, monkey test 2026-11-15). This is not a Studio bug and has no fix planned here.

What happens

  1. A message is queued in a Pine session's Chat while a turn runs: Enter during a request runs ChatQueueMessageAction, which queues the message (src/vs/workbench/contrib/chat/browser/actions/chatQueueActions.ts:107-113).
  2. The person presses Stop. Code-OSS deliberately leaves the queue alone after a cancelled request: shouldProcessPending = … && !token.isCancellationRequested (chatServiceImpl.ts:2266-2269, consumed at :2315). The queued message stays under "Queued".
  3. The person runs Reload Window, or the window restarts. The queued message is gone, with no message.

Why

  • A contributed session's model is rebuilt from the provider's provideChatSessionContent with pendingRequests: undefined (chatServiceImpl.ts:1085).
  • Local chat sessions serialize their queue (chatSessionOperationLog.ts:217); contributed sessions such as pine-computer do not.

Line numbers are at vscode-w06 1c792ef3 (upstream 235ceeb5 plus the Pine patch series). No Pine patch touches these files.

Related upstream behaviour (works as designed)

After a Stop, the next Send with a queued message opens Code-OSS's "You already have pending requests. Keep Pending Requests / Remove Pending Requests" prompt (chatWidget.ts:4000, :4321-4357). With the default window.dialogStyle: native (desktop.contribution.ts:290-293), it is a native macOS sheet. A CDP-driven test neither sees nor answers it, so in the monkey test Send looked like it did nothing.

Options, if this ever matters

  • An upstream change: persist pending requests for contributed sessions.
  • A Pine patch to Code-OSS.

Neither is planned. Recorded so the loss is known.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions