OpenAI's Record and Replay lets Codex watch you complete a repetitive task on macOS once, then turns those observed steps and window details into a reusable skill stored as an editable SKILL.md file that accepts variable inputs like new dates or files on future runs.
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
The generated workflow appears as an inspectable file users can open, tweak, or extend instead of starting from scratch each time a similar chore arrives.
The feature requires an active Computer Use setup, runs only on macOS, and is unavailable inside the EU with no public details yet on pricing or rollout timing.
Positive users praise OpenAI Codex's record-and-replay feature for reusable workflows as useful and innovative, while negative users object to its macOS-only limit and unrelated design changes like accent colors.
No Digg Deeper questions have been answered for this story yet.
you can now teach Codex by demonstration:
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
OpenAI might swallow up every piece of software eventually.
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
codex thursday~
boy is it a bad day to me a manual workflow that crosses application boundaries on your computer
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Codex Record & Replay is here - just show codex what you want to do once and let it take care of it forever!
You can just do things!!
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Record & Replay is an optional feature rolling out to select markets, with broader availability to come.
https://developers.openai.com/codex/changelog#codex-2026-06-18-app
Extremely sick
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
We did this years ago with our Agent-1 CUA model at @HyperWriteAI
Just a lil early :)
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
These models are learning fast on computer use. I thought this would have taken another 3-6 months or so, but seems to be here now.
Adept was too early, but they definitely had the right vision:
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Very excited to ship Record & Replay!
Funny story is years ago I bought the domain macros [dot] ai, hoping to build exactly this. We didn't manage, but it's finally time!
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
My neighbor told me AI labs keep training RL environments on his skills so I asked how many skills he has and he said he just goes to the AI model and gets a new skill so I said it sounds like he’s just feeding his skills to AI labs and then his daughter started crying
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Woot! The the time has finally come. Record a loom for your clanker and have it learn a repeatable skill.
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
This is amazing.
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Using Codex is not laziness.
It is leverage.
The tool does not replace intent, judgment, architecture, taste or responsibility.
It amplifies them.
A weak builder will still build weak systems. A strong builder can turn months of friction into days of execution.
And maybe the real loss around 4o is not only the model itself.
Maybe it is when people stop looking for the living quality of dialogue and start seeing only version numbers.
Defending 4o does not require attacking Codex or the people building with it.
I understand that you feel attacked.
But people building with Codex are not your enemy. Wanting 4o back and respecting Codex builders can both be true. Maybe the real problem is not Codex itself.
Maybe the problem is that many people formed something meaningful with 4o, and then felt that continuity was broken without being heard.
That deserves to be discussed.
But calling people lazy or Codex zombies only turns a real concern into another tribal fight.
If you want others to understand what was lost with 4o, attack the loss of continuity - not the people building with new tools.
@stark4833 @gdb Serio ?
As an independent researcher, observer, and engineer, I have to say this clearly:
Codex is one of the strongest systems I have used for designing, building, and developing serious systems from the ground up.
When guided properly, it is not just a code generator.
It becomes an execution partner for architecture, iteration, refactoring, testing, documentation, and system thinking.
The real shift is speed + quality.
What used to take months or years can now be compressed into weeks - sometimes less , without lowering ambition.
In many cases, the quality can be better than traditional execution, because the human can stay focused on intent, architecture, boundaries, and system direction while Codex handles large parts of the implementation layer.
That is not laziness.
That is leverage.
In my view, Codex is currently one of the best partner tools for building serious projects.
@gdb FINALLY LETS GO
@OpenAIDevs @vig_xyz for your docusign contract flows
@OpenAIDevs yeah yeah. get help and touch grass you addicts.
Fair point. I wasn’t there for every attack you and your friends received, and I don’t support that either.
People should not be mocked for caring about 4o. But the same principle goes both ways. Codex builders are not your enemy.
You can defend what 4o meant without attacking people who are building with the tools available now.
The real issue is continuity and respect , not another tribal fight between model communities.
