Detailed Analysis
A Reddit post in r/ClaudeAI has surfaced a notable bug affecting Anthropic's Cowork feature, in which the "Scheduled" tab disappears from the sidebar in both Claude Desktop and the web client at claude.ai. The user reports that Anthropic support confirmed this is a genuine, unresolved platform issue rather than a local caching problem or an account entitlement glitch, and that a full reboot does not fix it. In the interim, the poster discovered a manual workaround: scheduled task definitions are stored locally on disk at `C:\Users\<YourUsername>\.claude\skills\<skill-name>\SKILL.md`, each in its own timestamped subfolder, separate from whatever UI element is supposed to display them. By cross-referencing folder creation dates against when tasks were originally set up, users can identify and remove duplicate or malfunctioning scheduled tasks even when the sidebar itself is broken.
This bug report is significant because it exposes a structural fragility in how Cowork's scheduling system is architected. The disconnect between the local task-definition files and the UI that's supposed to surface them suggests the sidebar is essentially a thin rendering layer over a backend state that can silently desync — a classic failure mode in systems that mix local file-based state with cloud-synced session data. The post's additional detail is arguably more concerning than the sidebar bug itself: since Cowork moved to cloud-based scheduled sessions, Claude has apparently lost the ability to list, edit, or cancel scheduled tasks it created from within a conversation. This means users can no longer rely on natural-language interaction with Claude to manage their own automations — a regression in exactly the kind of agentic self-management capability that scheduled tasks and Cowork are meant to showcase.
The practical implications matter because Cowork's scheduling feature is positioned as a step toward more autonomous, agentic use of Claude — letting the model run recurring tasks (data pulls, reports, monitoring jobs) without a human re-initiating each session. If the mechanism for reviewing, correcting, or canceling those tasks is unreliable — both from the UI and from Claude itself as a conversational agent — it undermines user trust in delegating recurring work to the system. Duplicate tasks silently firing daily, as described in the post, is a low-grade but tangible cost (redundant API calls, cluttered outputs, unexpected side effects) that erodes confidence in autonomous scheduling specifically because there's no clean way to audit or stop it through supported channels.
More broadly, this incident reflects a recurring theme in the current wave of AI agent products: the gap between marketed autonomy and the operational tooling needed to safely manage that autonomy. As companies like Anthropic push toward more persistent, cloud-native agent sessions—moving away from ephemeral, single-conversation interactions—the infrastructure for observability, task management, and error recovery has to mature in lockstep. Bugs like this one, where users are forced to reverse-engineer local file structures and manually delete folders to stop unwanted automated behavior, suggest that the tooling is currently lagging behind the ambition. It's a reminder that as AI systems gain the ability to act independently over time, the guardrails and management interfaces surrounding that autonomy are just as critical as the underlying model capability, and gaps in that layer can quickly become user-facing reliability problems rather than abstract engineering concerns.
Read original article →