Background work, Dispatch and scheduling differ
By the end, you will brief a one-off background task, inspect its status and prepare recurring instructions without unnecessary access. Examples are instructional, not recorded runs.
Background work continues without watching each step. Dispatch takes an outcome and routes work to Cowork or Code tasks. Scheduling repeats instructions at selected times or intervals. Starting is not finishing; all paths need output and error checks.
Documentation checked on September 30, 2026 differs on some cloud/local details. Use this bounded workflow and inspect the route in your account.
Start with a small background task
Attach fictional text:
course-status.txt
Chapter 1 is ready. Chapter 2 is under review. Chapter 3 is being edited.
Publication date is unset. Publishing separately has not been decided.
Draft a short report from the attached document only.
Output: chapter status, missing details and one decision question.
Do not search, send or publish.
If a source or approval is missing, state it instead of guessing.
Cloud work may continue with the computer closed. Local folders or tools can depend on an open app. Inspect the route before leaving real work unattended.
Dispatch: specify outcome and workspace
The official Dispatch guide describes Pro or Max and an updated Desktop app on macOS or Windows. If available in the sidebar, choose the intended Project or Code environment. Three lines of summary do not inherently need Dispatch.
In the course-practice Project, prepare two outputs from the existing document:
1. A draft status update for the manager.
2. A pre-publication checklist.
Do not publish, send or change source files.
Ask before creating a task outside this Project.
Check which tasks opened and their destinations. Automatic workspace selection is not enough when similar Projects exist. Dispatch documentation describes computer hosting for phone use; do not promise every route works with the computer off.
Read status and open the result
Documented states include Running, Awaiting input, Awaiting answer, Completed and Error. Waiting for approval is not finished; Error is not a ready report.
Illustrative output:
Status: Chapter 1 ready; Chapter 2 under review; Chapter 3 being edited.
Missing: approved publication date and publishing approach.
Question: publish Chapter 1 separately or wait for all chapters?
Open the transcript and file. Check for invented dates or messages already sent. Answer only a necessary question, or stop. Do not approve an unexpected action just to clear a waiting state.
Dispatch documentation says an unanswered action request may be declined automatically after ten minutes. Do not assume work will continue without your availability for decisions.
Test recurring instructions manually first
Before creating a repeated responsibility, run the instructions manually and inspect the result. Use account-stored material for this exercise rather than relying on local availability.
Prepare recurring-task instructions but do not activate them until I approve.
Name: Course status check - practice.
Goal: read the practice document stored in this account; return status and gaps.
Scope: that document only. No email, calendar, web or sending.
If the source is missing, report that rather than returning an old report.
Suggest a manual test first.
This plans a task; it does not approve scheduling. Scheduled controls can create tasks manually or with Claude; the new interface may accept a conversational description. Read name, instructions, cadence and permission state before Save or Schedule.
Time, source and computer availability
For an actual recurring exercise, choose a cadence you can inspect and stop it after testing. Specify timezone and source. “Every morning” can be ambiguous without a time and timezone.
Updated documentation describes cloud Cowork scheduling but retains some local-task wording. Local Code scheduling requires an awake computer and open app. Do not copy rules between routes.
Repetition does not make context current. An unchanged document produces old information again. For tasks capable of writing or sending, inspect instructions and mechanisms against the approved purpose.
Graded practice
Easy: status versus output
Run one report. Success: identify running, waiting or completed, then inspect the actual output.
Intermediate: Dispatch destination
If available, request two bounded outputs in a practice Project. Success: correct workspace with no sending or publication.
Challenging: scope without drift
Prepare recurring instructions and test manually. Success: missing sources are flagged, stale reports are not called new, and no extra services enter scope.
Cleanup and troubleshooting
After scheduling practice, pause or delete through Scheduled and verify no future run remains. Archiving an output does not necessarily stop its schedule.
No expected run: check route, timezone, app state, prior run and pending input.
Stale recurring result: verify updated source and no reuse of old output.
Wrong Dispatch Project: stop and correct destination before further access or writing.
Unexpected action request: read it rather than approving automatically. Recurrence multiplies small mistakes.
Interface differs from documentation: check current sources and account state. Rollout does not guarantee identical behavior everywhere.
Schedule a task only after its instructions have produced a correct result, with a defined source, limits and stop path.