What are the three primitives Anthropic shipped that enable agents to work while you’re away?
Scheduled tasks in Anthropic’s cloud, Dispatch (a mobile orchestration layer for spawning parallel agents), and Computer Use (remote control of desktop apps that lack APIs).
How do Anthropic’s scheduled tasks work and what limits should you expect?
Scheduled tasks run in Anthropic’s managed cloud environment with configurable network access, environment variables and connectors (GitHub, Linear, Drive, OpenBrain, etc.). They’re meant for periodic checks (hourly or multi-hour intervals), not sub-minute continuous polling.
What real constraints remain when using Dispatch and Computer Use?
Some workflows still require the user’s desktop to be powered on (Claude can’t reliably wake a sleeping machine yet), tasks may need per-access approvals, mobile cannot always receive complex file outputs directly, and multi-app complex tasks have lower success rates in early testing.
How should builders and users think about deploying these agent features?
Adopt a management mindset: design agents to get genuine work off your desk (automating recurring, compounding tasks) rather than producing extra “pseudo work” like unnecessary proactive briefings; focus on clear intents, prompts and ground-truth connectors so outputs are actionable.