Detailed Analysis
A recent Reddit thread in r/ClaudeAI surfaces a practical friction point in Claude Desktop's scheduled tasks feature: the tasks appear to be tied to a specific device rather than synced across a user's account. The original poster describes attempting to set up a "Daily brief" workflow for a colleague — one that reads email and pulls reporting data from HubSpot via MCP (Model Context Protocol) connections — only to find that when logging into the same Claude account on a second computer, the scheduled tasks don't carry over, even though Projects do sync properly. This raises pointed operational questions: what happens if a laptop dies, or if an employee who set up a task leaves the company and the task needs to be handed off to someone else?
This is a meaningful gap for any organization trying to operationalize Claude beyond individual, ad-hoc use. Scheduled tasks are one of the more business-critical features Anthropic has rolled out for Claude Desktop, allowing recurring automated workflows (daily summaries, report generation, monitoring jobs) rather than one-off chat interactions. If those tasks live locally on a device rather than being synced server-side alongside the account, it undermines the reliability businesses need for automation — a single point of hardware failure could silently break a workflow, and there's no clear administrative path to reassign or migrate ownership of a task when personnel changes occur. For a feature explicitly aimed at recurring, unattended execution, device-level lock-in is a significant limitation, especially compared to how competitors' automation platforms (like scheduled jobs in cloud-based tools) generally treat the automation as tied to the account or workspace, not the local machine.
The underlying issue points to a broader tension in how AI assistant products are evolving from individual productivity tools into infrastructure for teams and companies. Features like MCP connectors (which let Claude interact with external services like HubSpot, email, and other business systems) show Anthropic's ambition to position Claude as a genuine operational layer for businesses, not just a chatbot. But the surrounding scaffolding — admin controls, task ownership transfer, cross-device state sync, offboarding workflows — often lags behind the flashier integration capabilities. This mirrors a pattern seen across the AI agent space generally: vendors race to ship powerful capabilities for connecting models to real-world data and workflows, while the "boring" enterprise IT concerns (continuity, handoff, redundancy, account administration) trail behind, only surfacing once real businesses start relying on the tools day-to-day.
The thread also reflects a documentation and communication gap. The poster notes they "can't seem to find consistent info anywhere," suggesting that Anthropic's public-facing materials haven't clearly addressed whether scheduled tasks are local or cloud-synced, nor provided guidance for team/business continuity scenarios. As more companies adopt Claude for MCP-connected daily workflows rather than personal experimentation, this kind of ambiguity becomes a real barrier to enterprise trust — businesses need explicit assurances about data portability, task ownership, and failure recovery before they'll build critical operations around a tool. Anthropic's broader push toward Claude for Enterprise and Claude Code suggests awareness of this need, but community feedback like this indicates the product still has gaps to close for organizations that want Claude to function as durable, transferable infrastructure rather than a personal utility for individual users.
Read original article →