[BUG]

Open 💬 2 comments Opened Jul 14, 2026 by mikebronner

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?

On the macOS Claude desktop app, individual runs of a Local scheduled Routine appear as sessions in the Recents list, interleaved with manual chats and with no visual distinction. A high-frequency Local routine (mine fires every 20 minutes) floods Recents with dozens of near-identical entries per day, burying real sessions.

However, they ALSO appear in the Routines section (where I would expect them to live), with all the runs listed in the routine view, in addition to the Recents listing. This duplication in Recents is extremely noisy, and I only noticed this changing recently (maybe in the last week or so).

This is the inverse of #54517, where a user reports routine runs disappeared from Recents (and notes the removal was intentional decluttering). Across versions/platforms the two states are inconsistent, and neither camp is currently served.

What Should Happen?

Since users disagree (#54517 wants them in Recents; this report + #54524 want them out), the durable fix might be a dedicated grouping / configurability — not forcing one behavior globally.

Error Messages/Logs

Steps to Reproduce

  1. Create a Local scheduled Routine on the macOS desktop app that fires frequently (e.g. every 20 min).
  2. Let it run several times.
  3. Open the sidebar → each run appears as a separate session under Recents, with no Scheduled/Routines grouping.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

not sure

Claude Code Version

1.20186.9

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

This is actually Claude Code in the "Claude for Mac" app.

View original on GitHub ↗

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