awml
Sign in

awml / platforms / codex-cloud

Codex Cloud

Platform · Public ·
Version 1 of 2
  1. #2 · chrismdp · · 0.4Latest
  2. #1 · chrismdp · · 0.3Showing

Codex Cloud: Codex working on a task in its own VM in OpenAI's cloud, in an environment set up with the task's GitHub repositories. Tasks start when someone asks, in ChatGPT on the web, phone or desktop, from @ChatGPT in Slack, or as a review asked for with @codex review on a GitHub pull request. It has no schedule of its own. This describes a kind of platform, not anyone's workspace. Checked against OpenAI's documentation on 22 October 2026. https://learn.chatgpt.com/docs/third-party/github https://learn.chatgpt.com/docs/third-party/slack

What it offersInstall recipeYAML

Install a workflow on Codex Cloud

Each task is a Codex session in its own virtual machine in OpenAI's cloud, in an environment set up with the workflow's GitHub repositories. A task starts when someone asks for it: in ChatGPT on the web, phone or desktop, through @ChatGPT in Slack, or as a review asked for with @codex review on a GitHub pull request. Codex Cloud has no schedule of its own, so a workflow started by a time needs a different platform, even though awml fit cannot tell.

Run awml fit with the workflow's security view and this description first. If it reports code steps, Codex will carry them out by following instructions.

What to create

  1. A GitHub repository holding the instructions in AGENTS.md, any scripts for code steps, and the workflow's contexts under notes if they are kept there. Give one section of AGENTS.md to each step, in the order the drawing lists them, saying what it reads, what it writes and what its operation must not do. An outside action marked Ask ends in a draft, a pull request or a message asking for a yes.
  2. A cloud environment with that repository. Open Codex in ChatGPT, choose the repository and Get started, and let Codex inspect it and install what it needs. Review the checks, then publish the environment.
  3. Internet access only where a step needs it. Agent internet access is off until you turn on Allow Codex to access internet in the environment; then allow only the domains the steps need.

Where secrets go

Credentials for HTTPS services go in the environment as network secrets, each with the domains it may be sent to. Programs see only a placeholder, and the proxy puts in the real value for allowed destinations. Values that are yours alone go in your personal vault. Never put a key in AGENTS.md, the repository or a task's request.

How to schedule the triggers

Codex Cloud runs a task when it is asked. Start one from ChatGPT with the environment selected, mention @ChatGPT in a Slack channel connected to the workspace, or ask for a review with @codex review on a pull request. For work on a schedule, use a platform with a scheduler, such as GitHub Actions or Claude Code cloud scheduled tasks.

How to check it is running

Each task shows its changed files and results in Codex in ChatGPT, where you can ask for follow up changes, then commit or open a pull request. A task's saved machine state can be recovered for up to seven days after its last turn.

Sources

  • https://learn.chatgpt.com/docs/cloud
  • https://learn.chatgpt.com/docs/environments/cloud-environments
  • https://learn.chatgpt.com/docs/third-party/github
  • https://learn.chatgpt.com/docs/third-party/slack