OpenAI's "Codex Thursday" dropped five updates at once, and the headline is a shift in how you think about AI-assisted coding. Goal mode is no longer an experimental feature and is available in the Codex app, IDE extension, and CLI. Paired with a new screen-capture shortcut called Appshots and the ability to keep working after your Mac locks, this release is less about making Codex smarter and more about making it autonomous enough to work while you're not watching.
From prompts to objectives
The old model for using Codex was transactional: send a message, wait for a result, send another. Goal mode changes that. Instead of sending Codex one instruction and waiting, you assign an objective and let it run across session breaks, token budget resets, and interruptions. With Goal mode, you can have Codex drive toward a specific objective for hours or even days.
The key mechanic is that the goal text acts as both the starting prompt and the completion criteria. Codex uses it to decide what to do next and whether the task is complete. You start Goal mode with /goal in the Codex app, IDE extension, or CLI. In the app, progress appears above the composer with controls to pause, resume, edit, or clear the goal.
Writing a good goal is the skill to develop here. Vague objectives produce vague results. The official docs suggest goals that include a specific outcome, measurable target, or test criteria. For example:
/goal Migrate this codebase from JavaScript to TypeScript.
# The app should compile in strict mode without explicit `any` type definitions.
/goal Reduce the time to interactive of the home page to below 1 second.
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves