Two kinds of terminal
The selector at the top of the Terminal tab chooses where the shell lands:- Host (default), lands you as
rooton the VM. Full control: install packages, edit/etc/, rundocker, restart services. - An app install: lands you inside that app’s container, as the image’s
USERdirective (for examplenodefor OpenClaw). Use this to run app-specific CLIs without leaving the dashboard.
Session persistence
Sessions run insidetmux on the VM. That means:
- Close your laptop, come back tomorrow → reconnect into the same tmux session, with full scrollback intact.
- Run a long process, navigate away, come back → it’s still running.
- Refresh the dashboard → tabs reopen.
exit in the terminal. It kills the tmux session.
Useful shortcuts
Per-app conveniences
When you select an app install:- The CLI binary the image declares (
bininpackage.jsonfor Node apps) is automatically symlinked intoPATH: for exampleopenclaw devices listworks even though the image ships it asnode /app/openclaw.mjs. - Your working directory is set to the app’s
WORKDIR(/appfor most images).
Security notes
- The host terminal runs as
rootbecause the VM is dedicated to your tenant. There are no co-tenants to drop privileges for. - Per-app terminals run as the container’s configured user. Add
--user 0to adocker execonly when you have to (e.g. one-shotchown). - All terminal traffic is encrypted between your browser and your VM.
- Closing the tab does not kill the session. Use
exitif you want to.
Next
Files
Browse and edit files without a shell.
Logs
Stream live container logs.