Occasionally, interactions with artificial intelligence deliver moments of genuine wonder, and one such instance occurred when I turned to Claude for assistance with a small workflow issue at the office. The excitement faded into astonishment upon reviewing my usage statistics afterward.
Each day, I rely on Claude to compile a summary of AI developments by deploying virtual agents to monitor platforms like Reddit, various social networks, and rival news sites. This process also involves checking my recent PCWorld articles to prevent overlaps in coverage.
The routine summary activates through a custom setup in Claude Cowork, a tool that handles tasks on personal computers, and the output is stored as a document on my home Mac mini, retrievable from anywhere using iCloud.
Related: Key guidelines and pitfalls for setting up an AI helper on your computer
While this automated overview isn't essential to my routine—I'm accustomed to sourcing information independently, and it often duplicates my existing knowledge—it serves as a useful addition to my regular review of AI trends. From time to time, it uncovers potential article topics I might overlook, such as the trend of users instructing Claude to communicate in prehistoric style, which Claude itself detected on a lesser-known online forum.
Working from PCWorld's Manhattan headquarters, distant from my home setup, I realized the expected morning update was absent from iCloud, likely due to a malfunction in the on-site Claude Cowork process on my Mac. Such interruptions occur sporadically, possibly from technical hiccups. With the automation confined to my home device, remote manual activation wasn't straightforward.
Undeterred, I proceeded with my standard information gathering on the office desktop but recalled an option: Claude Dispatch, which enables oversight of home-based Cowork activities via the Claude smartphone application. Time to test it.
Launching the iPhone version of the app, I selected the Dispatch section and inputted: 'Locate the routine for the daily summary in the AI article concepts workspace?' Workspaces in Cowork function as dedicated environments, each with tailored directives, routines, and relevant document repositories.
After brief deliberation, Claude responded affirmatively, outlining the routine's specifications. 'Does this match what you need? What action should I take regarding the summary routine—inspect, alter, or another step?'
I instructed it to execute the routine on demand. Claude confirmed: 'Initiated. The summary process will commence shortly, within approximately one minute.'
Moments later, the update appeared in iCloud, delivering the standard morning content. Even though the material was unremarkable, the seamless resolution felt innovative.
Curiosity prompted a glance at my usage dashboard to assess the impact of this short Dispatch session. (For context, I subscribe to the $20 monthly Claude Pro tier.)
Shockingly, the interaction and subsequent routine execution had exhausted 66% of my five-hour daily allocation in just minutes.
This voracious consumption wasn't entirely unexpected; my reporting has highlighted how Claude's advanced Cowork functionalities and programming capabilities rapidly deplete computational resources. Recently, I detailed exhausting a full week's quota for Claude's latest Design feature in under half an hour.
The precise cause remains unclear. The initial failed routine might have contributed some resources, though my allocation had reset well after the scheduled time, weakening that explanation. The repeat execution combined with Dispatch could have spurred the agents into intensive activity. Notably, my morning activities involved no other Claude engagements beyond this episode.
Ultimately, Claude Dispatch proved invaluable in resolving the automation glitch. However, the episode underscores the constraints of budget-friendly subscription models like Pro for handling such efficient yet resource-intensive innovations.