Connect to a workspace

Keep development on your node and use the editor and SSH client on your laptop.

Create a workspace

First create a project and copy its UUID. Supply your public Ed25519 key, not your private key. Run this command where the CLI can access the daemon socket:

readylab --wait workspace create <project-uuid> \
  --name dev --ssh-key "$HOME/.ssh/id_ed25519.pub" \
  --cpu 2 --memory-mb 2048 --disk-gb 20

Readylab marks the workspace Ready after its development checks pass. Use an existing Git-backed project to prepare source automatically, or begin with an empty workspace.

Connect over SSH

readylab workspace ssh <workspace-uuid> --identity "$HOME/.ssh/id_ed25519"
readylab workspace code <workspace-uuid> --identity "$HOME/.ssh/id_ed25519"

The second command needs VS Code Desktop and Remote-SSH on the client. If the workspace is behind the node’s private bridge, add --proxy-jump readylab-node, using your verified SSH alias.

The CLI helpers require daemon access to obtain fresh workspace metadata. If your laptop does not have that local daemon connection, use the paired browser UI’s Workspace Connect dialog to generate standard SSH/VS Code guidance through the node. The browser does not receive your private key.

Stop and start

readylab workspace status <workspace-uuid>
readylab --wait workspace stop <workspace-uuid>
readylab --wait workspace start <workspace-uuid>

Stopping the machine keeps its filesystem, but stops its running processes. This differs from disconnecting your laptop from an agent running in a persistent session. A separate app deployment can keep running while a workspace is stopped.

Your connection identity

Use the private key corresponding to the public key supplied at workspace creation. The helpers verify the guest fingerprint against daemon access metadata. Keep SSH host-key verification enabled for the node too.