FAQ

Where does my code live?

On the machine the workspace runs on. For a self-hosted box that's your hardware — Motion never copies your files to the hub; it proxies to your daemon over the tunnel. For a cloud workspace it's the container Motion runs for you.

Do I need Docker?

Only for Docker mode. The native install (--host / connect.ps1) runs directly on the host with no Docker and brings its own runtime. See Self-hosting.

Is the tunnel secure?

The box dials out to the hub (nothing inbound to open), authenticates with a 256-bit token sent in a header (not the URL), and the connection is WebSocket over TLS. You can rotate the token any time.

Can anyone with the link open my workspace?

No — opening a workspace requires your authenticated session. The connect token only lets a box register itself; it doesn't grant dashboard access.

What does --root / do, and is it safe?

It lets the IDE browse the whole machine. It's powerful — anyone who can open that workspace gets full read/write + a shell. Use it only on a machine you control. Default is your home directory. See What the IDE can see.

Will it survive a reboot?

Docker and native + systemd installs restart automatically. A native install without systemd does not — run motion start after a reboot. Check with motion status.

How do I update a box?

motion update — it checks the hub and updates in place, only swapping on a successful download. See the CLI.

How do I remove it completely?

motion uninstall stops everything and deletes ~/.motion. Your own files are untouched. Delete the workspace from the dashboard too if you're done.

Which platforms are supported?

Linux (x64/arm64) and macOS via the shell installer; Windows via connect.ps1. See Self-hosting for per-platform notes.