exe-dev

What This Skill Does

The exe-dev skill provides a comprehensive interface for managing persistent virtual machines on the exe.dev infrastructure directly from your OpenClaw agent. It streamlines the lifecycle of cloud development environments by automating the creation, configuration, and networking of remote Linux instances. With this skill, you can provision new machines, define public exposure settings, manage HTTP proxy configurations for web services, and configure custom domain routing without leaving the agent's chat interface. It essentially bridges your local development workflow with cloud-based persistent compute resources.

Installation

To integrate this functionality into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/bjesuiter/exe-dev Once installed, the agent will have the necessary permissions and command definitions to interface with the exe.dev CLI wrapper. Ensure you have your SSH keys properly configured to allow the agent to authenticate with the exe.dev host.

Use Cases

• Web Application Hosting: Quickly deploy a frontend or backend application and make it accessible via an exe.xyz subdomain.
• Remote Development: Use the VSCode remote SSH capability to connect your local IDE to a powerful remote machine, ensuring your environment is persistent and independent of your local machine's state.
• Agentic Testing: Host custom AI agents (like the Shelley agent) on remote VMs and manage their port exposures (e.g., port 9999) dynamically.
• Service Prototyping: Set up quick reverse-proxy configurations for testing webhooks or authentication headers without manual server configuration.

Example Prompts

1. "Create a new VM on exe.dev and set it up to host my current project."
2. "Update the proxy settings for my VM 'my-cool-app' to expose port 8080 publicly."
3. "List all my active exe.dev VMs and give me the VSCode remote connection string for the one named 'dev-box'."

Tips & Limitations

⚠️ Warning: This skill is experimental and auto-generated from documentation. Always verify commands before executing them in production environments. Default ports are often pulled from Dockerfile EXPOSE directives, so ensure your Dockerfile is clean. Remember that for custom domains, you must manually update your DNS records (CNAME or ALIAS) to point to the exe.xyz infrastructure. When testing authentication headers, use tools like mitmproxy as documented to simulate the X-ExeDev-UserID and X-ExeDev-Email environment variables.