Cowork, agent tasks, and scheduling

Home Tools Platforms Claude Cowork, agent tasks, and scheduling

Give an eligible agent a bounded deliverable and understand its cloud or local workspace.

Conversation & research · Changing · Documentation checked 2026-10-04

Claude apps, projects, and Cowork; Claude Code and Claude Platform are separate environments.

Paid-plan, device, and admin access vary. Cloud Cowork is beta; Pro / Max migration changes start October 6, after this verification date.

The worked example is illustrative and has not been tested in a signed-in product account.

What it does and how it connects

Give an eligible agent a bounded deliverable and understand its cloud or local workspace.

Cowork is agentic knowledge work: it can pursue a deliverable through files and tools rather than only returning an answer. The paid new Claude experience is rolling out and may remove the old mode selector. Cloud Cowork is beta; documented Pro / Max cloud-task changes begin October 6, after this guide’s check date.

Walkthrough

Use the product named in the access panel. The steps below combine documented controls with the editorial example.

  1. Confirm your client, paid plan, workspace policy, and whether the task is local or cloud.
  2. Provide a bounded folder or uploaded source set and an explicit output destination.
  3. Ask for a short plan and keep outbound or destructive actions outside the task.
  4. Review intermediate activity and the actual deliverable; inspect scheduling controls only where available.

Worked example

Prepare a briefing from three approved reports. Give the agent a separate draft-output location so it can create a result without replacing the reports. Scheduling this process should follow a successful manual run with stable inputs.

Using only these three reports, create a draft briefing on AI adoption. Preserve the source files. List sources used, missing evidence, and assumptions. Save a new draft with a clear filename. Stop if a source is inaccessible or if the task would require sending, publishing, deletion, or broader access.

Inspect and verify the result

Open each output and compare quotations, totals, and source references. Confirm where files were read and saved. Review whether an expected local dependency was actually available in a cloud task.

Limits and troubleshooting

An older tutorial may show a different selector or local environment. Plan, platform, and administrator controls affect availability. A scheduled task with an unavailable source should produce an exception, not a silent substitute.

Data, permissions, and actions

Folder and connected-account access can expose more than a single attachment. Cloud and local execution have different data locations. A prompt requesting review is useful, but actual permissions and action gates must constrain consequential tool use.

Incognito, exports, and retention

Understand what temporary conversations exclude, what remains retained, and who can export records.

Explore Incognito, exports, and retention

From reports to an editable briefing

Build a private Artifact from a bounded source set and a verified argument.

Explore From reports to an editable briefing

A bounded Cowork preparation task

Use an eligible agent to prepare a workshop pack while preserving original files.

Explore A bounded Cowork preparation task

Permissions and meaningful approvals

Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.

Explore Permissions and meaningful approvals

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

Cowork and the new Claude experience · Anthropic

Share this page