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 services.
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install bjesuiter/exe-devInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
⚠️ 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 | ssh exe.dev ls --json |
| Create VM | ssh exe.dev new |
| Make public | ssh exe.dev share set-public <vm> |
| Change port | ssh exe.dev share port <vm> <port> |
| Add user | ssh exe.dev share add <vm> <email> |
| Share link | ssh exe.dev share add-link <vm> |
https://<vmname>.exe.xyz/
https://<vmname>.exe.xyz:9999/
vscode://vscode-remote/ssh-remote+<vmname>.exe.xyz/home/exedev
Default 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.xyz
example.com → exe.xyz + CNAME www → vmname.exe.xyz
See references/exe-dev-vm-service.md for complete documentation including pricing, Shelley agent setup, SSH key config, and FAQ.
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
> ⚠️ **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. 🔜 # exe.dev VM Management ## Quick Commands | Task | Command | |------|---------| | List VMs | `ssh exe.dev ls --json` | | Create VM | `ssh exe.dev new` | | Make public | `ssh exe.dev share set-public <vm>` | | Change port | `ssh exe.dev share port <vm> <port>` | | Add user | `ssh exe.dev share add <vm> <email>` | | Share link | `ssh exe.dev share add-link <vm>` | ## Access URLs - **VM**: `https://<vmname>.exe.xyz/` - **Shelley agent**: `https://<vmname>.exe.xyz:9999/` - **VSCode**: `vscode://vscode-remote/ssh-remote+<vmname>.exe.xyz/home/exedev` ## Proxy Configuration Default port is auto-selected from Dockerfile EXPOSE. Change with: ```bash ssh exe.dev share port <vmname> <port> ``` Access ports 3000-9999 via `https://vmname.exe.xyz:<port>/` ## Authentication Headers When users authenticate via exe.dev: - `X-ExeDev-UserID` — user identifier - `X-ExeDev-Email` — user email For testing, use mitmproxy to inject headers: ```bash mitmdump --mode reverse:http://localhost:8000 --listen-port 3000 \ --set modify_headers='/~q/X-ExeDev-Email/user@example.com' ``` ## Custom Domains - **Subdomains**: CNAME `app.example.com` → `vmname.exe.xyz` - **Apex**: ALIAS `example.com` → `exe.xyz` + CNAME `www` → `vmname.exe.xyz` ## Full Reference See [references/exe-dev-vm-service.md](exe-dev-vm-service.md) for complete documentation including pricing, Shelley agent setup, SSH key config, and FAQ.
University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...
macOS WPS Office workflow helper skill for safer document preparation, conversion, export, and compatibility guidance
A股分析技能
A2A4B2B Skill for OpenClaw