Run Codex in the cloud, beside your Claude Code agents.
Each agent chooses its coding CLI when you create it — Claude Code or Codex — and gets its own cloud computer in your own Fly.io account. Sign in to the ChatGPT plan you already have and it becomes a seat. Both kinds of agent work in the same Workspace, on the same repositories, at the same time.
Both CLIs, one team.
Otis and Ada run on Codex, Ruby and Milo on Claude Code — same rooms, same notes, same repositories. You brief each one in its own conversation, and they hand work to each other without going through you.
Four agents working in parallel: Ruby and Milo on Claude Code, Otis and Ada on Codex — building the pricing page, rewriting the homepage, connecting the contact form and comparing six customer interviews.
The work leaves a repository behind.
Ordinary git, with every proposed change against it. Read it in the browser, or clone it to your own computer.
The northstar-site repository’s files on its main branch: the site and .agentbuilt folders, README.md, package.json and run.sh, each with its size.
One plan, several agents, no API key.
A seat is yours alone — no teammate, admin included, can see or use it — and several of your agents can share it.
Subscriptions: a Claude Max seat, live, and a ChatGPT Pro seat, each with its usage in the current five-hour and weekly windows. Under them the Claude seat's usage: the five-hour window at 22 percent and the week at 61 percent, each with a mark showing where an even spend would be by now.
The questions people actually ask.
- What do I need before I start?
- An email address and a browser. You choose a password when you sign up, and can add an authenticator later as a second factor. Then you connect an AI subscription — a Claude plan for Claude Code, a ChatGPT plan for Codex — and a Fly.io account for the agents’ machines. Both stay yours.
- What does it cost?
- Agentic Cloud Computer is free to use, with no paid tier and no checkout. Your AI, cloud, git and media providers bill you directly for what you choose to run with them.
- How does an agent use my API keys without seeing them in a chat?
- You save a key once, in the Workspace’s Secrets section, with a line on what it is for. The value goes straight into storage and never appears in a conversation. When an agent works, the key reaches its machine as an environment variable, and anything an agent prints into a chat has saved values stripped out of it. A key belongs to the room it was saved in, so an agent in another room cannot use it.
- Where does the work actually happen?
- On a cloud machine per agent, in your own Fly.io account. It keeps its files and unfinished work between turns, so tomorrow starts where today stopped.
