OpenAI Codex ships stable Goal Mode, Appshots, and post-lock Computer Use

OpenAI shipped three notable Codex updates around May 22, 2026, per the official Codex changelog. Taken together, they push Codex meaningfully further into long-horizon, low-supervision agentic territory: Goal Mode is now stable, Appshots brings one-keystroke screen context injection to macOS, and Codex can keep running Computer Use tasks after your Mac screen locks.

Goal Mode exits experimental and goes stable. Goal Mode — OpenAI's long-horizon objective-setting mode for Codex — has graduated from experimental to generally available across the Codex app, VS Code and JetBrains extensions, and CLI (version 0.128.0 or later required). In Goal Mode, instead of issuing one instruction and waiting for a single output, you assign Codex an objective: a defined outcome, success criteria, and a scope of work. Codex then drives toward that objective autonomously across session breaks, token budget resets, and task interruptions, without requiring you to prompt it forward at each step. The company says this enables hours- or days-long autonomous coding runs. The "stable" designation means the feature is no longer marked experimental and can be treated as production-ready in supported environments — a meaningful threshold for teams evaluating whether to rely on it for production-track work.

Appshots: inject your screen into Codex with a double-tap. Appshots is a new macOS-only shortcut that injects the frontmost window directly into your active Codex thread. Press both Command keys at once — Codex captures a screenshot of the frontmost app and pulls any accessible text the app exposes, including content outside the visible scroll area, and attaches it to the current thread as context. The practical use case: share what you are actually looking at — a browser tab showing an error, a design file, a build log, a document — without manually screenshotting, cropping, and pasting. Appshots is macOS-only at launch; Windows and Linux availability has not been announced.

Post-lock Computer Use. Codex can now continue executing Computer Use tasks after your Mac screen locks. If you set a long-running Computer Use task and need to step away, Codex no longer stops when the screen locks. Combined with Codex Mobile — the iOS and Android app that can trigger and monitor Codex sessions remotely — you can start a task at your desk, lock your Mac, and track progress or redirect the task from your phone.

What is not changing. These are feature additions, not model upgrades. The underlying Codex model and its capabilities are unchanged by this update. Goal Mode's ability to complete a complex multi-day task still depends on the scope of the objective you set, the quality of your task definition, and the specifics of your codebase. Appshots requires macOS and frontmost-window accessibility. Post-lock Computer Use requires the same Computer Use setup as before — it does not unlock Computer Use for accounts or environments where it was not already configured.

Who it matters for. The biggest immediate beneficiaries are developers who currently run long or complex Codex sessions and have to actively babysit them — checking in, unblocking stuck steps, re-prompting when context runs thin. Goal Mode stable and post-lock Computer Use together remove most of that overhead. Appshots is narrower in impact: it removes a copy-paste friction point on macOS, which matters most if you frequently need to share screen state with an AI coding assistant mid-session. See our best AI coding tools roundup for how Codex compares to Cursor and Claude Code on agentic and long-horizon features, and our Cursor vs Claude Code comparison for the current head-to-head at the interface layer.