OpenAI Codex can now record a Mac workflow and turn it into a reusable skill

OpenAI has added Record & Replay to Codex, a new macOS feature that lets you show Codex a workflow once and turn it into a reusable skill. This matters now because it moves Codex beyond code edits and chat prompts into repeatable desktop work: the kind of tedious internal process that normally lives in a checklist, a screen recording, or one person’s muscle memory.

What OpenAI launched

Record & Replay is documented in OpenAI’s Codex developer docs as a way to demonstrate a workflow on a Mac, then have Codex package the pattern into a skill you can run again.

OpenAI’s examples are not limited to software development. The docs mention workflows such as filing an expense, booking a parking space, creating a correctly configured issue, publishing a video, or downloading a recurring report.

The important details:

It is available on macOS.
Initial availability excludes the European Economic Area, the United Kingdom, and Switzerland.
Computer Use must be available and enabled.
Users start from the Codex app’s Plugins area, choose Record a skill, approve recording, perform the workflow, then stop the recording.
During recording, Codex observes the actions and window content needed to learn the workflow.
Codex can then package the workflow into a reusable skill that may use Computer Use, browser actions, connected plugins, or a mix of those tools.

Third-party coverage today framed the feature as Codex being able to “watch you work once and repeat the task forever.” That is a fair shorthand, but the official docs are more precise: this is about turning a demonstrated workflow into a reusable skill, not unconstrained background automation.

Why builders should care

For founders and engineering teams, this is a bigger deal than another autocomplete upgrade.

A lot of operational work is too company-specific for generic SaaS automation, but too repetitive to keep doing by hand: triaging issues, filling internal forms, publishing release assets, pulling reports, checking dashboards, updating vendor portals, and moving information between tools that do not have clean APIs.

Record & Replay gives Codex a path into that messy middle. Instead of writing a brittle script for every internal process, a team may be able to demonstrate the workflow once, let Codex build the skill, and then refine it over time.

The near-term opportunity is not “replace every ops role.” It is narrower and more practical:

capture repetitive internal workflows before they disappear into one employee’s habits;
turn common founder/admin tasks into reusable agent skills;
reduce the cost of automating processes that cross browser tabs, desktop apps, and private tools;
make Codex useful to non-engineering teammates who can demonstrate a task more easily than they can describe an API integration.

What to test before relying on it

This is also the kind of feature that needs careful rollout.

If Codex is observing window content and actions, teams should decide which apps, accounts, customer records, and internal tools are safe to include in a recording. Sensitive workflows should be tested in sandbox accounts first. Anything involving payments, production data, customer exports, or irreversible admin actions needs human approval gates until the skill has proved reliable.

Builders should also expect some brittleness. Recorded UI workflows can break when a vendor changes a layout, when an account has different permissions, or when a one-off modal appears. The useful question is not whether Record & Replay is perfect on day one. It is whether it can reduce enough repetitive work to justify a controlled library of Codex skills.

The practical takeaway

If your team already uses Codex on macOS, pick one low-risk workflow this week and try turning it into a skill. Good candidates are recurring reporting tasks, issue creation templates, release checklists, or internal admin flows where the cost of a mistake is low and the time savings are obvious.

Do not start with finance approvals, customer-impacting changes, or production operations. Start with boring workflows that someone currently repeats every week.