Agents
Start a coding agent on your box, close the laptop, and let it work; it is an ordinary process on a machine you already pay for, so nothing it does is metered.
On this page8
Start an agent
prized agents run claudeThis starts Claude Code in a detached tmux session named claude, in your synced project, and prints the reattach command; closing the lid changes nothing. run never starts a second copy of a session that exists; it says so.
| Flag | What it does |
|---|---|
--attach | Land in the session as it starts; otherwise reattach later with prized ssh -s claude. |
--dir | Working directory. Defaults to your only synced project; a clone is not one, so pass --dir ~/code/<name>. |
--session | Session name, for a second concurrent run of the same agent. |
-- ARGS | Everything after -- goes to the agent. |
The agent's own copy action (Claude Code: select, then c) lands on your clipboard through prized ssh (Copy out).
The four agents
| Agent | On the box | Runs on the box |
|---|---|---|
Claude Code (claude) | Preinstalled. | Yes |
Codex CLI (codex) | Preinstalled. | Yes |
Cursor (cursor) | Installed on demand (--install-cursor). | Yes |
ChatGPT app (chatgpt) | Drives codex over SSH from your machine. | No |
chatgpt is a connection, not a process on the box, so its tasks stop when your machine sleeps and prized agents run chatgpt refuses; prized agents run codex survives a closed laptop. App setup is on Codex remote.
See what is set up
prized agents lsOne row per agent: installed and signed in on your machine and on the box, MCP servers found, and where it is running. Read-only; takes --json.
Hand credentials to the box
prized agents handoff claude codexLists what would travel, asks, then copies the named agents' sign-in and MCP config to the box; prized setup runs the same step. Re-run it after changing MCP config. --gh adds your GitHub CLI token and git identity, --install-cursor installs Cursor's CLI first; what travels per tool is on Credentials.
Drive it remotely
prized prompt --provider claude "fix the failing tests and run them again"prized prompt runs the agent headless on the box and streams its events until the verdict; prized events follows a run and prized interrupt stops it, also over HTTP (Prompt an agent remotely).
Several agents at once
Each agent gets one session by default (claude, codex, cursor), each in its own project via --dir. For two runs of the same agent, name the sessions:
prized agents run claude --session claude-api --dir ~/code/api
prized agents run claude --session claude-web --dir ~/code/web
prized ssh --lsBring your own agent
Any CLI agent runs on the box. Pick other in setup's agent step and it prints these steps with your box's name filled in:
prized sshopens the box, waking it if needed.- Install the agent's CLI there.
- Sign in there, once per box; the credential stays on the box disk and Prized never sees it.
- Run it detached in a named session:
prized ssh -s myagent, ortmux new-session -d -s myagent 'the-agent'from any box shell. Reattach withprized ssh -s myagent.
For an API key, prefer a Connector: the box gets a placeholder and the real value never touches its disk. The handoff and prized agents run do not cover your own agent; sessions work the same.
Review from your machine
In a synced project, the agent's edits stream into the folder on your machine as it works, so you review the diff in your own editor. The box wins sync conflicts, so a local edit that races the agent yields to its work; a clone has no mirror, so review it over git.