メニュー
Log in to the Heyo platform via `heyvm login` — authenticate with email/password or API key to enable cloud sandbox operations (deploy, list, archive, etc.).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use the Heyo Cloud API to manage deployed sandboxes — execute commands, read/write files, start/stop sandboxes, and check status. Use when an agent needs to interact with a running deployed sandbox programmatically.
Deploy apps to Heyo cloud sandboxes — archive code, deploy to production, bind ports, set up custom domains, and manage deployed sandboxes. Use when the user wants to deploy, update, or manage a running app.
Build Dockerfiles for Firecracker microVM rootfs images and manage them with `heyvm mvm`. Use when the user wants to create a Firecracker image, write a Dockerfile for a Firecracker VM, or build/list/manage Firecracker rootfs images.
Use heyvm proxy, connect, share, ssh, and bind commands to expose ports, connect to remote sandboxes over P2P (iroh), mount remote workspaces, and share sandbox shells.
Create, start, stop, restart, list, and exec commands in heyvm sandboxes. Use when the user wants to manage sandbox lifecycle, run commands in isolated environments, or configure sandbox settings like mounts, ports, and backend types.
Check if the host system meets all requirements to run VM sandboxes. On Linux, verifies KVM, Firecracker, kernel images, networking permissions. On macOS, verifies Apple Container and Apple Virtualization native (apple_virt) readiness and VM images. Runs a full end-to-end test on each platform. Use when the user wants to diagnose setup issues or verify their host is ready.
| name | heyvm-login |
| description | Log in to the Heyo platform via `heyvm login` — authenticate with email/password or API key to enable cloud sandbox operations (deploy, list, archive, etc.). |
| argument-hint | [--api-key <KEY> | --email <EMAIL>] |
| allowed-tools | Bash, Read, Grep |
You are helping the user log in to the Heyo platform so they can use cloud features (deploying sandboxes, archiving, listing deployed sandboxes, etc.).
The binary is heyvm. If it is not on PATH, build it from mvm-ctrl/:
cargo build --release -p heyvm
heyvm login
Prompts for email, then securely prompts for password (hidden input). This is the simplest flow for most users.
You can also provide email up front:
heyvm login --email user@example.com
heyvm login --api-key <KEY>
Exchanges the API key for a JWT token. Also persists the key to ~/.heyo/.env so the CLI can refresh tokens automatically.
heyvm login --email user@example.com --password 'secret'
Both email and password can be passed as flags for automated workflows. Avoid this in shared shell history.
| Flag | Description |
|---|---|
--api-key <KEY> | Authenticate with an API key |
--email <EMAIL> | Email address for login |
--password <PASS> | Password (omit to be prompted securely) |
https://auth.heyo.computer by default, or the URL set via --auth-url / AUTH_SERVER_URL).~/.heyo/token.json.~/.heyo/.env for automatic token refresh.list, archive, deploy, connect, etc.) use the stored token automatically.Running heyvm login with no arguments when already authenticated will display the token expiry and exit without re-authenticating.
| File | Contents |
|---|---|
~/.heyo/token.json | JWT access token, refresh token, expiry |
~/.heyo/.env | API key and auth server URL (API key login only) |
Use --auth-url or the --dev flag on the parent heyvm command to target a local auth server:
heyvm --dev login --email dev@localhost.com
This sends credentials to http://localhost:3001 instead of production.
When the user asks to log in or authenticate:
heyvm login command.When the user provides $ARGUMENTS, pass them directly to heyvm login. For example, /heyvm-login --api-key abc123 should run heyvm login --api-key abc123.
If $ARGUMENTS is empty, run heyvm login interactively (the CLI will prompt for credentials).