The Rundown

In this guide, you will learn how to use Codex to handle repetitive, click-heavy work on your computer. Instead of manually archiving files, moving through queues, or clicking the same button over and over, you can give Codex a tightly scoped task, let it operate the interface visually, and supervise the first few actions before scaling up.

Who This Is Useful For

• Operators and admins cleaning up repetitive backlogs in web apps
• Creators and production teams moving through repetitive media workflows
• Anyone with a click-heavy process who does not want to build a custom automation for it

This works best when the task is repetitive, the interface is stable, and the right action is visually obvious.

What You Will Build

You will build a repeatable workflow for delegating a manual UI task to Codex.

In the video guide, we tested this on a batch video backup task in Google Drive.

What You Need

• A paid ChatGPT plan with Codex access

Pro tip: Don't start with a messy, high-risk task. Pick something boring and predictable first.

Step 1 Turn On Computer Use

Open Codex settings, find Computer Use, and click Install to install the plugin.

When macOS prompts you, grant:

• Screen Recording, so Codex can see the target app
• Accessibility, so Codex can click, type, and navigate

These system permissions are separate from Codex's app approvals. The system permissions let Codex operate apps at all. The app approvals decide which apps Codex is allowed to touch.

Pro tip: Computer Use is great for the repetitive tasks that keep showing up but do not have a clean API-based workflow in Codex or ChatGPT.

Step 2 New Task

Create a new task and toggle on Full access.

Step 3 Clean Up the Environment Before You Start

Before Codex touches anything, reduce the surface area.

• close sensitive tabs and unrelated apps
• use a dedicated browser profile if possible
• keep only the target app or window visible
• decide the batch size in advance

When the screen is clean and the task is narrow, Codex has less room to misread the situation.

Step 4 Write the Task Prompt Like an SOP

A vague instruction gets vague behavior. A tight operating procedure gets much better results.

Your prompt should include:

• the exact app
• the exact page or view
• the exact button or menu label
• the loop instruction
• the batch size
• what Codex should do when it is unsure

Here is a good example:

The key is to tell it which apps to use, what url to go to and to specify that it uses computer control for the task.

Step 5 Let Codex Do One Item First

Do not launch a giant batch immediately.

Have Codex complete one item first. Watch the screen and confirm three things:

1. it is on the right page
2. it chose the right row or target
3. it clicked the right action

Once that first action is correct, let it continue through the rest of the batch.

This first-item check is the simplest way to catch a misunderstanding before it becomes a mess.

Step 6 Scale to a Small Batch

Once the first action is verified, let Codex continue through a small batch like 5, 10, or 20 items.

That gives you a practical time win without making the session hard to supervise. It also makes troubleshooting easier because you can stop, adjust the prompt, and rerun the next batch if something drifts.

This is a better operating model than telling it to clear an entire backlog with no guardrails.

Going Further

Once one manual workflow is stable, you can turn it into an automation that still uses Computer Use. In this part of the guide, you will learn how to automate these tasks after you have tested them live once.

The workflow from the demo is:

1. create a project for the task
2. run the task manually once inside that project with Full access enabled
3. create an automation from that existing project
4. give it a clear title and restate the job in plain English
5. keep the automation set to Local
6. choose a smaller model if the task is simple and repetitive
7. hit Run now and watch the first few runs closely

Codex remembers the setup from the project you already tested. That makes it easier to automate a known-good workflow than to start from scratch inside the automation builder.

In the video guide, we used a recurring backup task: tell Codex to back up any videos to Safari using computer control, give it the Google Drive link, and let it repeat the same upload behavior we already verified in the live run.

Watch the first couple runs, make sure it is not drifting, and only automate jobs that are deterministic enough to trust. Use it for the boring work that eats time, not for work that needs judgment.