1---
 2name: using-exe-dev
 3description: Guides working with exe.dev VMs. Use when the user mentions exe.dev, exe VMs, *.exe.xyz, or tasks involving exe.dev infrastructure.
 4user-invocable: true
 5---
 6
 7# About
 8
 9exe.dev provides Linux VMs with persistent disks, instant HTTPS, and built-in auth. All management is via SSH.
10
11## Documentation
12
13- Docs index: https://exe.dev/docs.md
14- All docs in one page (big!): https://exe.dev/docs/all.md
15
16The index is organized for progressive discovery: start there and follow links as needed.
17
18## Quick reference
19
20```
21ssh exe.dev help             # show commands
22ssh exe.dev help <command>   # show command details
23ssh exe.dev new --json       # create VM
24ssh exe.dev ls --json        # list VMs
25ssh exe.dev rm <vm>          # delete VM
26ssh <vm>.exe.xyz             # connect to VM
27scp file.txt <vm>.exe.xyz:~/ # transfer file
28```
29
30Every VM gets `https://<vm>.exe.xyz/` with automatic TLS.
31
32## A tale of two SSH destinations
33
34- **`ssh exe.dev <command>`** — the exe.dev lobby. A REPL for VM lifecycle, sharing, and configuration. Does not support scp, sftp, or arbitrary shell commands.
35- **`ssh <vm>.exe.xyz`** — a direct connection to a VM. Full SSH: shell, scp, sftp, port forwarding, everything.
36
37## Working in non-interactive and sandboxed environments
38
39Coding agents often run SSH in non-interactive shells or sandboxes. Common issues and workarounds:
40
41**scp/sftp failures**: Ensure you're targeting `<vm>.exe.xyz` rather than `exe.dev`. Use ssh-based workarounds.
42
43**Hung connections**: Non-interactive SSH can block on host key prompts with no visible output. Use `-o StrictHostKeyChecking=accept-new` on first connection to a new VM.
44
45**SSH config**: Check whether both destinations are configured to use the right key:
46
47```
48Host exe.dev *.exe.xyz
49  IdentitiesOnly yes
50  IdentityFile ~/.ssh/id_ed25519
51```