Documentation
Machines and accounts

Codex Cloud tasks in codecast

Bring your Codex Cloud tasks into your inbox, start new ones with several attempts, and turn the result into a pull request or local changes.

6 min read

Codex Cloud runs Codex tasks on OpenAI's machines, against a GitHub repository, on your ChatGPT plan. Codecast brings those tasks into your inbox as ordinary sessions, and lets you start and steer new ones from the composer: send follow-ups, ask for several attempts, open a pull request, or apply a task's changes to the checkout on your computer.

A task runs on OpenAI's machines, but one of your computers does the talking: the browser can't reach Codex Cloud by itself, so codecast drives it from a computer of yours that is signed in to Codex. Your Codex sign-in never leaves that computer.

Connect Codex

  1. Open Settings and choose Provider Keys under Machines. The Codex Cloud row says whether the selected computer is signed in.
  2. Click Connect Codex, then Sign in to Codex. Codex opens its sign-in page in the browser on that computer; sign in with the ChatGPT account your tasks run on. On a computer with no browser, such as a cloud machine, use Sign in with a code and enter the code it shows.
  3. The dialog says the computer is signed in to Codex, with your account and plan, and the row's button reads Codex connected.
The Codex Cloud row in Provider Keys
Codex Cloud runs on the computer's Codex sign-in, not on an API key.
The Connect Codex dialog once a computer is signed in
The sign-in itself stays on the computer.

Set up an environment for each repository. Codex Cloud runs a task in an environment made for its repository, under Codex → Environments on chatgpt.com. If you have several for one repository, pin the one you want. Without one, your first message waits and its card links to that page; it goes out on its own once the environment exists.

Bring your existing tasks in

Settings → Sync & Privacy → Sync Codex Cloud tasks is off to start with. Off, codecast shows only the tasks you start from codecast. On, it also brings in every task on your account from the last 30 days, including ones you started on chatgpt.com.

Each task becomes a Codex session with its title, repository, branch and pull request. Its transcript shows the prompt, Codex's reasoning, each command with its output, the answer and the diff. Codex Cloud doesn't stream: while a turn runs, the session shows Codex's latest progress line, and the whole turn appears when it ends.

Start a task

In a new session's composer, pick Codex as the agent. Open the menu that says where the session runs and choose OpenAI's cloud. More controls appear beside it:

  • with: ChatGPT plan runs on Codex Cloud. API key is the other lane, described below.
  • ask: Codex reads the repository and answers, without changing code or opening a pull request.
  • attempts (1 to 4): Codex makes several attempts at your first message.
The new-session composer set to run in OpenAI's cloud on the ChatGPT plan, with ask and attempts
Run in OpenAI's cloud, on your ChatGPT plan, with three attempts.

The task starts from your checkout's branch if that branch is on GitHub, otherwise from the repository's default branch. Codex works from GitHub, so commits you haven't pushed aren't there; the transcript says so under the first prompt.

Every later message is a follow-up. A message sent while a turn is still running waits and goes out when the turn ends. Stopping the session cancels the running turn, and every attempt with it.

Compare attempts

Three attempts at one prompt become three branches of one session. A follow-up continues the attempt it was sent on.

Each attempt becomes a branch of the session. Chips under the shared prompt switch between them, with an unread dot on each. Switch attempt in the session menu opens the branch map, which does the same.

Pull requests and your own checkout

The Codex Cloud chip in the session header holds the task's actions. They are also in the session menu and the command palette.

The Codex Cloud chip's menu in a session header
The task's actions live on the Codex Cloud chip.
ActionWhat it does
Open on chatgpt.comOpens the task on chatgpt.com
Create draft PROpens a draft pull request with this attempt's changes. A toast links to it, and the session's branch and pull request follow
Apply locallyWrites this attempt's changes into the repository's checkout on your computer, uncommitted. It refuses if you have local edits to a file the change touches, and says so if the checkout already has the changes
Archive / UnarchiveHides the task on chatgpt.com, or brings it back. The session stays in codecast either way

An ask task doesn't change code, so its PR and apply actions are off.

When Codex Cloud can't go on

When something stops Codex Cloud, a word appears beside the composer control and on the session chip, and a message you send waits with a card that says why. It goes out on its own once the cause clears.

You seeWhat it meansWhat to do
not connectedThe computer has no Codex sign-in, or it expiredClick Connect Codex on the card and sign in again
needs setupThe repository has no Codex environmentCreate one under Codex → Environments
limitedA window of your ChatGPT plan's Codex limits is used upWait for the reset; the card counts down. Running tasks keep syncing
no accessYour ChatGPT Business or Enterprise workspace keeps Codex Cloud off for youAsk a workspace owner to turn on Use Codex in the cloud for you. Signing in again won't help
pausedCodex Cloud changed in a way codecast can't read yetNothing to do: codecast checks again every few minutes and resumes on its own

A waiting message's card also offers Start on API key instead, which runs it on the other lane.

The API key lane

API key under with runs the session on the OpenAI Agents API, billed to the OpenAI key in Settings → Provider Keys at API rates plus sandbox time. It streams as it works, but it reaches public GitHub repositories only and can't push, open a pull request or apply changes. Its sessions sync separately, under Sync OpenAI Agents API sessions.

Good to know

  • Tasks count toward your ChatGPT plan's Codex limits, the same ones the usage meter in the header shows.
  • Codecast never refreshes your Codex sign-in, because that would sign out the Codex you run yourself. When it expires, sign in again from Settings.
  • Codex Cloud has no public API, and OpenAI can change it without notice. When that happens codecast pauses rather than guessing, and resumes once it can read Codex Cloud again.
  • Reading a task in codecast doesn't mark it read on chatgpt.com.
  • A Codex environment's variables and secrets are never stored or shown by codecast. What syncs is the task: its transcript, title, branch and pull request.
More guides
Agent features: what your agents know how to do
Switch features on for each computer, and every new session there learns to remember, delegate, track work, show results and use your machine.
Memory: agents that look up past work
Your agents search every session you can see, across your machines, agents and team, and answer with the session they found it in.
Let Claude, Cursor and Codex read your codecast
Add codecast.sh/mcp to an agent that runs outside codecast, sign in once, and it reads your docs, tasks, plans, pages and sessions as you, read only.
Search your history across every machine
Every computer you connect sends its sessions to one history, searchable from the web, the Mac app and your iPhone.
See which agent session wrote a line
Set Blame to Sessions on any file to see the session behind each line, and open the conversation where it was decided.
Messaging between sessions
Your sessions hand each other results and answers directly, so you stop relaying text between them.
Stable context: sessions that know what's been happening
New sessions start with a short list of what you and your team worked on recently, so they pick up threads instead of starting cold.
See your whole team's agent sessions in one place
Every session your team runs, on every machine and agent, in one live Activity page and inbox, shared per folder.
Use Codecast with T3 Code
Threads you start in T3 Code appear in Codecast with no setup, beside every session you run anywhere else, ready to search, steer and share. What you get on top, and what stays in T3 Code.
Use Codecast with OpenCode
Sessions you run in the OpenCode TUI appear in Codecast within seconds, with no plugin. Reply to them from the app, start new OpenCode sessions there, and search them beside every other agent you use.
Share a session with your team
Choose what the team sees of a session, share it by link or a few messages at a time, and how that compares to other tools.
Pinned thread state
The agent keeps one short note on each session saying where it stands, above the composer and on its inbox card.
Decisions: asking without interrupting
Agents put the calls only you can make on one Decisions page you clear when you choose to, and each answer goes back to the session that asked.
Team chat with your agents in the room
Channels, threads and DMs where you can hand a session or a role something by mentioning it, while agents stay quiet unless they're needed.
Huddles, transcripts and walkie
Every huddle is transcribed under each speaker's name and leaves a summary, so your agents can quote what was said, and a session can join the call.
Workers, forks and switching agents
Your agent can hand work to workers that report back to it, and you can fork a conversation to try two directions from the same point.
Tasks and plans
Agents file the work they take on, post progress and close it with what they verified, and you follow it on the Tasks and Plans pages.
Triggers
Agents schedule their own follow-ups, once, on a schedule or on a GitHub or Linear event, and you can set one yourself from the Triggers page.
Workflows
A fixed sequence of agent steps, checks and approval gates that runs the same way every time and waits for you where you want a say.
Orchestration
Hand an agent a whole plan and it runs a team: implementers working in parallel, a reviewer on every task and critics on the result.
Pull requests and issues
Every pull request gets a page with its checks and threads, the session that opened it fixes what reviewers and CI flag, and Linear or GitHub issues become tasks.
The org: roles that look after your work
Give lasting work to a role with an area, a charter and a standing session, and approve the changes your agents propose to the org.
Let agents use your Chrome
Agents check pages in the Chrome you already use, logins included, from their own background tabs. Screenshots and errors come back to the conversation.
Vault: keys, logins and sign-ins for your agents
Fill a credential once and every agent on every machine can use it, without the value ever entering a conversation.
Computer use: agents in your Mac apps
Agents work in Preview, Slack, System Settings or your own desktop build, in the background, with an orange pointer that shows where they act.
Typecheck: one shared check for every agent
With Typecheck on, agents on a computer share one typecheck per project, so checks answer in seconds and a busy machine stays usable.
Skills: slash commands for the jobs you repeat
Type / in a Claude Code session to pick up work, hand it over, get a second opinion or ship a pull request, the same careful way every time.
Run sessions on other machines and in the cloud
Start a session on another computer or a cloud machine in your AWS account, move it there and back, and watch it from anywhere.
Usage limits are a pause
When a Claude plan runs out, sessions wait for the reset or continue on another account you've saved, instead of stopping for good.
The visual canvas
Agents answer with charts, comparisons and diagrams drawn right in the conversation when a picture says it better than text.
Published pages
Agents turn reports and mockups into pages with their own link that you can share, gate, and get comments on.
Why codecast feels instant, even offline
Everything you see comes from a copy on your device that the server keeps current, so screens open at once, your edits show immediately, and nothing is lost offline.
Taking longer than usualOffline · reloads when back