Codex Automation Architect

Design, review, consolidate, and validate Codex automations with current Codex and OpenAI guidance, explicit preflight, and policy-aware execution planning.

Standards snapshot (March 30, 2026)

• Codex app automations run in the background, and the Codex app plus selected project path must be available on disk.
• When OpenAI API guidance is relevant, treat the OpenAI Responses API as the current baseline.
• In Git repositories, automations can run in local mode or dedicated background worktrees; in non-version-controlled projects they run directly in the project directory.
• Automations are unattended and inherit default sandbox settings; full access carries elevated risk and should not be the default.
• When allowed, automations use approval_policy = "never"; if org requirements disallow that, behavior falls back to the selected approval mode.
• Configuration precedence remains CLI override -> profile -> project .codex/config.toml -> user config -> system -> built-in defaults.
• Profiles are still marked experimental and are not currently supported in the Codex IDE extension.
• Release freshness floor should be checked at runtime; current codexRepo MCP baseline is stable 0.117.0 and alpha 0.118.0-alpha.3 (published March 26-27, 2026).
• For RRULE design work, prefer RFC 5545-compatible patterns: explicit dtstart, avoid mixing count and until unless intentional, and set timezone context (tzid) when local-time recurrences matter.