Docs · CLI

Workstation lifecycle.

Create, start, suspend, resume, destroy. Every workstation follows the same four states: STOPPED, STARTING, RUNNING, STOPPING. Idle suspension is automatic after 6 hours of no client connection.

Create

$ remoco user add luke luke@doss.com
# provisions a workstation named "luke" · grants workstations.user role
# starts the instance · prints SSH one-liner

Wake (start)

From your Mac, the remoco wrapper does this automatically on SSH. If you want it explicit:

$ gcloud workstations start wiley \
  --config=wiley-xl --cluster=remoco --region=us-central1 --project=remoco-cloud
# ~10 second resume from STOPPED to RUNNING

Use

$ ./infra/ssh.sh wiley          # interactive SSH
$ gcloud workstations ssh wiley \
  --config=wiley-xl --cluster=remoco --region=us-central1 --project=remoco-cloud \
  --command='remoco dev'
# one-shot command; used by agents

Suspend

Idle-suspend is automatic after 6h. To suspend manually:

$ gcloud workstations stop wiley --config=wiley-xl ...

Your /home/user persistent disk survives. Dev servers die on suspend — that's why everything runs inside tmux.

Resize (change class)

Edit the config, not the instance. All workstations on the config pick up the new class on next start.

$ gcloud workstations configs update wiley-xl --machine-type=e2-highmem-8

Destroy

$ remoco user remove luke
# confirms, deletes instance; reclaim-policy on the config decides disk fate

Tmux conventions

← CLI reference Worktrees →