[vscode-recents] VS Code Recents empty on recent VS Code versions

[PiasekDev]

Extension name

vscode-recents

Description

The VS Code Recents extension is currently showing an empty list for me, although VS Code itself still shows recent projects correctly.

I am not completely sure this is the root cause, but from local debugging it looks like this may be related to recent VS Code storage changes.

What I checked:

• Vicinae logs only show:

[EXTENSION] "Worker exited with code 1"

• Querying the old VS Code state DB returns no row:

sqlite3 ~/.config/Code/User/globalStorage/state.vscdb \
    "select value from ItemTable where key = 'history.recentlyOpenedPathsList';"

• Querying the new shared storage DB does return my recent projects:

sqlite3 ~/.vscode-shared/sharedStorage/state.vscdb \
    "select value from ItemTable where key = 'history.recentlyOpenedPathsList';" | jq .

This seems similar to issues/fixes in other projects after VS Code 1.118 moved recently opened history to shared application storage:

• VS Code change: share recent folders between apps microsoft/vscode#311963
• Similar Raycast extension issue: [Visual Studio Code] Search recent projects no longer shows projects on current VS Code version raycast/extensions#27537
• Similar PowerToys Run VS Code Workspaces fix: Fix VS Code Workspaces shared storage lookup microsoft/PowerToys#47505

Possible fix, if this diagnosis is correct: for recent VS Code versions, read from ~/.vscode-shared/sharedStorage/state.vscdb first, then fall back to the legacy ~/.config/Code/User/globalStorage/state.vscdb.

Steps to reproduce

1. Use VS Code 1.118+ with some recent projects visible in VS Code.
2. Install/open the Vicinae VS Code Recents extension.
3. Open the Recents command/view.

Expected behavior

The extension lists the same recent projects that VS Code shows.

Actual behavior

The Recents view is empty.

Vicinae version

v0.20.15 (commit a0b875caf)

[github-actions]

cc @ShyAssassin

[ShyAssassin]

Currently i am not on the latest VSCode version so i cant really test if the fix you proposed would work, i will create a PR sometime later today to update the paths and ping you for testing.

[ShyAssassin]

Sorry for taking a while, this is a larger change than i thought
Who thought changing this path to not follow XDG stuff was a good idea