Claude Dispatch is the longer term. Brace for the quota shock
Each as soon as in awhile, I get a “whoa, that was cool” second from AI, and I bought a type of whereas enlisting assist from Claude to deal with a minor velocity bump at work. I additionally bought a shock when checking my Claude utilization meter after the thrill was over.
Let’s begin with the cool second.
Every morning, I’ve Claude generate a every day AI information briefing, with Claude sending a small crew of brokers to scour Reddit, social media, and competing web sites to inform me what’s producing buzz within the extensive world of AI, whereas additionally cross-referencing my newest PCWorld tales to keep away from repetition.
This every day information report is triggered by an automation I created in Claude Cowork, the Claude characteristic that may carry out duties in your desktop, and Claude saves the every day transient as a textual content file on my Mac mini at residence, which I can entry remotely through iCloud.
Associated: Putting in an AI assistant in your PC? 5 do’s and don’ts
Now, this Claude information digest isn’t mission-critical for me; I’m used to gathering the information by myself, and there are many occasions when the Claude briefing doesn’t choose up something that I don’t already know. Nonetheless, it’s a useful complement to my very own every day scan of the AI sector, and infrequently it comes up with story concepts I in any other case might need missed. (That “Persons are prompting Claude to speak like a caveman” concept, for instance, got here, fittingly, from Claude, which noticed the chatter on an obscure subreddit.)
Anyway, I’m working in PCWorld’s Instances Sq. workplace, away from my residence Mac mini, and I discover that the morning Claude information transient that must be sitting in iCloud is lacking, most likely as a result of the native Claude Cowork on my Mac failed to fireside. (It occurs from time to time, maybe because of a glitch within the Matrix.) And since I’m away from residence and the Claude Cowork automation is native on my residence system, I can’t hearth it manually.
No huge, I believed, as I started my typical information checks on my workplace PC. However then I remembered: May I take advantage of Claude Dispatch, the Claude characteristic that permits you to management native Claude Cowork periods remotely from the Claude cell app, to achieve out and set off that automation for me? Let’s discover out.
I fired up the Claude app for iPhone, tapped the Dispatch tab, and despatched a immediate: “Are you able to entry the every day information transient automation within the AI story concepts venture?” (“Tasks” are particular person workspaces in Cowork with their very own Claude directions, automations, and assortment of related information for reference.)
Ben Patterson/Foundry
Claude thought for a minute or so after which reported again. “Discovered it,” Claude mentioned, giving me the small print of the automation. “Is that the fitting one? And what do you need to do with the information transient automation—examine it, modify it, or one thing else?”
I then requested Claude to set off the automation manually. “Executed,” Claude replied, “I’ve triggered a handbook run for the every day information briefing, firing in about 1 minute.”
A minute or so later, growth—the every day information digest popped up in iCloud, full with my morning briefing. That, I believed, was fairly cool, even when this explicit briefing itself didn’t unearth something out of the peculiar.
Then got here the shock. Out of curiosity, I checked my Claude utilization meter to see how a lot of my Claude allowance had been consumed by my transient Dispatch session. (I’m on the $20-a-month Claude Professional plan, by the way in which.)
The reply? My Dispatch change plus the handbook automation run had wolfed up 66 p.c of my five-hour Claude utilization window, all in a matter of minutes. Whoa.
Once more, I shouldn’t have been too stunned by Claude’s urge for food; I’ve been writing about how Claude’s agentic Cowork and coding skills eat AI tokens like no tomorrow, and I lately described how I blew via every week’s utilization allotment for Claude’s new Design instrument in roughly half-hour.
It’s not clear precisely what Claude did to eat via all that utilization. Maybe the failed morning automation wolfed up some tokens proper there (though my five-hour utilization window had refreshed hours after the common automation schedule, which casts doubt on that concept), after which perhaps the second automation run plus the Dispatch dialog despatched Claude’s crew of brokers into overdrive. Nonetheless, I hadn’t achieved any work or had any exchanges with Claude that morning exterior the Dispatch interplay.
In any occasion, Claude’s Dispatch skills definitely got here in clutch throughout this morning’s automation snafu. However my Dispatch journey additionally proved that inexpensive flat-rate plans like Claude Professional barely have sufficient fuel within the tank for “that was cool” moments like these.

