Codex in ChatGPT

Give Codex a repository task from ChatGPT and review the work it completes in the cloud. The current workflow uses a published Codex Cloud environment: a reusable setup containing the repositories, tools, and access your task needs.

Before you start

• A ChatGPT account and workspace with Codex Cloud access. Cloud work requires ChatGPT sign-in; local API key sign-in is not a substitute.
• Access to the GitHub repository you want Codex to use, with the relevant work saved there. Files only on your computer are not automatically present in the cloud repository.
• The repository’s setup instructions, test commands if known, and permission to connect the repository. Private dependencies may require additional service access.
• One small task with an observable result, such as correcting a link to an existing page. Use the web or desktop app to create a new environment.

Want to do it yourself?

Difficulty

8 out of 10

Estimated completion time

1–2 hours, plus environment setup time

Skills you’ll need: Configure and test a cloud repository environment, inspect changed files, and distinguish setup failures from code failures.

I’ll do it myselfI’d rather get help

How this helps your brand

A prepared cloud environment can support reviewable website work away from your local computer. Recorded setup and behavior checks help you judge the result before it joins the project you publish.

1. 1

   Step 1: Choose a cloud environment in ChatGPT

   Sign in to ChatGPT on the web or in the desktop app. In a new task, choose Work in, then Cloud, and open Select environment. Select an existing published environment if it already contains the right repository and tools.

   If you need a new setup, choose Create environment. Select the GitHub repository and connect GitHub when prompted. Check the repository owner and name carefully before continuing.

   If the repository or Cloud option is missing, confirm the active account, workspace access, and repository connection. Resolve those prerequisites before sending a coding task.

2. 2

   Step 2: Prepare and test the environment

   For a new environment, select Get started. Codex inspects the repository and prepares dependencies and tools. Tell it the supported runtime, setup instructions, and relevant commands when it asks for details.

   For a website, ask it to identify how the preview starts and how the project checks its code. Read the setup report and errors; a completed installation alone does not prove the website starts or its checks pass.

   If a private package or service is unavailable, identify the required host and credential with your project owner. Configure access through the environment settings rather than putting a secret in the task prompt. Then repeat the failing setup check.

3. 3

   Step 3: Publish the tested setup

   Review the configuration, prepared files, and test results. Resolve unfinished setup work, save changes, and choose Publish. Wait for Environment published before selecting Start a new task.

   Publishing an environment prepares it for new coding tasks; it does not publish your website. Each new task gets its own workspace from the published setup.

   If you selected an existing published environment in step 1, you can start the task directly. Confirm it is still suitable for your current repository and dependency versions.

   Illustrated exampleOne published setup, separate task workspaces

   Example · Northline Studio website

   Published environmentRepository: northline/site

   Environment published

   • Repository
   • Runtime + dependencies
   • Tested setup commands

   Each new task starts from this setup

   1. A
      Fix the services linkIts own workspace and edits
   2. B
      Correct opening hoursIts own workspace and edits

   Publish prepares the environment. Your website still goes live through your normal deployment process.

4. 4

   Step 4: Give Codex a small repository task

   Use the prompt below and name the repository, page, current behavior, and expected result. For example, ask it to correct the home-page services link to an existing services page without changing the button’s styling.

   Ask Codex to inspect the relevant files, make the smallest edit, and report actual check results. Include steps for reproducing the issue so it can check the same behavior.

   Cloud work runs remotely and can continue while your computer is asleep. A running task is still work in progress: wait for its result and inspect it before using the changes.

5. 5

   Step 5: Review the files and verify the result

   Read the task’s summary and changed files. Check that the edit matches the repository and page you requested. Read the check output and separate passing checks from failures or commands that were not run.

   Request a correction in the same task if the edit changes unrelated behavior. For a visible website change, ask for a preview or other available evidence, then repeat the original user action in a runnable copy of the result.

   If browser verification is unavailable, do not count a successful code check as proof that the page works visually. Record the manual steps still needed and perform them before accepting the change.

   Illustrated exampleA passing code check still leaves a link to try

   Example changed fileapp/page.tsx

   Beforehref="/service"

   Afterhref="/services"

   Only the destination changes. The button text and styling stay the same.

   ✓ Code check

   npm run lintPassed in this example

   ○ Browser check

   Not run in the cloud taskStill needs a runnable preview

   Repeat the original action

   1. 1Open Home
   2. 2Choose Services
   3. 3Confirm /services

   Accept the link fix after the existing Services page opens correctly.

6. 6

   Step 6: Repair setup problems at the correct level

   A missing dependency is a setup problem; a wrong link is a task problem. If a check cannot start, ask Codex to name the missing tool, package, service, or access, then fix that prerequisite and rerun the check.

   For a reusable environment change, open Settings, Codex Cloud, then Environments. Edit the environment, prepare and test the update, save it, and choose Republish. Start a new task to use the update: existing tasks keep their own saved state.

   When the result is ready, use your normal review process to commit the work or open a pull request. Save important work in source control; an environment’s saved state is not your project backup.

Work in the selected Codex Cloud environment on [repository owner/name].

Task: [one small change]
Page or relevant file: [route or file path]
Reproduction: [steps to see the current problem]
Current result: [what happens now]
Expected result: [what should happen]
Verification: [existing check commands and manual steps, or ask Codex to identify them]

Inspect the repository and environment before editing. Preserve unrelated work and make the smallest necessary change. Run the relevant existing checks, then report changed files, commands actually run, their results, and any blocked checks or remaining manual verification. If setup or access is missing, identify it precisely instead of inventing a workaround. Leave the result for review; do not merge or deploy.