Chapter 6. Scheduled Tasks, Cloud, and Mobile — Run on Time, Even While You're Away
Optional Read this when you need it. You can skip it and still follow the later chapters.One-line summary: Run weekly routines with Scheduled tasks. A scheduled task that uses your local folder needs your computer turned on and the app running. Cloud tasks are for people with a GitHub repository, and your phone acts like a remote control for your computer.
This chapter is based on the Codex official docs checked on November 1, 2026. This guide did not save an actual scheduled task. Doing so would expose real work content and use up usage limits (for the same reason as Claude Code Chapter 8).
Running a Weekly Review with Scheduled Tasks
Scheduled tasks let you set up recurring work to run in the background.[1] You can view all your scheduled tasks and their run history under Scheduled in the app sidebar.[2]
You create scheduled tasks in the desktop app or on the web, through chat as usual.[3][4] Inside a scheduled task, you can also call a skill using $skill-name.[5] Using the skill from Chapter 5, you can ask like this:
Every Friday at 6 PM, use $weekly-review to create this week's weekly review in the notes folder.There is a condition. A scheduled task that uses a folder on your computer only runs when your computer is on and the app is running.[6] If you plan to use scheduled tasks, check your computer's power and sleep settings to make sure it is not asleep at that time.
The app's "Prevent sleep while running" setting (click to expand)
On macOS and Linux, the Prevent sleep while running setting keeps your computer from going to sleep while a chat is running, so it continues even if you step away.[7] It does not keep your computer awake until the scheduled time. That is why you need to check your computer's power and sleep settings separately, as above.
Scheduled tasks run unattended (without a person watching). Because of this, they keep your default boundary (sandbox) range, but run without asking for permission unless your organization blocks it.[8] Since no one is there to answer prompts, any action outside the boundary will fail.
| Your Default Permission (Boundary) | What Happens in a Scheduled Task |
|---|---|
| Read-only | Scheduled tasks that need to write files fail |
| Write inside folder | Tasks that only write inside the folder, like the organizer tool, will run |
| Full access | Uses files, commands, and the internet without asking (risky) |
Source: Codex official docs (excerpted; the middle row is this guide's summary)[9][10]
Here is how it maps to the permission menu from Chapter 4.[11]
- Ask for approval and Approve for me: Use the middle row's boundary (write inside folder).
- Full access: Uses the last row.
However, in a scheduled task, even Ask for approval will not ask you.
Before you create a scheduled task, run the same request in a regular chat first. Just like in Chapter 5, check the result against your original files, and move it to a schedule only when it looks good. Make sure to check the results of the first few runs as well. The official docs recommend this exact order.[12]
Quick check
You set up a schedule to create a weekly review in your organizer folder every Friday. What is needed for that scheduled task to run?
How Is the Cloud Different?
Cloud tasks run in a workspace over the internet, so they keep working even while your computer is asleep.[13]
Since the organizer folder only exists on your computer, this guide does not use the cloud. If your company works with GitHub (a service where you keep files online and manage their change history together), just remember that you can send long-running tasks to the cloud and turn off your computer.
There are conditions for using the cloud.
- You must have a cloud workspace prepared in advance, that is, a published environment.[14]
- To set up that workspace, you choose and connect a GitHub repository.[15]
- Your computer's local files, running programs, and browser sign-ins do not transfer to the cloud.[16]
Quick check
Which statement about Codex cloud tasks is correct?
Continuing from Your Phone
From your phone, you can check progress, approve actions, and send instructions. The actual work runs in the cloud or on your connected computer.[17] To connect your computer, go to Settings → Connections → Control this Mac or PC in the app and click Set up.[18]
You connect by scanning a QR code. The official docs tell you to connect only devices you own and trust.[19] That is because a connected phone can control Codex on your computer.
The official docs explain this based on the iOS app. Features roll out to accounts gradually, so you might not see it on your phone yet.[20]
Quick check
When connecting your phone to control Codex on your computer, what do the official docs emphasize?
Try It Yourself
- Open Scheduled in the sidebar (you do not need to create a task).
- Run
$weekly-reviewfrom Chapter 5 one more time in a regular chat and check the result. - If you do create a scheduled task, make sure the work stays inside the folder, and check the first run's result against the original files.
Up next: In Chapter 7, you will check the same organizer tool from the terminal using a single codex exec line.
Summary
- You create scheduled tasks through chat and view them in Scheduled. You can call a
$skillinside a scheduled task. - A scheduled task that uses your local folder needs your computer on and the app running.
- Scheduled tasks run without a person watching and use your default permissions. Full access is risky.
- Cloud tasks require a GitHub repository and a published environment. Your local files do not transfer.
- Your phone controls your computer or the cloud. Connect only devices you trust.
Glossary
| Term | One-line meaning |
|---|---|
| Scheduled | Where you view scheduled tasks and their run history |
| Published environment | A ready workspace where cloud tasks start |
| Unattended | Running without a person watching |
Finished this chapter?
Progress is saved only in this browser. See your progress on the full table of contents.
Next chapter: Chapter 7. Using It in the Terminal
References (20)
Codex official docs, "Scheduled tasks". "Schedule recurring tasks to run in the background." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Scheduled tasks". "Find all scheduled tasks and their runs on Scheduled in the ChatGPT desktop app sidebar." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Scheduled tasks". "You can create and update scheduled tasks from a ChatGPT or Codex chat." learn.chatgpt.com (checked on 2026-11-01) ↩︎
The terminal (Codex CLI) does not have a screen to manage scheduled tasks. Codex official docs, "Scheduled tasks". "Codex CLI doesn't provide the Scheduled management interface." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Scheduled tasks". "In the ChatGPT desktop app, you can explicitly trigger a skill in a scheduled task prompt by using
$skill-name." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Scheduled tasks". "Keep the computer on and the app running when a scheduled task needs local files." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Settings". "On macOS and Linux, turn on Prevent sleep while running so local chats can continue while you step away." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Scheduled tasks". "Scheduled tasks run unattended with your default sandbox settings." / "Scheduled tasks use
approval_policy = "never"when your organization policy allows it." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Scheduled tasks". "If your sandbox mode is read-only, tool calls fail if they require modifying files, accessing network, or working with apps on your computer." / "If your sandbox mode is full access, background scheduled tasks carry elevated risk, as ChatGPT may change files, run commands, and access network without asking." learn.chatgpt.com (checked on 2026-11-01) ↩︎
"Read-only" is a setting that might not appear separately in the permission menu from Chapter 4 (this guide's summary). ↩︎
Codex official docs, "Permissions". "For most work, start with Ask for approval. It lets ChatGPT work within the current workspace and pauses before reaching beyond that boundary." / "Changing who reviews a request doesn't expand the sandbox." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Scheduled tasks". "Before you schedule a task, test the prompt manually in a regular chat first." / "When you start scheduling runs, review the first few outputs and adjust the prompt or cadence as needed." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex Cloud". "Each task has its own workspace and can keep working while your computer is asleep." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex environments". "A cloud task requires a published environment you can access." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex Cloud". "Choose your GitHub repositories and select Get started. Connect GitHub if prompted." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex environments". "Your computer's local files, running processes, browser sign-ins, and VPN access aren't automatically transferred to it." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex on mobile". "Follow progress, approve actions, and send instructions from your phone. Codex runs tasks in the cloud or on a connected computer." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex on mobile". "Go to Settings > Connections > Control this Mac or PC and select Set up or Add." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex on mobile". "Only connect devices you own and trust." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Codex on mobile". "Use the ChatGPT mobile app with Cloud or a connected Mac or Windows PC. Availability depends on rollout and your workspace settings." learn.chatgpt.com (checked on 2026-11-01) ↩︎