Suppose a customer says your booking page is confusing. You have their message, the live page and an approved design reference. With the necessary tools and access, Codex can compare those sources, investigate the problem and prepare a proposed change for review.
Start by defining the job: what should the agent check, what may it change, and what should it return? The examples below follow that process in Codex and related desktop features, from the first source material to a reviewed file or page. They also show how to reuse a procedure and follow up when the work changes.
- INPUTBring the evidenceUse the actual page, approved files and relevant records.
- WORKSTREAMKeep the work togetherCarry decisions and source context into the next step.
- OUTPUT → REVIEWReturn something usefulInspect the result before the agreed external action.
A useful handoff includes the result, its evidence and what still needs your decision.
Give ongoing work a home
A workstream is an ongoing responsibility, such as website improvements, customer feedback or operations. Keep related requests in a task conversation you can return to, along with the problems discussed, approved changes and evidence for the next step. Use a project when several tasks depend on the same files or sources.
Pin tasks you revisit and name them for their responsibility, such as Website Improvements or Customer Feedback. Pinning keeps them easy to find in the sidebar; it does not create continuity on its own. That comes from returning to the relevant conversation and maintaining useful project records. Projects and chats
Keep detailed context in its own workstream. Bring back only what needs attention.
Keep working rules, next actions and source-linked notes where someone can inspect them. For a file-based project, that could be an instructions file and a short action list. If your team already uses a project tracker, maintain its existing records rather than creating another list to keep in sync.
Long conversations can continue through compaction, which summarizes older context. Details can be lost in a summary, so ask the agent to save important decisions, blockers and the next check in the appropriate project record when that write is authorized. Long-running work, Compaction glossary
Talk through the messy input
You do not need a polished specification to begin. With dictation, describe what you noticed, where it happened and what you suspect, then edit the transcription before sending it. Live Voice supports an ongoing conversation and task coordination where available; dictation produces prompt text. Dictation, Voice
For the booking-page example, share the customer's wording and the page. Ask the agent to test your explanation against those sources before proposing a fix.
Example prompt
Review this customer feedback and our service page. Identify where the booking process is unclear. Separate what the customer reported from your own findings. Prepare a proposed wording change and an issue draft with source links. Keep both here for review; do not reply to the customer or update the live page.
The prompt separates the customer's report from the agent's findings and keeps both proposed outputs in review. Add a correction or another source in the same conversation while it works.
Show the actual source
Choose source material that answers a specific question. An approved proposal establishes scope, a spreadsheet supplies the numbers, and a screenshot shows the layout you mean. Say which source to trust when they disagree.
On supported macOS setups, Appshots capture the frontmost app window and available text, which can include text outside the visible area. Review sensitive content before sharing. Browser tools can inspect a page directly, but the desktop built-in browser uses a separate profile and does not automatically share your regular browser's signed-in session. Appshots, Browser
Example prompt
Open this page in the built-in browser and compare it with the approved design reference. Check spacing, readability, and the request-a-quote path. Prepare a short issue list with screenshots and suggested changes. Do not submit the form or change the site.
A plugin with an authorized connection can bring in records from the system where the work lives. For a weekly project brief, that might mean permitted messages, calendar entries and task records. Name the project and time range to keep the brief focused.
Meeting notes can reveal what changed across recent project discussions. Ask for decisions, owners, dates and open questions linked to their sources, and leave a missing owner unassigned until someone resolves it. The brief should make clear what changed and which action follows.
Make a useful procedure repeatable
Memory, skills and plugins serve different roles. When enabled, memory can carry useful context forward from earlier work. A skill packages instructions, references and optional scripts for a repeatable job. A plugin is an installable package that can include skills, connections to external tools, or both. Memories, Skills, Plugins
Memory
What is useful to recall?
“Keep reports short. Put unresolved decisions first.”
Skill
How should the job run?
Check sources, flag missing evidence, format the review.
Plugin
What can support the job?
Reusable skills, tool connections, or both.
Each has a different role. Keep required rules in explicit instructions or project records.
Consider a weekly account review. Memory might recall a reporting preference, while the skill defines which sources to compare and how to flag missing evidence. A plugin that includes the needed connection can provide access once authorized. Keep required rules in explicit instructions or project documentation so they do not depend on memory recall.
Run the review once with human oversight to identify its judgment calls. Then document the repeatable steps, including how to handle conflicting sources, missing data and actions requiring approval.
Example prompt
Turn this approved weekly-review process into reusable instructions. List its inputs, source checks, output format, and approval points. Include how to handle missing or conflicting evidence. Draft the instructions for review before creating or installing anything.
Once the procedure works, consider packaging it as a plugin if other people need to install its skills or supported connections.
Keep the follow-up loop running
A supplier response may arrive tomorrow, or a launch checklist may change after today's review. For follow-ups that need the same context, schedule the check inside the existing conversation. A standalone scheduled task starts from its saved prompt instead. Scheduled tasks
Specify what to check, how often to check it, what the agent may do, when to notify you and when to stop. Without those boundaries, repeated summaries can become another thing to review.
- MONStartRecord the baselineSave the starting state of the approved tracker.
- TUEQuietNo meaningful changeKeep a record of the check; no notification needed.
- WEDNotifyA new blocker appearsBring back the decision that needs attention.
- THUUpdateRecord the resolutionKeep the update with the project context.
- FRIStopThe agreed final checkFinish the scheduled loop after this run.
Schedule the checks, report meaningful changes and stop after the agreed final run.
Example prompt
Each weekday at 9 a.m. Eastern through this Friday, check the approved launch tracker for this project. Report new blockers, changed owners, or missed dates since the previous check. Keep a record of the check. Stay quiet when nothing meaningful changes. Draft any follow-up messages for review and ask before sending. Confirm the final run date with me before scheduling, then stop after that run.
Test the instructions before scheduling them and review the first few runs. A local scheduled task needs the computer on, the app running and its project files available. Confirm the notification settings as well so you know where to look when a check needs your attention. Notifications
Coordinate focused tasks
Split a larger job when its parts can be reviewed independently. For a website refresh, one task might inventory broken links while another checks copy against approved wording. A coordinating task gathers their findings, resolves overlaps and prepares one review.
Each worker returns a bounded result. The coordinator owns the final handoff.
Give each task a defined output and the sources it needs. Avoid assigning two tasks to edit the same material simultaneously. Where supported, Voice can start separate tasks, check their progress and send follow-up instructions. Voice coordination
Example prompt
Coordinate two independent reviews of this website project: broken links and copy consistency. Give each task the approved source material and a read-only scope. Combine their findings, remove duplicates, and return one prioritized review with evidence. Do not change the website or create external assignments.
Remote access lets you check and direct work from another supported device. The host, meaning the computer running the work, supplies the files, tools, credentials and permissions. Technical projects can also use a configured SSH connection to a remote development machine. Your phone sends instructions; the host still needs to be awake, connected and able to access the required systems. Remote connections
Finish with something people can use
Ask for the file or page the next person needs. A budget comparison calls for an inspectable spreadsheet; a presentation needs editable slides and a preview. For a website change, request a way to review its appearance and behavior. Specify where to save the result and which checks it should pass. Artifacts
Example prompt
Prepare a workshop resource hub from these approved materials. Include the agenda, resource links, and a participant checklist. Save a reviewable version with editable source, check every link, and list any missing content. Do not deploy or share it until I approve the finished version.
Sites can build and host websites. For a review step before anything goes live, ask it to save a version without deploying. Every Sites deployment URL is a production deployment, even when access is restricted, so approve the content and intended audience before deployment. Sites
When a direct tool connection cannot do the job, Computer Use may be able to operate an allowed app visually. It still needs the required app access and permissions. Ask it to preserve editable originals and show you the result for review. Computer Use
After reviewing the first draft, return specific feedback to the same conversation and record what remains. Agree on what counts as finished so the next pass has a clear endpoint.
Check your available features
OpenAI's documentation calls the desktop product the ChatGPT desktop app, which includes Codex and ChatGPT Work. Features differ between the desktop app, web, mobile, command line and editor extension, as well as by plan, operating system, rollout and workspace settings. Appshots are documented for macOS; Windows Computer Use takes over the foreground and needs an unlocked, available session. Local Codex memory is separate from ChatGPT web memory. Check your setup before depending on a feature.
Bring one recurring task and a sample of its input to Om Concepts. We can scope a first version with a specific output, a review step and a way to check whether it works. You can also email alex@omconcepts.net.
Sources and credit
This original Om Concepts guide is informed by the Codexmaxxing source deck credited to Jason Liu / OpenAI. The explanations, examples and diagrams are our own. It is not authored or endorsed by OpenAI. Product documentation linked throughout was checked September 11, 2026.
The header image is original AI-generated editorial artwork. It illustrates the workflow and does not depict a real product screen or client result.
