All resources
Guide·8 min read·ChatGPT·Codex

My ChatGPT and Codex Plugin Setup (The Plugins + Copy-Paste Prompts)

You can have ChatGPT work inside your browser and use apps on your computer. This is the setup behind my video, with the plugins to start with and prompts for each workflow.

Start in the desktop app

Open ChatGPT in the desktop app. Choose Work or Codex for the computer workflows below. Open Plugins, find the tool you want, and install or enable it. Finish any connection prompts, then start a new task.

ChatGPT and Codex share a public plugin directory. The same plugin can have different capabilities across devices. For the browser and computer demos, use your desktop. OpenAI's plugin setup covers the supported surfaces.

The setup from the video

Chrome lets the agent work in your connected browser, including tabs where you're already signed in.

Computer Use lets it interact with supported desktop apps.

Browser is the built-in browser for opening pages and checking websites inside the app.

Image generation creates and edits images inside the task. This is a built-in capability, so start by asking for an image.

Install the plugins your task needs. A model choice alone doesn't connect your browser or give it access to your apps.

1. Connect Chrome

Open Settings → Computer use in the desktop app. Select Chrome and follow the setup prompts. Use Install to open the extension listing, then install the ChatGPT extension. Return to settings and check that Chrome shows Manage.

Now start a Work or Codex task. Type @ and select Chrome from the menu. Use the Chrome profile where you installed the extension. Start with a few pages, then increase the batch once the workflow works.

For more examples, use my browser setup guide.

Copy-paste this
Use Chrome to review the pages I have open for this project. Tell me which tabs you can access first. Compare the information on those pages and make a short table with a source link for every finding. Keep my existing tabs open.

2. Give it a batch of browser tasks

Give each page a clear job. A batch of 24 tabs is useful when you know what you want from each one. It isn't a promise that every site will work or that all actions happen at once.

Replace the bracketed part with your own list. Start with research or a review before using a workflow that changes an account.

Copy-paste this
Use Chrome. Open the following pages in separate tabs: [paste my page list]. For each page, record its title, the main claim and one detail relevant to [my goal]. Put the results in a table with clickable sources. Flag anything you couldn't verify. Don't submit forms or change account settings.

3. Turn on Computer Use

Open Plugins → Computer Use and install or enable it. Turn on its server and skill if those controls appear. Use Try now, then review app access in Settings → Computer use.

On Windows, keep the target app visible on the active desktop. On macOS, grant Screen Recording and Accessibility when prompted. Use a task that names the app and the exact result you want.

The game-settings example in my video is a specific setup. For your own computer, have the agent check compatibility and explain the changes before installing anything.

Copy-paste this
Use Computer Use to open Calculator. Calculate 128 times 47, then show me the result in the app.

4. Generate images for your app

Ask for an image in the same task where you're building the app. Give it dimensions and a visual direction. Attach an existing image when you want an edit or a matching style.

Start with one image you like, then use it as the reference for the next batch. Availability and usage limits depend on your account. Don't treat image generation as an unlimited free service.

Copy-paste this
Generate a 1536 by 1024 hero image for my [type of app]. Use [brand colors] and a [visual style] look. Leave clear space on the left for a headline. No text inside the image. Show me the result so I can choose the direction before we make the remaining assets.

5. Have it check your website

Open your project or provide a test URL. Ask the agent to work through specific user journeys and collect evidence. This is how you turn a vague 'check my site' request into something you can review.

For recordings, ask it to use the capture tools available on your device. Have it tell you when a recording isn't supported instead of claiming it made one. Use test data for forms.

Copy-paste this
Review my website at [test URL] using the browser. List the pages and user journeys you can test. Check the main navigation, the primary form and the mobile layout. Use test data. Capture screenshots of the important states. Record the journeys if recording is available in this environment. Create a local review page that groups the evidence by journey and lists any problems you found. Mark anything you couldn't test. Don't publish the review page yet.

Add tools for the work you actually do

For file work, search the plugin directory for Documents, Spreadsheets, Presentations, and PDF. These are also part of my setup. Use them when the finished result needs to be a document or a spreadsheet. Presentations handles slide decks.

Open each plugin's details and check what's included. Connect an external account when your task needs it. OpenAI's file guide explains the file workflows.

The plugin list shown at the end of the video

Here are the names from my plugin menu. Start with the browser tools above. Add the others when you have a use for them.

In the ChatGPT/Codex plugin directory: Documents, PDF, Spreadsheets, Presentations, Template Creator, Sites, Browser, Chrome, Computer Use, Visualize, Plugin Management, and Deep Research. Search these names in Plugins. Directory instructions.

From the official Claude plugin marketplace: Atlassian, Chrome Devtools MCP, Claude Code Setup, Claude Md Management, Code Simplifier, Context7, Figma, Frontend Design, GitHub, Huggingface Skills, MCP Server Dev, Neon, Playwright, Railway, Skill Creator, Stripe, Superpowers, Telegram, Typescript Lsp, and Vercel. Some add a workflow. Others connect a service and need a sign-in.

Other community plugins shown:

Anthropic Skills and Default templates also appear in my menu. Those names don't identify a verified public download for the exact bundle I have installed.

For a community plugin, search the directory first. If it isn't listed, check the linked publisher's installation instructions and the import options available in your app. Don't paste a Claude-only install command into Codex and expect it to work unchanged.

If a tool doesn't show up

Check that the plugin is installed and enabled. Finish any connection step, then start a new task. For Chrome, confirm the extension is in the correct browser profile and that the browser appears in the @ menu.

Update the desktop app if your controls look different. Availability can depend on your device, region, plan and workspace settings. Ask the agent which tools it can actually use in that task.

Use browser and computer access only on accounts and devices you own or have permission to operate.

Get the next one first

New prompts every week.

Free. The new drops and the tools behind them, before they hit the feed.

No spam · New issues Sunday · Unsubscribe anytime

Need it custom?

Want this built for you?

Tell me the idea and I’ll build it. An app, a tool, an automation. You don’t need to be technical.

Frequently asked questions

ChatGPT and Codex use the same public plugin directory, with support varying by surface. This guide focuses on the desktop workflows shown in my video. See the official plugin guide.

The setup starts with tools available to your account. Choose a supported model in your app, then enable the plugins you need. Changing the model doesn't install plugins or connect Chrome.

Check the plan and limits shown in your account. A plugin installation doesn't guarantee unlimited usage, and connected services can have their own requirements.

The computer work runs on a desktop host. With Remote configured, you can start or follow supported tasks from your phone while they run on your connected Mac or Windows computer.

You can start with the browser and Calculator prompts without writing code. Website testing works best when you can provide a working test page and describe the steps a visitor should be able to complete.