awml / platforms / claude-cloud-tasks

Claude scheduled tasks in the cloud

Platform · Public ·
Version 2 of 2
  1. #2 · chrismdp · · 0.4ShowingLatest
  2. #1 · chrismdp · · 0.3

Scheduled tasks in the Claude app (claude.ai, formerly Claude Cowork), which run in the cloud on Anthropic's servers and reach outside services through the connectors the person has added. This describes a kind of platform, not anyone's account. Checked against Anthropic's documentation on 22 October 2026.

Install a workflow on Claude scheduled tasks in the cloud

Each run is a Claude session on Anthropic's servers, which carries out the task's instructions and reaches outside services through the connectors on the person's Claude account. It runs whether or not the person's computer is on.

Run awml fit with the workflow's security view and this description first. This platform holds no folders, so every context the workflow keeps must live in a connected service, such as Google Drive or Notion, and the workflow should draw that service as a connector. If the fit reports code steps, Claude will carry them out by following instructions.

What to create

  1. A connector for every connector the workflow names, at claude.ai under Customize, then Connectors. A person's connector uses that person's own account.
  2. The instructions, as a skill on the person's Claude account, or in the task's own prompt. Give one section to each step, in the order the drawing lists them, saying what it reads, what it writes and what its operation must not do. A draft step writes a draft and never sends it. An outside action marked Ask ends in a draft, or a message asking the person for a yes.
  3. The scheduled task. In the new Claude experience, describe the work and how often it should run in a conversation, answer Claude's questions and click Schedule on the task it proposes. Where Claude Cowork is still separate, choose Scheduled in the sidebar, then New task, then Set up manually, and give the name, the prompt, the approval mode, the frequency and the model. Leave the folder empty: a task that needs local files runs on the computer instead.

Where secrets go

Connectors keep their own authorisation on Anthropic's side, and connector tokens never enter the sandbox where code runs. Never paste a key or password into a task's prompt, a skill or a chat. A step that needs a key of its own for an outside API does not belong on this platform as it is set up by default, since the sandbox reaches only allow listed destinations.

How to schedule the triggers

Choose hourly, daily, weekly or weekdays when creating the task, or manually to run it only on demand. Tasks run on their cadence even when the computer is asleep or the app is closed. A trigger that is an event, such as an email arriving, needs a different platform.

How to check it is running

Choose Scheduled in the left sidebar, on any device, to see upcoming and past runs. Open a run to read its session and what it made. Use Run now once after creating the task, then read the result before leaving it to run.

Sources

  • https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork
  • https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview
  • https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude
  • https://support.claude.com/en/articles/16761823
  • https://support.claude.com/en/articles/12512180