Codex App Automations (Scheduled Agent Runs)
Codex's native answer to scheduled agent loops: define a prompt plus a schedule in the Codex app and it runs in the cloud on cadence — nightly dependency audits, morning issue triage — with no terminal open. The Codex-side equivalent of Claude Code Routines.
Implementation note
When to use: recurring agent work on the Codex side of the fence — nightly dependency audits, morning triage of new issues — where you want cloud execution on a schedule with no terminal open. It is the Codex-side equivalent of Claude Code Routines. How it works: define an Automation in the Codex app: a prompt plus a schedule. The automation then runs in the cloud on that cadence — your machine can be off entirely. Note this is a Codex-app pattern, not a Claude slash command; it is filed in this directory as a harness pattern. Safety: cloud-scheduled agents run unattended by definition, so the discipline lives in the prompt: give automations report-shaped work (audit, triage, summarize) before mutation-shaped work, and make any write action land as a reviewable artifact — a PR or an issue — rather than a direct change. Review the first few scheduled outputs before extending its scope.
Source: OpenAI (Codex app docs) ↗
More automation loops
Run workflows with dynamic sub-agents
Split a task into packets, run sub-agents in parallel, synthesize results, and verify completion.
Run agent turns until goal met
Agent executes repeated turns toward a condition, with a lightweight evaluator checking progress after each turn until the goal is reached.
Run agent until goal met
Queue agent turns with goal context until your objective is achieved, treating the goal as untrusted data.