Install a workflow on Claude Code cloud scheduled tasks

Each run is a full Claude Code session in a fresh cloud machine, with a clone of the task's GitHub repositories and the connectors chosen for it. It runs without stopping to ask for approval, and anything it does through GitHub or a connector appears as the person who made the task.

Run awml fit with the workflow's security view and this description first. If it reports code steps, Claude will carry them out by following instructions, so write each as an exact procedure or a script the instructions run.

What to create

1. A GitHub repository holding the instructions, as CLAUDE.md or a skill at .claude/skills/<workflow>/SKILL.md, any scripts for code steps, and the workflow's contexts under notes if they are kept there. 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. An outside action marked Ask ends in a draft, a draft pull request or a message asking for a yes.
2. A cloud environment. The Default environment allows only its list of trusted domains. If a step must reach another host, edit the environment's network access to Custom and list that host.
3. The task, at claude.ai/code/routines: New task, then Set up manually. Give the name, the prompt and the model, choose a trigger, then under Advanced settings choose the repository and the environment. On the Connectors tab remove every connector the workflow does not name, since Claude can use every tool of an included connector, writes included, without asking.
4. Branch protection on the repository's main branch. Runs push to claude/ branches unless the prompt names another, so say in the prompt where changes to the notes should go.

Where secrets go

Keys for APIs a run calls go in the environment as network secrets, which sessions use without seeing them. Do not use environment variables for keys: anyone who uses the environment can see them. Connectors keep their own authorisation. An API trigger's token is shown once: keep it in the secret store of whatever calls the trigger.

How to schedule the triggers

Pick hourly, daily or weekly, or after creating the task choose Custom in its Edit dialog and give a cron expression no more often than hourly. A run set exactly on the hour can start several minutes late, so choose a few minutes past. From the command line, /schedule creates a task and /schedule update changes its schedule. For a trigger that is an event, add an API trigger and have the sender POST to the task's fire URL, or a GitHub trigger on pull request or release events.

How to check it is running

The task's page lists past runs under History. Open each to read its session: a green status means only that the session started and stopped without an infrastructure error, not that the work succeeded. From the command line, /schedule list lists tasks, and asking /schedule why a run did nothing reads its log. Use Run now once after creating the task.

Sources

• https://code.claude.com/docs/en/routines
• https://code.claude.com/docs/en/cloud-environments