Chapter 15 · DESKTOP
Dispatch, background work and scheduled tasks
Dispatch accepts an outcome and routes work into Cowork or Code tasks. Scheduling runs work at a time or cadence. These are different mechanisms: starting work does not prove it finished.
Video
Steps
- Check eligibility: the Dispatch page requires Pro or Max and the current Desktop app on macOS or Windows. Select Dispatch in the sidebar if available.
- Give an outcome and limits. Specify the workspace or Project if there are several choices, and request drafts rather than automatic sending.
- Watch Running, Awaiting input, Completed or Error states. When approval is requested, open the task and read exactly what it asks to do.
- For scheduled work, set time, cadence and output criteria. Check dependencies on Desktop, files and cloud behavior in current documentation. Verify one run before relying on a long schedule.
Common pitfall: Background work can stop on permission, connectivity or usage limits. Check the result, not just the task name.
Hands-on exercise: Create a sample task that produces a short file without sending anything. Inspect the task status and resulting file.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
Does Running mean the deliverable is ready?
Recap
- Dispatch routes work into tasks
- Scheduling differs from background execution
- Check status and output