codex-goal-loop

Automating complex software migration with Codex involves a persistent goal loop that follows a structured Plan, Act, Test, Review, and Iterate process. This continuously executes and verifies the task until a specific stop condition is met.

A persistent goal loop for task execution is an automated agent cycle that continuously processes a task through planning, acting, testing, and reviewing. It iterates until a defined stop condition is achieved, ensuring continuous verification.

Yes, using the persistent goal loop requires Codex CLI, app, or extension version 0.128.0 or higher. You must also explicitly enable the goals feature in your config.toml file to run automated tasks.

Handling refactors with contract tests using Codex is best achieved through a persistent goal loop. This approach provides continuous verification and iteration, executing structured checkpoints until your test suite passes without warnings.

You should stop an automated Codex task loop when your full test suite passes with zero deprecation warnings, or when a specific change requires architecture decisions. You define these stop conditions in your initial goal prompt.