# 3.7 How today's tools support the rhythm (/ai-worker-paradigm/the-10-80-10-operating-rhythm/both-ai-vendors) --- type: Document title: "3.7 How today's tools support the rhythm" description: "How the two AI vendors and open-source tools support the rhythm in work that runs on a schedule, the differences that change a decision, and what stays true on each." status: stable order: 103.7 ksor: owner: team:panaversity audience: [ public ] approval: by: process:panaversity at: 2026-11-04T06:52:55Z chapter: "03" part: I expert_status: required concepts: [ "3.7" ] last_verified: 2026-10-04 review_by: 2026-11-04 sources: - id: anthropic-scheduled-tasks title: "Schedule recurring tasks in Claude Cowork (Claude Help Center, updated 29 September 2026, verified 2026-10-04)" resource: https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork - id: anthropic-scheduled-tasks-local title: "Schedule recurring tasks in Claude Cowork, where a task runs (Claude Help Center, verified 2026-11-03)" resource: https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork - id: anthropic-scheduled-tasks-plans title: "Schedule recurring tasks in Claude Cowork, the plans that have them (Claude Help Center, updated 30 October 2026, verified 2026-10-31)" resource: https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork - id: anthropic-cowork-surfaces title: "Use Claude Cowork on web, desktop, and mobile (Claude Help Center, verified 2026-11-03)" resource: https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile - id: anthropic-cowork-safely title: "Use Claude Cowork safely (Claude Help Center, updated 16 September 2026, verified 2026-10-04)" resource: https://support.claude.com/en/articles/13364135-use-claude-cowork-safely - id: openai-scheduled-tasks title: "Scheduled tasks in ChatGPT (OpenAI Help Center, verified 2026-10-04)" resource: https://help.openai.com/en/articles/10291617-scheduled-tasks-in-chatgpt - id: openclaw-automations title: "Automations (OpenClaw documentation, verified 2026-10-23)" resource: https://docs.openclaw.ai/automation/cron-jobs - id: omnara-cron-trigger title: "Create a cron trigger (Omnara API reference, verified 2026-10-23)" resource: https://docs.omnara.com/api-reference/endpoints/configs-and-profiles/create-cron-trigger - id: omnara-permissions title: "Tool permissions (Omnara documentation, verified 2026-10-23)" resource: https://docs.omnara.com/tools/permissions - id: omnara-integrations title: "Integrations (Omnara documentation, verified 2026-10-23)" resource: https://docs.omnara.com/integrations/overview - id: openclaw-sandbox title: "Sandboxing: modes, scope and backend (OpenClaw documentation, verified 2026-10-23)" resource: https://docs.openclaw.ai/gateway/sandboxing/modes-scope-and-backend - id: omnara title: "Omnara README (Omnara, GitHub, Apache 2.0, verified 2026-10-23)" resource: https://github.com/omnara-ai/omnara/blob/main/README.md - id: openclaw-dedicated-machine title: "Secrets and storage (OpenClaw documentation, verified 2026-10-23)" resource: https://docs.openclaw.ai/gateway/security/secrets-and-storage - id: openclaw-exposure title: "Exposure runbook (OpenClaw documentation, verified 2026-10-23)" resource: https://docs.openclaw.ai/gateway/security/exposure-runbook generated: at: 2026-11-04T06:52:55Z by: process:panaversity trust_tier: unverified build_id: sha256:46fd53c5d7ab1c14f6347908d45c9fdaecda4d914439923ee878bdcecd57803e dirty: true ksor_version: 0.0.60 --- **In everyday life.** You can ask your bank to send money for you on a schedule, such as your rent every month. Banks keep these scheduled transfers safe in different ways. - **The first bank, like Claude.** When you set up a scheduled transfer, it asks you to pick one setting for it: ask me before every transfer, check each transfer for me, or don't ask at all. One choice covers everything that scheduled transfer does, as Claude's approval mode covers every action in a scheduled task. - **The second bank, like ChatGPT.** It asks you to approve only certain kinds of transfer, such as payments to someone you have never paid before. Everything else goes through. As on ChatGPT, only some kinds of action need you. - **The safest account.** Either way, the safest account is one that no scheduled transfer can reach at all. An approval only makes a person decide. An account no transfer can reach makes a wrong transfer impossible. Both AI vendors let an everyday user hand over recurring work that runs while they are away: a **scheduled task**. That is where the rhythm is most at risk, because nobody watches the middle. Here is how the two AI vendors this book covers support each part of the rhythm in a scheduled task today. Anthropic makes Claude, and OpenAI makes ChatGPT. Open-source tools can do the same on computers you run yourself. > **Anthropic, as verified 15 October 2026.** **Scheduled tasks** are on all paid plans: Pro, Max, Ultra, Team and Enterprise, as of 31 October 2026.[^anthropic-scheduled-tasks-plans] You set one up on the Scheduled page, or by describing it in a conversation and confirming. Claude saves your instructions, and runs the task hourly, daily, on weekdays, weekly or on demand, with your connected tools, skills and plugins. Tasks run remotely, so they run even when your computer is asleep.[^anthropic-scheduled-tasks] As of 3 November 2026, two Anthropic pages differ on a task that needs files or apps on your computer. The scheduling page says such a task runs only on your computer.[^anthropic-scheduled-tasks-local] The page on web, desktop and mobile says new scheduled tasks run in the cloud and reach your files only while the Claude Desktop app is open.[^anthropic-cowork-surfaces] So check where your task says it runs. > > - *First 10:* when you set a task up by hand, you choose its **approval mode**: Manually approve, Automatically approve or Skip all approvals. Anthropic's steps for scheduling from a conversation do not mention the setting, so check it on the Scheduled page after you create the task.[^anthropic-scheduled-tasks] > - *Middle 80:* in Automatically approve, Claude checks each action for safety before it runs it. In Skip all approvals, nothing checks the task's actions. In every mode, Claude asks before it permanently deletes files. Anthropic advises starting with low-risk tasks, such as summaries, and advises against scheduling tasks that send messages, make purchases or take other actions that are hard to undo.[^anthropic-cowork-safely] > - *Final 10:* each run is its own session. You review upcoming and past runs on the Scheduled page, where you can also pause, edit or run a task,[^anthropic-scheduled-tasks] and Anthropic advises reviewing the output after each run.[^anthropic-cowork-safely] > **OpenAI, as verified 15 October 2026.** **Scheduled tasks** in ChatGPT run once, on a schedule, or as monitoring tasks that watch for a change and notify you. They are on every plan, with limits: Free users can run a task at most once a day, and each plan limits how many tasks can be active at once. **Event-triggered tasks**, which respond to activity in Gmail, Slack or GitHub, are not available on Free or Go. On Enterprise and Edu, an admin must switch them on first.[^openai-scheduled-tasks] > > - *First 10:* you write the instructions. For an event-triggered task, you review its **Trigger**, **Condition** and **Prompt** before you rely on it. In managed workspaces, admins may control which apps and actions are allowed. > - *Middle 80:* connected apps read or act within the permissions you granted. An action that sends a message or changes data in another app may need approval. If it does, the task **pauses** until you review it. > - *Final 10:* you review results on the Scheduled page. If a task stops responding, OpenAI says to check there for a paused task or a pending approval, and to confirm the app connection is still authorized.[^openai-scheduled-tasks] > **Open source, as verified 23 October 2026.** Two of the book's open-source projects run work on a schedule. **Automations** are OpenClaw's scheduler: one-time jobs, cron schedules, webhooks and Gmail triggers. Each wakes the agent at the set time and can send the result to a chat app.[^openclaw-automations] In Omnara, a **cron trigger** starts a new agent on a schedule, or sends input to one that is running, in the time zone you choose.[^omnara-cron-trigger] > > - *First 10:* you write the job's instructions, and you set each tool yourself. In Omnara, each tool is set to always allow, always ask or always deny. Tools from connected MCP servers start at ask, and Omnara's own tools start at allow.[^omnara-permissions] > - *Middle 80:* a tool set to ask stops the agent until a person approves, in Omnara's dashboard or in Slack or Discord.[^omnara-integrations] OpenClaw's tools run on the computer itself unless you turn its sandbox on, and the sandbox is off by default.[^openclaw-sandbox] > - *Final 10:* Omnara saves every step of every agent, so you can read what each run did.[^omnara] > > *Running it safely:* run a scheduled assistant on a dedicated machine, VM or container, with its own credentials,[^openclaw-dedicated-machine] and never open it to the public internet.[^openclaw-exposure] **The difference that changes a decision.** The two AI vendors ask for approval in different ways. On Claude, approval is one **setting per task**: you choose the approval mode once, and it covers every action the task takes. On ChatGPT, approval applies to **kinds of action**, mainly sending messages and changing data in other apps, together with your app permissions and your admin's rules. With open-source tools, you set the limits **tool by tool**, and the starting settings matter: some tools start at allow, and OpenClaw's sandbox starts off. Whichever you use, an action waiting for approval is your approval queue (see [Lesson 3.3](middle-80-percent.md)). A task stuck waiting for approval produces no results, so it looks exactly like a quiet night. That is why "silence is not success" (see [Lesson 3.4](final-10-percent.md)) matters most here. So Brightline would set up its monthly reconciliation, a scheduled task that must never change the register, differently on each. - *On Claude:* the approval mode covers the whole task. Manually approve can make a person approve every step, including harmless ones, so Dave ends up running the task step by step himself (see [Lesson 3.3](middle-80-percent.md)). That is why the better design is a task that only reads and reports, with Manually approve as an extra layer of safety. Any change to the register is made later, in a separate step Dave reviews. - *On ChatGPT:* the task can read freely, and it pauses when an action needs approval under the permissions and rules that apply. So Dave's review must include checking the Scheduled page for paused tasks, not just reading the reports that arrived. - *On an open-source runtime such as Omnara:* set every tool that could change the register to always deny, and every tool that writes to the vendor to always ask. Then Dave's review includes the saved steps of each run, not just its report. On all three, the strongest limit is simple: the task cannot use access it was never given. A task with read-only access to the register cannot change it through that connection, as long as no other connected tool can write to it. > [!TIP] > **Before the first scheduled run, whichever tool you use** > > 1. **Give the least access that works.** Connect only the tools the task needs, and read-only where you can. > 2. **Know where it will wait for you.** On Claude, check the task's approval mode. On ChatGPT, know which of its actions can pause it. In an open-source tool, check every tool's setting, because some start at allow. > 3. **Run it once while you watch.** Use last month's data where you know the answer, as in a dry run (see [Lesson 3.2](first-10-percent.md)), before the schedule takes over. > 4. **Put your review in the calendar.** Pick the times you will read its results and check for paused or missing runs (on Claude and ChatGPT, on the Scheduled page), so that silence is never mistaken for success. > [!IMPORTANT] > **The invariant** > > Decide the limit in the specification first. A limit that always applies goes in the Role Contract; a limit for one task goes in the brief. For Brightline's reconciliation, one limit is "never change the register." Then turn it into whatever controls the product offers. **A product setting can make a person decide. Only removing every access path makes an action impossible.** > > Rules that need judgment, such as "stop if the gap cannot be explained," are written in the instructions on every product. (The gap is the difference between the vendor's statement and the register.) Their measurable parts can also get automated checks, for example that the listed differences add up to the gap. The judgment itself is checked in the final 10. If you replace either AI vendor, or move to an open-source tool, that division stays the same. ![Three strengths of limit, drawn as three stacked bands, with an arrow labeled "Stronger prevention" pointing up. The subtitle says to define the limit in the specification, then enforce it at the strength it needs. The top band, in dark blue, removes every access path. Then the worker cannot do the action with the tools and credentials it has. At Brightline, that is read-only access to the register, with no other tool or credential that can write to it. The middle band, in purple, enforces an approval step. The action waits until an authorized person approves it, and the route that carries it out must enforce that step. At Brightline, a proposed register correction or vendor credit waits for Dave's approval before it is posted. The bottom band, in amber, states the rule and checks the result. Rules that need judgment go in the instructions, measurable checks are automated, and a person judges the reasoning. At Brightline, the rule is "Stop if the gap cannot be explained." An automated check asks whether the differences add up to the gap, and a person asks whether the explanations are supported. A banner reads: "An instruction guides. An approval gate holds. Removed access prevents."](./img/three-strengths-of-limit.png) *Figure 3.13. Three strengths of limit. Removing every access path makes an action impossible. An approval step makes a person decide. A rule that needs judgment is written in the instructions and checked in the final 10. Its measurable parts also get automated checks.* [^anthropic-scheduled-tasks]: Schedule recurring tasks in Claude Cowork, Claude Help Center, accessed 15 October 2026. [^anthropic-scheduled-tasks-local]: Schedule recurring tasks in Claude Cowork, Claude Help Center, accessed 3 November 2026. [^anthropic-scheduled-tasks-plans]: Schedule recurring tasks in Claude Cowork, Claude Help Center, accessed 31 October 2026. [^anthropic-cowork-surfaces]: Use Claude Cowork on web, desktop, and mobile, Claude Help Center, accessed 3 November 2026. [^anthropic-cowork-safely]: Use Claude Cowork safely, Claude Help Center, accessed 15 October 2026. [^openai-scheduled-tasks]: Scheduled tasks in ChatGPT, OpenAI Help Center, accessed 15 October 2026. [^openclaw-automations]: Automations, OpenClaw documentation, accessed 23 October 2026. [^omnara-cron-trigger]: Create a cron trigger, Omnara API reference, accessed 23 October 2026. [^omnara-permissions]: Tool permissions, Omnara documentation, accessed 23 October 2026. [^omnara-integrations]: Integrations, Omnara documentation, accessed 23 October 2026. [^openclaw-sandbox]: Sandboxing, modes, scope and backend, OpenClaw documentation, accessed 23 October 2026. [^omnara]: Omnara, README on GitHub, accessed 23 October 2026. [^openclaw-dedicated-machine]: Secrets and storage, OpenClaw documentation, accessed 23 October 2026. [^openclaw-exposure]: Exposure runbook, OpenClaw documentation, accessed 23 October 2026.