Run OpenCode in the cloud

A sleeping laptop runs nothing, so closing the lid stops OpenCode mid-task. To keep it working, run it on a machine that stays on:

• OpenCode in tmux on a server you run. You install it, maintain the machine, and move your code there with git.
• A Prized box. A Linux machine that stays on, with your project folder synced both ways and its ports on your localhost; one command installs OpenCode there and starts it. The steps follow.

11. Put your project on a box

Sign up at prized.dev: the tour starts a box on $30 of free credit with no card, then shows one command that installs the CLI and signs this machine in (Quickstart). Then run setup in your project folder:

cd ~/code/myproject
prized setup --no-start

It syncs this folder with ~/code/myproject on the box; --no-start keeps setup from starting Claude Code or another agent there. Already have a box? Skip the sign-up and run just the setup.

22. Start OpenCode on the box

prized agents run opencode --attach --dir code/myproject

The first run installs OpenCode on the box from a pinned release, checked against its SHA-256, then starts it in your project in a tmux session named opencode and opens that session in this terminal. A copy you installed on the box yourself is used instead.

OpenCode starts on its free models, which need no key; they are free for a limited time, and some may use what you send to improve the model (OpenCode Zen). For private code, connect your own provider on the box, since your laptop's OpenCode sign-in does not travel:

• Sign in: type /connect in OpenCode, or run opencode auth login in a shell on the box.
• Or use a key: add the provider's key as a Secret (Keys for other agents), then quit OpenCode and run the same command to restart it with the key.

33. Close the lid

Give OpenCode its task, then close the terminal or the laptop. The session belongs to the box, so OpenCode keeps working, and its edits sync to your laptop when it wakes (Sync). The same prized agents run opencode --attach --dir code/myproject opens the session again, or starts OpenCode again if the session is gone. If the session holds only a shell, as it does when the dashboard's OpenCode row opened it while OpenCode wasn't running, that command reports the session as already running and neither installs nor starts OpenCode: run prized ssh --kill opencode first.

44. Check on it from anywhere

• From a computer: prized ssh -s opencode. On another computer, install the CLI and run prized login first.
• From your phone or any browser: open the box on the dashboard. The arrow beside Open terminal lists OpenCode, which opens the box's terminal in the opencode session.

Or hand it a task and walk away

prized prompt --provider opencode --cwd code/myproject --auto --detach "run the test suite and fix what fails"

This runs OpenCode headless on the box and returns at once; prized events --follow follows the run. --auto lets it run commands; without it, OpenCode edits files but its shell commands are refused (Prompt an agent remotely).

With an updated box agent that supports running-job protection (the runs capability), the run counts as use even while it waits on the model. A turn that prints nothing for 6 hours stops counting. On an older agent, or when support is unknown, the run counts for one idle window after it starts, then only while it keeps the CPU or network busy. In that case, or if the task can stay silent longer, run prized box auto-pause BOX off before starting it (Auto-pause).

What it costs

Asleep, a box pays only for its disk (Billing). On the free credit, a box sleeps after 2 hours idle, never in its first 24 hours; OpenCode's output in its tmux session counts as use, so the box stays up while it prints (Auto-pause). Nano through Small keep OpenCode's session through a pause, and prized box pause sleeps it at once (Pause and resume).

Rather work in opencode Desktop? Use opencode Desktop with a Prized box runs its sessions on the box. Models and backends for headless runs are on Prompt an agent remotely.