What Claude hand-off and scheduled tasks is good at
- Hand over a report or deck and Claude keeps going after you close your laptop; schedule it (for example every Monday) and it starts without being asked.
- Cloud sessions run on Anthropic's servers and keep working with your computer off; desktop tasks can use your local files, connectors, plugins and apps.
- By default Claude asks before taking an action, and you can switch it to check in only when something needs a closer look.
- Included in Pro, the same plan used for chat and Claude Code.
Where Claude hand-off and scheduled tasks breaks
- It is task and schedule based, not one named agent watching your accounts; tasks that need local files, Chrome or desktop apps need Claude Desktop open and the computer awake.
- Dispatch, the phone-to-desktop persistent thread, is a limited beta and not available to new users; its permission prompts are auto-denied after ten minutes without a reply.
- Background work shares the plan's rolling five hour usage windows and weekly caps with chat and Claude Code.
- Anthropic warns that driving a desktop agent remotely can chain into reading, moving or deleting files and acting in connected services, including because of malicious content the model meets; on Pro and Max, model training is listed as opt-out.
When a custom build beats Claude hand-off and scheduled tasks
When the weekly report pulls the same numbers every time, a scheduled job against the Claude API with batch pricing costs less and never hits a chat usage window.
Setup
No-code. Someone comfortable with spreadsheets can set it up. No code needed.
Sources
- claude.com/blog/cowork-is-now-claude
- support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork
- claude.com/docs/cowork/guide/dispatch
- claude.com/pricing
Price checked 9 Oct 2026. If something here is out of date, email indra@kratuva.com and we will fix it.
