Install Heyo

MCP server

The quickest way in: point your coding agent at Heyo’s hosted MCP server and it can deploy, run commands in VMs, commit to repositories, and read logs — nothing to install.

First, create a token in your namespace: open the app-lb dashboard and use the Get started card, or go to App-tokens → New token. The token is confined to your namespace and starts with applb_.

# Add the Heyo MCP server to Claude Code
claude mcp add --transport http heyo https://mcp.heyo.work/mcp \
  --header "Authorization: Bearer applb_…"

# Or, for other MCP clients (.mcp.json or client settings)
{
  "mcpServers": {
    "heyo": {
      "type": "http",
      "url": "https://mcp.heyo.work/mcp",
      "headers": { "Authorization": "Bearer applb_…" }
    }
  }
}

heyctl

The command line for apps running on Heyo. Deploy them, scale them, read their logs, and publish the images they boot from — all with the one login your namespace gives you.

# Linux (x86_64) — install heyctl
curl -fsSL https://heyo.computer/heyctl/install.sh | sh

# Log in with the token for your namespace, then look around
heyctl login --server <your admin URL> --token-stdin
heyctl get deployments
heyctl logs my-app

• Deploy from a spec — heyctl apply -f app.yaml creates or replaces a deployment.
• Publish your own images — heyctl artifact push uploads a VM image under your namespace, ready to deploy.
• See what is running — status, logs and resource use for every deployment.

Linux x86_64 builds today. Other platforms are coming soon.

heyvm & heyvmd

Spin up and manage agent sandboxes on your own machine. The installer puts the heyvm CLI and its daemon, heyvmd, side by side — one command to install, another to launch your first VM.

# macOS & Linux — install heyvm and heyvmd
curl -fsSL https://heyo.computer/heyvm/install.sh | sh

# Log in and launch your first sandbox
heyvm login
heyvm create my-agent
heyvm exec my-agent -- bash

• Millisecond boot — sandboxes start in well under a second, no waiting around.
• Snapshot & restore — save VM state and resume exactly where you left off.
• Bring your own image — use any OCI-compatible container image as your base.
• Local or cloud — run on your machine or push to hosted Heyo infrastructure.

Skills

Skills are reusable instruction packages that give AI agents specialized Heyo capabilities — deploy to a sandbox, manage VMs, run SQL, expose ports, and more. The CLI ships them straight into your project so your agent knows exactly what to do.

# Install the Heyo skills into ./.claude/skills
heyvm install-skills

# Or target a different directory
heyvm install-skills --path ./my-project/.claude/skills

# Already have the skills CLI? Pull them straight from the registry
npx skills add heyo-computer/skills

Skills land in .claude/skills/ in the current project, where Claude Code (and other ACP agents) detect them automatically.

CI

git submit sends a change to Heyo CI straight from your clone — committed work, local commits, or uncommitted edits — and runs your .ci/workflows/*.yml against it in fresh VMs. No push, no branch, no waiting on a hosted runner.

# macOS & Linux — install the git submit subcommand
curl -fsSL https://heyo.computer/git-submit/install.sh | bash

# Register the repo on your CI dashboard's /repos page, then paste its two lines
git config ci.endpoint https://ci.<your region>.heyo.work
git config ci.token    cis_…

# Submit from the repository root
git submit --dry-run   # see what would be sent
git submit             # run your workflows on HEAD
git submit --dirty     # include uncommitted changes

• Sends a patch, not your repo — only the diff against a commit already on your origin leaves your machine.
• Exactly what you tested — the runner checks that the build tree matches yours before it starts.
• Run one workflow — git submit --only <name> skips the rest.
• Stay current — git submit --upgrade reinstalls the latest client.

Needs bash, git, curl and python3. Installs into ~/.local/bin; set GIT_SUBMIT_INSTALL_DIR to choose another directory.