Docs / Agents

Runtimes and computers

Run Claude Code, Codex, Cursor or Antigravity on a Pangea Cloud computer, your own server, or your Mac, and share a computer with teammates.

Pangea is the team workspace around your coding agents. It adds context, scoped credentials, tools, memory, approvals, transcripts and collaboration. The runtime and its model account stay yours.

Three words describe where work happens:

• A computer is a machine: a Pangea Cloud computer run for your team, a server you run, or a Mac running the Pangea app.
• A runtime is one coding agent, such as Claude Code or Codex, installed on a computer.
• An agent is the long-lived worker you talk to. Each agent runs on a runtime.

Supported runtimes

Each runtime keeps its own vendor harness and sign-in.

Pangea also supports OpenCode, with its own provider sign-in, and Grok Build, with your xAI account.

Pick the model and reasoning effort in the composer. Codex models that offer it also have an Ultrafast mode beside Fast.

Add a computer

You need an account with the runtime's provider, such as Claude or ChatGPT. Only a team Administrator can add computers.

1. Open Computers

In the Mac app, open Settings → Computers and choose Add computer.

2. Choose where it runs

• Pangea cloud computer: a computer Pangea runs for your team, with its own desktop. Give it a name and a size, and pick who can use it: only team admins, everyone, or specific people. Then choose Create computer. Cloud computers come with your plan.
• Your own computer: a laptop or server you run. Pangea shows a one-time command. Run it on the machine and it joins the team as a computer. The token in the command works once and expires in an hour.

3. Sign in

Choose the runtime and sign in with your own account. Pangea opens the provider's page. Approve access, then paste the code it shows if asked. The sign-in stays on that computer. You can also sign in later from the runtime's card.

4. Start an agent

When the runtime is online, choose New agent in the sidebar and pick the runtime in the composer.

On a Mac running the Pangea app, you can also use a runtime already installed there. Open Settings → This computer → Local runtime. A local runtime runs only while Pangea is open, and only for your own agents unless you share the computer. On a server without the app, run pangea agent instead.

A cloud computer's software updates from its card under Settings → Computers. An update restarts every agent on it.

Share your computer with teammates

You can let teammates run their own agents on your computer's local runtime. Under Settings → Computers, open your computer's menu and choose Manage access…. Share it with everyone in the team, including people who join later, or with chosen people. Then pick how requests are handled:

• Ask me first: you approve each teammate's agent before its first turn. The request appears in your Inbox. Their message is sent once you approve.
• Full access: no approval needed.

When you approve, you can approve once, Approve and trust for 8 hours, or Approve and always trust. To revoke access, change it in Manage access….

Agents started from a channel or a trigger never run on a shared computer.

When a runtime runs out

Under Settings → My preferences → Agent fallback, keep an ordered list of runtimes to fall back to. When a session's runtime is out of usage, unreachable, or fails a turn, the session moves to the next one in your list, and the transcript says why.

What Pangea adds to the runtime

For each agent, Pangea gives the runtime a scoped set of capabilities:

• the cloud credentials selected for that agent;
• Kubernetes configuration built from the selected accounts and clusters;
• built-in Pangea skills and skills written by your team;
• tools for infrastructure, observability, databases, knowledge and triggers;
• shared team memory and resource context;
• plans, human decisions, approvals, and links back into Pangea.

Tool calls, reasoning, plans and answers stream back into the shared transcript. The transcript survives reconnects. Moving work between runtimes depends on the provider and the destination. Read the move confirmation, and don't assume local files or sign-ins move with the history.

Provider accounts and terms

Each provider sets its own subscription limits, acceptable use and enforcement. Review the terms for the account and the sharing you plan to use. Pangea does not exempt you from those terms.

Credentials and isolation

An agent is authorized with a short-lived token bound to its user, team and session. The backend checks the routes it may call and the connections selected for it. That token can't be used for other teams or other sessions.

Cloud access is limited by both the account's member allow-list and the credentials selected for the agent. Pangea mints or fetches credentials when needed, instead of copying every connected credential onto the computer. See Access control and IAM trust model.

A runtime's sign-in stays on its computer. Read removal and deletion confirmations with care: stopping a runtime, deleting a cloud computer and revoking a provider sign-in have different effects. Save the files you need before deleting a computer. Conversation history is not a backup of its disk.

Usage and billing

Model usage runs on the account the runtime signs in with, such as your Claude or ChatGPT subscription. Pangea never charges for model tokens. Cloud computers and their hours come with your team's plan. See Plans and billing.

Troubleshooting

• Not signed in: open the runtime under Settings → Computers and sign in again. Providers can expire or revoke sign-ins.
• Starting: a new cloud computer is still starting. It usually takes 10 to 30 seconds.
• Offline: the computer is paused or unreachable. Resume it from its menu. For your own machine, check that pangea agent is still running there.
• Out of cloud hours: the team used its monthly hours. See Cloud hours.

Move between computers

Use a session's runtime picker to move future work to another runtime. Push or copy the repository changes and set up dependencies on the new computer first. Don't delete the old computer until the new one has everything you need. The transcript is not a backup of the computer's disk or sign-ins.