Codex can now work more persistently towards your goals,

whether it's for hours or even days.

The goal functionality is now available in the Codex app,

IDE extension, and the CLI.

With it, you can specify a concrete goal to achieve,

and Codex will continue to work until that goal has been met.

Let me show you how it works.

Start by typing /goal in your message composer to enable the goal mode.

From there, we can define our goal for Codex.

This will act as both the original message to have Codex start the task and as

instructions to have it determine if the task has been completed.

The best goals are those where it is clear whether Codex has actually achieved

the goal or not. For example, by specifying a measurable target or having

clear test criteria that have to pass.

If you struggle writing the goal yourself,

you can ask Codex to help. Either by using Plan Mode first before using the

resulting plan as your implementation goal,

or by just asking Codex to interview you before crafting the goal and then

having it set the goal itself.

Once Codex is up and running, you can continue to use steering to send

additional messages, for example, to have Codex correct course.

You can also start side chats to understand the work done so far

without having to interrupt the main task.

Because Codex might take hours or even days,

you can also pause and resume your goal later on.

This is helpful, for example, when you're about to head out of the office and

your laptop is about to lose internet connection.

Once you're ready to continue, you can resume the goal or even edit it if your

goal has changed or if you want to give Codex more concrete guidance.

Using goals in Codex is incredibly powerful.

We've seen many people have Codex make progress on complicated tasks for

upwards of 100 hours on a single goal.

So give it a try.