Prized docs

Quickstart.

Four steps from signup to a box with your project on it and your coding agent signed in. You need a Mac.

1. Sign up and create a box

Go to prized.dev and sign up. You can walk through the tour and look around the dashboard before paying for anything; what needs a plan is running a box.

Choosing a plan is what starts your first box, so there is no separate size to pick: each plan is priced to run one size around the clock, and the $100 plan gets you a Small. Your first cycle's credit lands before you are back from Stripe and the box boots while you install the CLI, which takes about the same minute. After that, boxes bill by the hour from that credit, so a shape the balance could not keep running for four hours cannot be created (unless you switch on overage, which bills the extra with your next invoice instead); see Billing for the plans and rates.

2. Install the CLI

curl -fsSL https://prized.dev/install.sh | sh

This installs prized, its background daemon, and a Prized-managed copy of Mutagen, which powers sync; there is nothing else to install. Re-running the installer upgrades in place, and prized update does the same from inside the CLI. If the Mutagen download fails because you were offline, prized setup fetches it later. Once you are signed in the CLI reports command usage (never arguments or file contents) to help us fix bugs; it is easy to turn off.

3. Log in

prized login

Your browser opens the dashboard, where you mint a CLI token. Paste it back into the terminal. The CLI stores it in ~/.config/prized and sets up your SSH identity. Tip: the install command shown during onboarding carries a single-use link that does this step for you.

4. Set up

prized setup

One command for the rest, safe to re-run at any time. setup finds the box on your account, writes the config, installs the SSH stanza, starts the background daemon, and runs a health check; re-run it later and it converges whatever is missing without clobbering anything. Then it offers the optional parts, asking before the first two:

  • Project. Name one (prized setup myproject) and it creates ~/code/myproject on the box, mirrored to ~/Prized/myproject on your Mac, both ways, .git included. Pass a path (prized setup ~/src/myproject) and setup offers three modes for it: synced in place (the folder itself is the live Mac side, box wins conflicts), --copy (a copy under ~/Prized, original untouched), or --clone (a git clone on the box, no live mirror; right for a checkout other people or agents also edit). See Sync.
  • Agents. Pick from Claude Code, Codex, Cursor, and the ChatGPT app, and setup hands each one to the box: its sign-in and MCP servers travel over the SSH tunnel, so the box is signed in without retyping any OAuth flow. It lists exactly what would be copied and asks per agent; see Credentials.
  • Session. With exactly one runnable agent picked, setup starts it in a detached tmux session on the box and prints the reattach command, no extra question; pass --no-start to skip this. That session keeps running with your laptop closed.

Connect any time with prized ssh, which lands you in a persistent tmux session; a dev server started there appears on your laptop's localhost within seconds.

Check everything at once with prized status: box vitals, sync state, mirrored ports, daemon health.

Or let an agent do it

Steps 2 through 4 are one paste into your coding agent. Onboarding composes the prompt for you: its connect step asks setup's questions in the browser (your agent, then the project and how it reaches the box) and bakes the answers in, GitHub handoff included, ready for Claude Code, Codex, Cursor, or Codex in the ChatGPT app. The generic prompt, for a later machine, is on Agent setup.

Something unclear or out of date?

On this page