Desktop app: folder picker "Recent" list capped at 8 (was 20+), and scheduled routines crowd out real projects

Status Open
Maintainer reply None cached
Activity 3 comments · opened Sep 18, 2026

Environment: Claude Desktop 2.2553.1 (Windows Store/MSIX build), Windows 10 Pro 19045. Regressed in a build between 1.46388.4 (2026-09-05) and 2.110.0 (2026-09-17); the long list was still present in early September.

What happens

The "Recent" group in the Code tab's folder picker (No folder / Recent / Open folder…) now shows at most 8 folders. It used to show 20+. Because the list is recomputed from session activity rather than kept, it churns constantly — I have to Open folder… and re-browse to my project directories most days.

Why (from reading the renderer bundle)

The list is derived on every render in the module that owns the ccd-dismissed-recent-folders-v1 store:

  • getAll() (all local session records) → group by originCwd → rank by newest lastActivityAt ?? createdAt → .slice(0, 8) (var _=8). The SSH/WSL variant is .slice(0, 5).
  • Sessions spawned by scheduled routines (records carrying scheduledTaskId) are not excluded. With six daily routines each running in its own folder, they occupy 6 of the 8 slots every morning, so anything I worked on yesterday is evicted unless it was one of the two most recent folders. Reproduced from my own session records for three consecutive days.
  • The hover-X "Remove from recent" doesn't help: a dismissed folder is re-shown as soon as a newer session exists there, and the dismissal record is then deleted. A routine un-dismisses its folder on its next run.
  • Path spelling is not normalized — C:\ and C: are counted as two folders and take two slots.

Expected

  • A materially larger cap (the previous 20+), or a user-visible way to pin folders in this picker.
  • Routine-spawned sessions (scheduledTaskId set) excluded from the frecency ranking, or at least weighted below interactive sessions.
  • Dismissal should survive routine runs — either persist it until the user starts an interactive session there, or exclude routine sessions from the "newer session" test.
  • Normalize path spelling before grouping.

Repro

  1. Have several scheduled routines (Routines sidebar) that run in different folders.
  2. Work in 3–4 projects during the day.
  3. Next morning, open the folder picker: routine folders fill most of the 8 slots; yesterday's projects are gone.

View original on GitHub ↗

3 Comments

JimMcBubbles · 26 days ago

Correction on the regression window. This isn't a desktop-app build change — the Code tab UI is served from assets-proxy.anthropic.com, and pulling the earlier hashes of the frecents module (c749529a1-*, Aug 22 → Sep 17) shows what actually happened:

  • Through the Sep 10 build the local list had a capTotal switch driven by the GrowthBook flag ccd_recent_folders_dismiss_main (the same flag that enables the hover-X dismiss). Flag off: [...sessionFolders /* uncapped */, ...detected.slice(0, max(0, 10 - n))] — every folder with a session. Flag on: [...sessionFolders, ...detected].slice(0, 8).
  • That flag rolling on for my account (~early September) is the moment the list collapsed from 20+ to 8.
  • The Sep 17 build (c749529a1-BaBwa-p0.js) removed the flag and hard-coded the capped path (var _=8).

So the request reduces to: restore the uncapped session-folder list (or a cap in the 20s) now that the dismiss feature is shipped, and exclude scheduledTaskId sessions from the ranking — with an 8-slot list, six daily routines evict everything else overnight.

non-x2 · 15 days ago

+1 — same here on Windows 11, Claude Desktop 2.9939.4.0 (MSIX).

I work across 15–20 project folders in parallel, so the ones I need keep falling off the 8-item "Recent" list and I have to go through "Open folder..." every time.

Would love either ~20 recent folders again, or a setting to choose the count (e.g. 8 / 15 / 20 / 30). Pinning favorite folders to the top would also solve it.

aklaunch · 9 days ago

Seeing this on macOS too, where Recent only shows 6. I need about 10. Pinning folders there would solve it.