Concepts

Orgs

An org is the top-level billing and membership boundary — everything else (projects, sandboxes, members, usage) belongs to exactly one org. A Starter, Pro, or Max org is single-player; a Business plan org has members, seats, and shared limits.

Most CLI commands resolve the org automatically: if you belong to exactly one, it's used without asking. If you belong to more than one, pass --org <name-or-id> (or -o).

Projects

A project is the resource boundary within an org — every sandbox belongs to exactly one project. A project holds a repository and default branch, and optionally free-text context (conventions, guardrails, architecture notes) that gets written into every sandbox created under it as CLAUDE.md/AGENTS.md. Every org gets a Default project automatically; creating a sandbox with --project picks a different one, and is only required when an org has more than one.

Sandboxes

A sandbox is an isolated host: its own machine, processes, ports, package cache, environment variables, and filesystem, provisioned on demand and torn down when you're done with it. Each sandbox runs one agent — claude or codex — against one repository, on one branch.

Sandboxes move through a lifecycle:

stopping is what sleep returns, and it lasts only as long as the snapshot takes to write. It shows as saving, and becomes stopped on its own.

Attaching (remote attach) connects to a Firecracker sandbox over the RemoteHost envd tunnel, and to a direct-IP provider over SSH using the per-installation keypair generated the first time you created a sandbox — every sandbox trusts the key of the person who created it, not a shared operator key.

Agents

Remotehost launches one of two coding agent harnesses inside a sandbox:

• claude — Claude Code
• codex — Codex

Remotehost doesn't modify or wrap the agent — it provisions the machine, injects your SSH key and repository, and launches the agent's normal CLI inside it.

Sandbox profiles and machine sizes

Sandbox profiles describe the intended workload. auto starts from the smallest viable sandbox shape and can grow from measured pressure over time. Named profiles such as agent-small, agent-standard, build-heavy, and browser-heavy give RemoteHost clearer intent when the workload is known upfront.

Every sandbox runs on one of three machine sizes, chosen with --machine-size (-m):

The multiplier scales how much of your plan's included machine-hours (or overage) a running sandbox consumes per hour — see Pricing & Billing.