Detailed Analysis
A Reddit user in r/ClaudeAI has flagged what appears to be a UI regression in the Claude desktop app: the "Last activity" filter, which previously allowed users to narrow the Code tab's session list to those active within 1, 3, 7, or 30 days (or show all), has disappeared from that view. The filter menu for Code sessions now only exposes Status, Environment, Group by, and Sort by options. Notably, the same filter still exists and functions normally in the Home/chat session list, accessible through an identical slider icon that opens a menu including Type, Status, Last activity, and Group by. This inconsistency suggests the removal is isolated to the Code tab specifically, rather than a broader deprecation of the feature across the app.
This kind of discrepancy matters because Claude Code has become a heavily used surface for developers running multiple concurrent or sequential coding sessions, often across different projects, branches, or environments. As session lists grow over time, the ability to filter by recency is a practical necessity for managing clutter and quickly locating recent work. Losing that filter — especially silently, without changelog notes or an official acknowledgment — creates friction for power users who rely on Claude Code as a persistent workspace rather than a one-off chat interface. The fact that the same UI pattern (icon, menu structure) still works elsewhere in the app makes this read more like an unintentional regression introduced in a recent update than a deliberate design decision, though Anthropic has not publicly confirmed either explanation at the time of the post.
This episode is also illustrative of a broader pattern in how AI coding tools are evolving: as products like Claude Code mature from experimental features into daily-driver developer tools, users increasingly expect the same stability, consistency, and feature parity they'd demand from any professional IDE or CLI tool. Small UX regressions — filters vanishing, settings resetting, inconsistent behavior between related views — carry outsized weight for this audience because they disrupt established workflows built around managing many parallel sessions, agents, or tasks. Anthropic's Claude Code has been iterating rapidly, shipping new capabilities like background agents, multi-session management, and IDE integrations, and rapid iteration cycles like these sometimes introduce regressions in secondary UI elements that aren't covered by primary test suites or release notes.
Finally, the thread underscores a recurring theme in how AI companies communicate product changes to their user base: the lack of a clear, centralized changelog or bug-tracking venue for desktop app behavior leaves users guessing whether something is an intentional redesign, an oversight, or a bug worth formally reporting. The original poster's request for "an official place to report/track this" highlights a gap that many fast-moving AI product teams face — feature parity and regression tracking often lag behind the pace of shipping, and community forums like Reddit end up serving as informal QA channels until official acknowledgment or a fix arrives in a subsequent release.
Read original article →