← 전체 글로 돌아가기

이 글은 아직 한국어로 제공되지 않아 영어 버전을 보여 드립니다.

How do I schedule Claude Code or Codex runs?

4분 분량작성: The Octuo team
Screenshot of Octuo for macOS showing scheduled routines

Choose by where the run has to happen. Claude Code has cloud routines, desktop scheduled tasks and in-session loops; Codex has scheduled tasks in its desktop app, plus codex exec for scripts you schedule yourself. Claude Code's docs say cloud routines keep working with your laptop closed. Every local option needs your computer on.

Which options need my computer on?

Claude Code, per its docs:

  • Cloud routines run on cloud infrastructure, from a schedule, an API call or a repository event. They start from a fresh clone, not your local files, and the shortest interval is one hour. The docs call them a research preview.
  • Desktop scheduled tasks run on your machine with access to local files, but "only fires while the app is open and your computer is awake."
  • In-session loops need an open session, and recurring ones expire after seven days.

Codex, per its docs:

  • Desktop-app scheduled tasks need the computer on and the app running when they use local files.
  • Browser-created tasks cannot work directly in a folder on your computer.
  • codex exec runs from scripts and CI. By default it uses a read-only sandbox and requires a Git repository. claude -p plays the same role for Claude Code.

Which one should I pick?

  • Must run while you are away, work lives in a repository: a cloud routine.
  • Needs local files or tools: a desktop task, with the computer on.
  • Quick polling while you work: an in-session loop.
  • Part of a pipeline: claude -p or codex exec, started by a scheduler you trust, such as cron or launchd.

How do I keep an unattended run on a leash?

  • Write a self-contained prompt. The routines docs say it must be explicit about what to do and what success looks like. State the goal, a "done" line and where results land.
  • Give it the narrowest access that works. Codex scheduled tasks run unattended with your default sandbox settings. Claude Code routines include all your connectors by default and can use their tools, including writes, without asking, so remove the ones you do not need.
  • Run it once by hand, then review the first few runs before you trust the schedule.
  • Do not trust a green status. The docs say it only means the session started and exited without an infrastructure error. Open the run.

How will I know it ran?

Ask for a result every run, even "nothing to report," with the run time and a count on top; see silence is not success. Time the job backwards from when you will read it: schedule a recurring job backwards.

Where Octuo fits

Octuo is a personal assistant that coordinates your AI tools, agents and outside services for you: you say the goal, and it handles the preparation, delegation and follow-up. Octuo supports scheduled routines, and both you and Octuo can add and modify them. Schedules and condition watches run on their own and notify only when something changes.

Give Octuo a goal. It delegates work to supported tools and agents, such as Claude Code and Codex (examples only; no partnership or endorsement), carries the context they need and brings the results back. Octuo follows the work and reports back. Progress is there whenever you want to check; decisions that need you come to Attention. You step in for your own account sign-ins, payments and sensitive approvals that must be yours; Octuo handles the surrounding work.

Octuo is a native Mac app and needs an internet connection. See what Octuo does. New accounts get 1,000 OC trial credits, once per person, no card. OC stands for Octuo Credits.

FAQ

Can I schedule Claude Code to run when my laptop is closed? Its docs say cloud routines keep working with the laptop closed. They use a fresh clone, not local files, and are a research preview, so re-check the details.

How long does an in-session loop last? Recurring in-session tasks expire after seven days and fire only while the session is running. For longer, the docs point to routines or desktop tasks.

Will a scheduled run ask before it edits files? Possibly nobody is there to answer. Codex tasks run unattended with default sandbox settings, and cloud routines run autonomously with no permission-mode picker.

Sources

The product names above belong to their owners. We have no affiliation with them.