exe-dev
Manage persistent VMs on exe.dev. Create VMs, configure HTTP proxies, share access, and set up custom domains. Use when working with exe.dev VMs for hosting, development, or running persistent service
Manage persistent VMs on exe.dev. Create VMs, configure HTTP proxies, share access, and set up custom domains. Use when working with exe.dev VMs for hosting, development, or running persistent service
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
ā ļø Warning: This skill was auto-built by clawdbot from the exe.dev markdown documentation. It's not tested yet ā use with caution! I plan to test it soon. š
| Task | Command |
|---|---|
| List VMs | |
| Create VM | |
| Make public | |
| Change port | |
| Add user | |
| Share link | |
https://<vmname>.exe.xyz/https://<vmname>.exe.xyz:9999/vscode://vscode-remote/ssh-remote+<vmname>.exe.xyz/home/exedevDefault port is auto-selected from Dockerfile EXPOSE. Change with:
ssh exe.dev share port <vmname> <port>
Access ports 3000-9999 via
https://vmname.exe.xyz:<port>/
When users authenticate via exe.dev:
X-ExeDev-UserID ā user identifierX-ExeDev-Email ā user emailFor testing, use mitmproxy to inject headers:
mitmdump --mode reverse:http://localhost:8000 --listen-port 3000 \ --set modify_headers='/~q/X-ExeDev-Email/user@example.com'
app.example.com ā vmname.exe.xyzexample.com ā exe.xyz + CNAME www ā vmname.exe.xyzSee references/exe-dev-vm-service.md for complete documentation including pricing, Shelley agent setup, SSH key config, and FAQ.
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
Ā© 2026 Torly.ai. All rights reserved.