Recently I had a package stolen. Amazon told me it would take about 25 minutes to connect me to a person, so I gave the thread Computer Use and told it to check every five minutes. Once someone joined, check every minute and do its best to get me a refund.
\nI went to take a shower. When I came back, the refund was done.
\nThat was when Computer Use clicked for me. Codex is not just a coding agent. Most of my work is messages, forms, browser tabs, and apps that do not connect neatly to anything else.
\nCodex now has three ways to work there:
\n| Use | \nBest for | \nStart with | \n
|---|---|---|
| Computer Use | \nNative apps and work across apps | \n@Computer, @AppName, an Appshot, or Remote Control | \n
| Chrome | \nSigned-in sites and multiple tabs | \n@Chrome | \n
| In-app browser | \nPages, artifacts, and visual review | \n@Browser | \n
My rule is to use the narrowest tool that can finish the job. If a plugin works, use it. If the task needs a screen, choose among these three.
\nComputer Use is the most powerful option and usually the slowest. It can operate Spotify, finance apps, System Settings, or iPhone Mirroring. But it has to look at the screen, click, wait, and look again.
\nOn a Mac, it can work in the background while you keep using your computer. On Windows, it takes over the active desktop.
\nInstall it from Settings > Computer Use. On macOS, grant Screen Recording and Accessibility permissions. Then mention @Computer, mention an app directly with @AppName, or just ask Codex to use Computer Use.
The stolen-package example also shows the difference between a Goal and a thread automation. The Goal was to get the refund. The automation woke the thread every five minutes, then every minute when the agent appeared. One supplied the finish line; the other let Codex wait without forgetting the job.
\nI asked people for the most ambitious things they had done with Computer Use. Someone applied for a Schengen visa. Someone else paid monthly Airbnb taxes through a county website. One person repaired a virus-filled PC through a reboot loop. Another used iPhone Mirroring for iOS Screen Time. I immediately wondered whether the same setup could operate a dating app.
\nI have also used Computer Use as the last mile when another tool stopped short. One thread read feedback from Slack, changed a video, and rendered a new version. The Slack integration could not upload files, so Computer Use clicked Add file and posted it.
\nAn Appshot sends the frontmost Mac window to a Codex thread. Press both Command keys, then say what you want.
\nI use this for emails, Slack messages, errors, designs, settings panels, and forms. Sometimes the Appshot is enough. If Codex needs to act, I tell the same thread to continue with Computer Use.
\nAppshots are how I point. Computer Use is how Codex acts.
\nRemote Control lets me start or steer the same work from my phone. In the Codex app, click Set up Codex mobile, scan the QR code, and connect ChatGPT mobile. The host stays awake and online; the work still runs there with its projects, plugins, Chrome setup, and Computer Use permissions.
\nThomas Ricouard has been pushing this part of Codex forward. He started with Codex Monitor, where every active and past session was visible so you could jump back into the work. Codex Mobile now has notifications when work finishes and better reconnection, followed by /side conversations. Remote Control is becoming less like a status screen and more like Codex in your pocket.
I let Computer Use research and draft. I stay present for payments, credentials, account changes, and security settings. Follow Ari Weinstein for Computer Use and Appshots, and Thomas for Codex Mobile and Remote Control.
\nUse the Chrome extension when Codex needs your Chrome profile, cookies, extensions, or an authenticated site. It can control several tabs in a thread and keep working in its tab group while you use Chrome elsewhere.
\nOpen Plugins, add Chrome, and install the Codex Chrome extension. Once it says Connected, mention @Chrome.
In one thread, I gave Codex an open Strudel Composer tab and told it to make the music more interesting. It rewrote the harmony and arrangement, changed the tempo, saved the track, and left it playing.
\nI also keep a Twitter thread that uses Chrome to check DMs, read news, and collect product feedback. It writes anything durable to my vault but does not post or send messages.
\nThat is my default boundary for Chrome: research and draft freely; ask before sending, publishing, purchasing, or submitting.
\nThe in-app browser lives inside a Codex thread. I use it for public pages and visual artifacts I want to review with Codex. It does not carry your Chrome profile or login state.
\nOpen Plugins, add Browser, and mention @Browser.
The annotation tools are my favorite part. I often ask Codex to create a single index.html, open it in the browser, and wait for comments. Then I can click an element and say “this hierarchy is backwards,” “make this less card-heavy,” or “these controls need more room.” The comment includes the screenshot and element context, so I do not have to describe the whole page again.
The browser can also establish context and hand the job to another tool. I once opened an X post and asked Codex to investigate it. The page showed which post I meant; the Twitter CLI then retrieved 38 replies, including nested replies that were not visible on the page.
\nThe Atlas browser team is working to make the in-app browser more powerful: not just a preview, but a place where you and Codex can work on the same thing together. They are cooking. Follow James Sun to see what they are working on.
\nI do not want to remember this routing every time, so I put it in AGENTS.md:
\n- ------Follow me (@jxnlco) for the ways I am using these tools, Ari Weinstein for Computer Use, Thomas Ricouard for Codex Mobile, James Sun for browser work, Andrew Ambrosino for Codex app updates, and OpenAI Developers for broader news.
\nThe interesting part is not that Codex can click buttons. A thread can start with an Appshot, move across apps and browsers, wait for someone else, and keep working after I leave.
\nIf you want me to go deeper on Goals, thread automations, Appshots, Remote Control, or how I route work between these tools, leave a comment. Tell me what you are trying to do; I will use the best questions for the next post.
\n", "content_markdown": "Recently I had a package stolen. Amazon told me it would take about 25 minutes to connect me to a person, so I gave the thread Computer Use and told it to check every five minutes. Once someone joined, check every minute and do its best to get me a refund.\n\nI went to take a shower. When I came back, the refund was done.\n\nThat was when Computer Use clicked for me. Codex is not just a coding agent. Most of my work is messages, forms, browser tabs, and apps that do not connect neatly to anything else.\n\nCodex now has three ways to work there:\n\n| Use | Best for | Start with |\n| -------------- | ----------------------------------- | ------------------------------------------------------ |\n| Computer Use | Native apps and work across apps | `@Computer`, `@AppName`, an Appshot, or Remote Control |\n| Chrome | Signed-in sites and multiple tabs | `@Chrome` |\n| In-app browser | Pages, artifacts, and visual review | `@Browser` |\n\nMy rule is to use the narrowest tool that can finish the job. If a plugin works, use it. If the task needs a screen, choose among these three.\n\n## 1\\. Computer Use: almost any app\n\n[Computer Use](https://developers.openai.com/codex/app/computer-use) is the most powerful option and usually the slowest. It can operate Spotify, finance apps, System Settings, or iPhone Mirroring. But it has to look at the screen, click, wait, and look again.\n\nOn a Mac, it can work in the background while you keep using your computer. On Windows, it takes over the active desktop.\n\nInstall it from **Settings > Computer Use**. On macOS, grant Screen Recording and Accessibility permissions. Then mention `@Computer`, mention an app directly with `@AppName`, or just ask Codex to use Computer Use.\n\nThe stolen-package example also shows the difference between a Goal and a thread automation. The Goal was to get the refund. The automation woke the thread every five minutes, then every minute when the agent appeared. One supplied the finish line; the other let Codex wait without forgetting the job.\n\n### People are already using it for stranger things\n\nI asked people for [the most ambitious things they had done with Computer Use](https://x.com/jxnlco/status/2066547199983473013). Someone [applied for a Schengen visa](https://x.com/thevedlabs/status/2066577349273874617). Someone else [paid monthly Airbnb taxes through a county website](https://x.com/GabGarrett/status/2066584487161467090). One person [repaired a virus-filled PC through a reboot loop](https://x.com/craigsdennis/status/2066550916158009401). Another used iPhone Mirroring for [iOS Screen Time](https://x.com/ChristianInProd/status/2066682841249796481). I immediately wondered whether the same setup could [operate a dating app](https://x.com/jxnlco/status/2066618356958896428).\n\nI have also used Computer Use as the last mile when another tool stopped short. One thread read feedback from Slack, changed a video, and rendered a new version. The Slack integration could not upload files, so Computer Use clicked **Add file** and posted it.\n\n### Appshots let me point\n\nAn [Appshot](https://developers.openai.com/codex/appshots) sends the frontmost Mac window to a Codex thread. Press both Command keys, then say what you want.\n\nI use this for emails, Slack messages, errors, designs, settings panels, and forms. Sometimes the Appshot is enough. If Codex needs to act, I tell the same thread to continue with Computer Use.\n\nAppshots are how I point. Computer Use is how Codex acts.\n\n### Remote Control lets me leave\n\n[Remote Control](https://developers.openai.com/codex/remote-connections) lets me start or steer the same work from my phone. In the Codex app, click **Set up Codex mobile**, scan the QR code, and connect ChatGPT mobile. The host stays awake and online; the work still runs there with its projects, plugins, Chrome setup, and Computer Use permissions.\n\n[Thomas Ricouard](https://x.com/Dimillian) has been pushing this part of Codex forward. He started with [Codex Monitor](https://x.com/Dimillian/status/2010330190510273016), where every active and past session was visible so you could jump back into the work. Codex Mobile now has [notifications when work finishes and better reconnection](https://x.com/Dimillian/status/2057452433777807486), followed by [`/side` conversations](https://x.com/Dimillian/status/2060215793971786098). Remote Control is becoming less like a status screen and more like Codex in your pocket.\n\nI let Computer Use research and draft. I stay present for payments, credentials, account changes, and security settings. Follow [Ari Weinstein](https://x.com/AriX) for Computer Use and Appshots, and [Thomas](https://x.com/Dimillian) for Codex Mobile and Remote Control.\n\n## 2\\. Chrome: your signed-in browser\n\nUse the [Chrome extension](https://developers.openai.com/codex/app/chrome-extension) when Codex needs your Chrome profile, cookies, extensions, or an authenticated site. It can control several tabs in a thread and keep working in its tab group while you use Chrome elsewhere.\n\nOpen **Plugins**, add **Chrome**, and install the [Codex Chrome extension](https://chromewebstore.google.com/detail/codex/hehggadaopoacecdllhhajmbjkdcmajg). Once it says **Connected**, mention `@Chrome`.\n\n### Make the music more interesting\n\nIn one thread, I gave Codex an open Strudel Composer tab and told it to make the music more interesting. It rewrote the harmony and arrangement, changed the tempo, saved the track, and left it playing.\n\n### A thread that watches Twitter\n\nI also keep a Twitter thread that uses Chrome to check DMs, read news, and collect product feedback. It writes anything durable to my vault but does not post or send messages.\n\nThat is my default boundary for Chrome: research and draft freely; ask before sending, publishing, purchasing, or submitting.\n\n## 3\\. The in-app browser: review and annotate\n\nThe [in-app browser](https://developers.openai.com/codex/app/browser) lives inside a Codex thread. I use it for public pages and visual artifacts I want to review with Codex. It does not carry your Chrome profile or login state.\n\nOpen **Plugins**, add **Browser**, and mention `@Browser`.\n\n### The page becomes the specification\n\nThe annotation tools are my favorite part. I often ask Codex to create a single `index.html`, open it in the browser, and wait for comments. Then I can click an element and say “this hierarchy is backwards,” “make this less card-heavy,” or “these controls need more room.” The comment includes the screenshot and element context, so I do not have to describe the whole page again.\n\n### Hand the work to another tool\n\nThe browser can also establish context and hand the job to another tool. I once opened an X post and asked Codex to investigate it. The page showed which post I meant; the Twitter CLI then retrieved 38 replies, including nested replies that were not visible on the page.\n\nThe Atlas browser team is working to make the in-app browser more powerful: not just a preview, but a place where you and Codex can work on the same thing together. They are cooking. Follow [James Sun](https://x.com/JamesZmSun) to see what they are working on.\n\n## Put the routing rule in AGENTS.md\n\nI do not want to remember this routing every time, so I put it in `AGENTS.md`:\n\n```md\n## Browser and desktop routing\n\n- Prefer a plugin when one can finish the task.\n- Use an Appshot when showing the frontmost Mac window is easier than describing it.\n- Use `@Browser` for public pages, visual review, and annotations.\n- Use `@Chrome` for signed-in sites, existing tabs, extensions, or multiple tabs.\n- Use `@Computer` for native apps or work across apps.\n- Use Remote Control to start or steer work from my phone.\n- Ask before sending, publishing, purchasing, submitting, or changing account settings.\n```\n\n## Follow the work\n\nFollow [me (@jxnlco)](https://x.com/jxnlco) for the ways I am using these tools, [Ari Weinstein](https://x.com/AriX) for Computer Use, [Thomas Ricouard](https://x.com/Dimillian) for Codex Mobile, [James Sun](https://x.com/JamesZmSun) for browser work, [Andrew Ambrosino](https://x.com/ajambrosino) for Codex app updates, and [OpenAI Developers](https://x.com/OpenAIDevs) for broader news.\n\nThe interesting part is not that Codex can click buttons. A thread can start with an Appshot, move across apps and browsers, wait for someone else, and keep working after I leave.\n\n## What should I write about next?\n\nIf you want me to go deeper on Goals, thread automations, Appshots, Remote Control, or how I route work between these tools, leave a comment. Tell me what you are trying to do; I will use the best questions for the next post.\n", "dateCreated": "2026-09-27T19:29:15.293681927+00:00", "date_created": "2026-06-16T00:00:00+00:00", "date_modified": "2026-06-16T00:00:00+00:00", "date_published": "2026-06-16T00:00:00+00:00", "description": "When to use Computer Use, Chrome, or the in-app browser in Codex.", "external_url": "https://jxnl.co/writing/2026/06/16/three-ways-codex-can-use-a-computer/", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/jxnl-co/2026/06/2026-06-16-three-ways-codex-can-use-a-computer.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/jxnl-co/2026/06/2026-06-16-three-ways-codex-can-use-a-computer.md" }, "id": "urn:aggr:item:7a80421703446e961dc2382b30364e77b99976ee", "isBasedOn": { "@id": "https://jxnl.co/writing/2026/06/16/three-ways-codex-can-use-a-computer/" }, "mainEntity": { "@id": "https://jxnl.co/writing/2026/06/16/three-ways-codex-can-use-a-computer/", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/jxnl-co/2026-06-16-three-ways-codex-can-use-a-computer/#webpage" }, "author": [ { "@type": "Person", "name": "Jason Liu" } ], "dateModified": "2026-06-16T00:00:00+00:00", "datePublished": "2026-06-16T00:00:00+00:00", "headline": "Three Ways Codex Can Use a Computer", "timeRequired": "PT6M", "url": "https://jxnl.co/writing/2026/06/16/three-ways-codex-can-use-a-computer/", "wordCount": 1250 }, "name": "Archived snapshot: Three Ways Codex Can Use a Computer", "preview": null, "reading_minutes": 6, "replicated_at": null, "source": "jxnl-co", "source_name": "Jason Liu", "summary": "When to use Computer Use, Chrome, or the in-app browser in Codex.", "tags": [ "applied ai", "codex", "computer use", "personal", "personal software", "workflows" ], "temporalCoverage": "2026-09-27T19:29:15.293681927+00:00", "title": "Three Ways Codex Can Use a Computer", "url": "https://aggr.aymericbeaumet.com/items/jxnl-co/2026-06-16-three-ways-codex-can-use-a-computer/", "word_count": 1250 }