Code tab lost its "Recents" group after update (Home tab still has Recents)

Status Fixed / completed
Reported on v2.1.37
Maintainer reply None cached
Activity 2 comments · opened Aug 7, 2026 · closed Aug 7, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After updating the Claude Code desktop app this morning (Windows 11; update
required a restart), the "Recents" group that used to appear at the top of the
project list in the CODE tab is gone.
The HOME tab still shows its "Recents" list normally — so this is specific to
the Code tab. In the Code tab, the list now only shows projects grouped by
folder (BFE-Finder, Bridge Design Tool, CATT, ...), with no Recents section at
the top. To reach a recently-used project I now have to scroll through the
alphabetical folder groups.
Yesterday (before the update) the Code tab had a "Recents" group pinned at the
top listing my most-recently-used projects/sessions. It disappeared after the
update.

What Should Happen?

The Code tab should show the "Recents" group at the top of the project list,
as it did before the update, so recently-used projects are reachable without
scrolling the full folder list.

Error Messages/Logs

Steps to Reproduce

  1. Open the Claude Code desktop app
  2. Go to the Code tab
  3. Observe the project list — no "Recents" group appears at the top

(Compare: the Home tab still shows a Recents list)

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Type: 2.1.37 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

<img width="295" height="665" alt="Image" src="https://github.com/user-attachments/assets/ccc79a33-e786-416f-b920-1da50f013850" />

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗