Summary
GET /api/workspaces in the REST API probes connected VS Code instances via a backchannel to get fresh workspace data before responding. The gRPC GetConnectedWorkspaces handler only returns cached getVSCodeWorkspaces() data without triggering a refresh.
This means gRPC clients may see stale workspace lists, especially if VS Code opened new folders since the last backchannel exchange.
Expected behavior
GetConnectedWorkspaces should trigger the same backchannel probe as the REST endpoint before returning results, or at minimum document that it returns cached data and provide a separate RefreshWorkspaces RPC.
Context
Identified during gRPC config parity audit in #32.
Summary
GET /api/workspacesin the REST API probes connected VS Code instances via a backchannel to get fresh workspace data before responding. The gRPCGetConnectedWorkspaceshandler only returns cachedgetVSCodeWorkspaces()data without triggering a refresh.This means gRPC clients may see stale workspace lists, especially if VS Code opened new folders since the last backchannel exchange.
Expected behavior
GetConnectedWorkspacesshould trigger the same backchannel probe as the REST endpoint before returning results, or at minimum document that it returns cached data and provide a separateRefreshWorkspacesRPC.Context
Identified during gRPC config parity audit in #32.