Desktop app 2.37337.1 update removed sidebar folder grouping, hid the Routines section and dropped routine runs from the session list

Status Open
Maintainer reply None cached
Activity 2 comments · opened Oct 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (one sidebar regression with three visible effects)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After the Claude desktop app updated itself (now 2.37337.1 on macOS 26.6.2, Claude Code CLI 2.37337.1), the Code tab sidebar lost the structure I had been using every day:

  1. Folder grouping is gone from the main session list. The list used to show one heading per project folder with that folder's sessions under it, sorted alphabetically. It now shows a single "This computer" heading with every session in one flat list, sorted by session title. The sidebar's "Group by: project" setting no longer groups by folder in the new sections layout; it groups by environment ("This computer" / "Remote Control"), so there is no way to get the per-folder view back.
  2. The Routines section is switched off. It had been visible at the top of the sidebar, which is where I checked on my scheduled routines each day. After the update list_sections reports the Routines section as shown: false, collapsed: true. I did not change this setting.
  3. Routine runs are no longer listed as rows. Sessions created by routines (a daily 05:00 plan, a daily check, a weekly review) used to appear under their project folder like any other session. They now only exist under their routine, and the sidebar tools refuse to group or pin them ("Routine runs show under their routine, not as their own sidebar rows"). With the Routines section hidden, they are invisible.

I made no changes to sidebar settings or preferences between the last working state (yesterday, 14 October 2026) and today.

What Should Happen?

  • An app update should not change the user's sidebar layout, grouping or section visibility. If the layout has to change, the previous grouping (by project folder, alphabetical) should be preserved or migrated, and sections that were shown should stay shown.
  • Grouping the main list by project folder should remain available in the sections layout.
  • Routine runs should still be reachable from the main list, or the Routines section should not be hidden by an update.

Error Messages/Logs

No error. Diagnostic output from the app's own sidebar tools after the update:

Routines section: {"id":"routines","kind":"routines","collapsed":true,"shown":false}
Sessions section:  {"id":"sessions","kind":"sessions","group_by":"project","sort_by":"alpha","session_count":0}

group_by: "project" on the sessions section now renders as a single "This computer" heading.

Attempting to group a routine run:

Session "local_…" is a routine run. Routine runs show under their routine, not as their own sidebar rows, so they can't be grouped, pinned or marked.

Steps to Reproduce

  1. On the Claude desktop app's Code tab, have sessions across several project folders, with the sidebar grouped by project and sorted alphabetically, and the Routines section visible at the top.
  2. Let the app update to 2.37337.1.
  3. Open the Code tab: the main list shows one "This computer" heading with all sessions flat, the Routines section is hidden, and routine runs no longer appear as rows.

Workaround used: created one custom sidebar group per project folder and moved every non-routine session into it. This restores per-project headings but routine runs still cannot be filed, and the Routines section still has to be re-enabled by hand.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

The desktop app build in use on 14 October 2026 (auto-updated; exact prior version not recorded)

Claude Code Version

2.37337.1 (desktop app and CLI)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Claude desktop app (Code tab)

View original on GitHub ↗

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