Scheduled-task run sessions flood the session list - group, auto-archive, or bulk-archive them

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 28, 2026

On the desktop app (Windows, Microsoft Store install), every scheduled-task run creates a new session, and those sessions land in the main session list alongside interactive chats, indistinguishable at a glance and never cleaned up.

Real numbers from one workspace: four recurring tasks (a daily sweep, a daily uptime check, a daily feed refresh and a 10-minute inbox watch) accumulated 113 unarchived run sessions in under a month - at which point the session list is mostly machine runs and the human chats are buried. The only bulk remedy discovered is deleting the parent task, which auto-archives its runs; for tasks that are still live there is no route except archiving run sessions one at a time, each with its own confirmation prompt.

The per-run session model itself is good (isolation, bounded context, per-run audit trail) - this is purely a presentation and lifecycle gap.

Requests, any subset of which would help:

  1. Group task-run sessions under their parent task in the session list (collapsed by default), rather than interleaving them with interactive chats.
  2. Auto-archive run sessions after N days (configurable), or keep only the last N runs per task visible.
  3. A bulk archive action for a task's historical runs that does not require one confirmation per session.
  4. A visible marker distinguishing task-run sessions from interactive sessions (the store record already carries scheduledTaskId, so the data exists).

Environment: Windows 11 Pro, Claude Desktop via Microsoft Store, observed August 2026. Related quality-of-life report from the same workspace: #90080 (Remote Control registration).

View original on GitHub ↗