---
title: VM templates
description: Ready-to-run Beam VMs: OpenClaw and Hermes Agent, a devbox for Claude Code and Codex, a desktop for computer use, Blender on an RTX 4090 and a video studio for agents. Start one with a single command from your terminal or your coding agent.
---

# VM templates

This is Beam's VM template catalog. Each template is a public Beam VM template: a disk with the software installed and set to start on boot. Starting one creates an independent VM in the user's workspace (4 vCPU · 8 GiB · 50 GiB disk, plus a GPU where the table lists one), billed per second while it runs. The same catalog is on the web at [www.beam.cloud/templates](https://www.beam.cloud/templates) and as JSON at [www.beam.cloud/templates.json](https://www.beam.cloud/templates.json).

---

## Start a template

- **Fresh machine:** `curl -fsSL https://www.beam.cloud/install | sh -s -- --template <slug>` installs the CLI, signs in through the browser, connects the user's coding agents and starts the VM. It asks before creating the VM; add `--yes` once the user has approved.
- **CLI already set up:** `beam vm new <slug> --template <template_id>`. Add `--cpu` and `--memory` to change the size.
- **MCP:** call `create_vm` with `{"name": "<slug>", "template": "<template_id>"}`.
- **Open it:** `beam vm terminal <name>` or `beam vm desktop <name>`, as each template says.

Tell the user which template you chose and its hourly price before creating it, from the VM and GPU rates in [pricing.md](https://www.beam.cloud/pricing.md). Templates ship signed out of every account, so once the VM is ready, give the user its first-run step: signing in is theirs to do. Never ask the user for a token.

---

## Templates

| Template | Slug | Category | VM | Template ID |
| --- | --- | --- | --- | --- |
| OpenClaw | `openclaw` | Personal agents | headless | `085a234c-5974-4f12-8cec-bf5da8258ea0` |
| Hermes Agent | `hermes-agent` | Personal agents | headless | `eb8f47d8-4a7b-4dd9-8949-4a1c843a2236` |
| Agent devbox | `agent-devbox` | Coding agents | desktop, Docker | `a1da2d96-f807-4f2b-9ccd-08ce9c695712` |
| Computer use | `computer-use` | Coding agents | desktop | `a10dbe30-6dec-4e7b-ab41-4e86d4cad7cf` |
| Blender | `blender` | Creative | desktop, RTX 4090 | `20717ff4-d7b2-4825-b341-de1faf7bb7d5` |
| Video studio | `video-studio` | Creative | desktop | `71342c8e-c38d-49f0-8a6f-e51e4b06a853` |

### OpenClaw (`openclaw`)

The personal agent you message on WhatsApp, Telegram or Slack, on a VM that stays on when your laptop doesn't.

- OpenClaw, ready to onboard
- Its gateway as a service once you onboard, running from boot
- Node.js 24

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template openclaw
# CLI already set up
beam vm new openclaw --template 085a234c-5974-4f12-8cec-bf5da8258ea0
# Open it
beam vm terminal openclaw
```

MCP `create_vm` arguments:

```json
{"name":"openclaw","template":"085a234c-5974-4f12-8cec-bf5da8258ea0"}
```

**First run:** Run `openclaw onboard --install-daemon` to sign in to a model, with a ChatGPT or Claude subscription or an API key, and connect your chat apps.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/openclaw](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/openclaw)

### Hermes Agent (`hermes-agent`)

Nous Research's agent that remembers, learns skills and answers on Telegram, Discord, Slack and WhatsApp.

- Hermes Agent with its tools and skills
- Its messaging gateway
- A browser for web tasks

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template hermes-agent
# CLI already set up
beam vm new hermes-agent --template eb8f47d8-4a7b-4dd9-8949-4a1c843a2236
# Open it
beam vm terminal hermes-agent
```

MCP `create_vm` arguments:

```json
{"name":"hermes-agent","template":"eb8f47d8-4a7b-4dd9-8949-4a1c843a2236"}
```

**First run:** Run `hermes setup` to pick a model and connect your chat apps, then `hermes gateway install` to keep it answering.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/hermes-agent](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/hermes-agent)

### Agent devbox (`agent-devbox`)

Claude Code, Codex and the Cursor CLI on a VM that keeps working after your laptop closes. Drive Claude Code from your phone.

- Claude Code, Codex and the Cursor CLI
- Remote Control in tmux, for the Claude app
- Docker, the GitHub CLI, Node.js 22, uv and Python 3.12
- Google Chrome on a desktop

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template agent-devbox
# CLI already set up
beam vm new agent-devbox --template a1da2d96-f807-4f2b-9ccd-08ce9c695712
# Open it
beam vm terminal agent-devbox
```

MCP `create_vm` arguments:

```json
{"name":"agent-devbox","template":"a1da2d96-f807-4f2b-9ccd-08ce9c695712"}
```

**First run:** Sign in with `claude`, then run `claude-remote` and open the session in the Claude app on your phone.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/agent-devbox](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/agent-devbox)

### Computer use (`computer-use`)

A Linux desktop that Claude Code and Codex operate, clicking through apps and websites while you watch.

- Claude Code and Codex
- agent-desktop, for apps on the desktop
- agent-browser, for websites in Chrome
- Their skills, so the agents know how to use them

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template computer-use
# CLI already set up
beam vm new computer-use --template a10dbe30-6dec-4e7b-ab41-4e86d4cad7cf
# Open it
beam vm terminal computer-use
```

MCP `create_vm` arguments:

```json
{"name":"computer-use","template":"a10dbe30-6dec-4e7b-ab41-4e86d4cad7cf"}
```

**First run:** Sign in with `claude` or `codex` and give it a task, then watch with `beam vm desktop computer-use`.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/computer-use](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/computer-use)

### Blender (`blender`)

Blender on an RTX 4090 in your browser, for Claude Code, Codex or any MCP client to build and render scenes in while you watch.

- Blender 4.5 LTS full screen, streamed over WebRTC
- An RTX 4090 for the viewport and Cycles, which renders with OptiX
- MCP for Blender, registered and running
- A starter project in /workspace

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template blender
# CLI already set up
beam vm new blender --template 20717ff4-d7b2-4825-b341-de1faf7bb7d5
# Open it
beam vm desktop blender
```

MCP `create_vm` arguments:

```json
{"name":"blender","template":"20717ff4-d7b2-4825-b341-de1faf7bb7d5"}
```

**First run:** Run `beam vm port-forward blender 8082` and add `http://127.0.0.1:8082/mcp` to your agent as an HTTP MCP server.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/blender](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/blender)

### Video studio (`video-studio`)

Claude Code and Codex make videos from code with HyperFrames and Remotion, rendered on the VM.

- HyperFrames and Remotion, with their skills
- A starter project for each in /workspace
- Claude Code, Codex and FFmpeg

```bash
# Fresh machine: install the CLI, sign in, connect agents, start the VM
curl -fsSL https://www.beam.cloud/install | sh -s -- --template video-studio
# CLI already set up
beam vm new video-studio --template 71342c8e-c38d-49f0-8a6f-e51e4b06a853
# Open it
beam vm terminal video-studio
```

MCP `create_vm` arguments:

```json
{"name":"video-studio","template":"71342c8e-c38d-49f0-8a6f-e51e4b06a853"}
```

**First run:** Sign in with `claude` or `codex` and describe the video you want.

Recipe: [https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/video-studio](https://github.com/beam-cloud/beta9/tree/main/sdk/examples/vm/templates/video-studio)

---

## Questions

### How is a template billed?

Like any Beam VM: per second for CPU, memory and any GPU while it runs, plus its disk. Templates start at the default size, 4 vCPU and 8 GiB of memory with a 50 GiB disk, and Blender adds an RTX 4090. Stop or pause the VM and its compute charges stop; a GPU VM stops rather than pauses.

### What do I get when I start one?

An independent VM in your workspace, booted from a copy of the template's disk. What you change stays on your VM: nothing flows back to the template, and later versions of the template don't change your VM.

### Why does it start signed out?

Everyone who starts a template gets a copy of the same disk, so it carries no accounts, API keys or chat apps. Each template's first step signs you in on your own VM, and those sign-ins stay on its disk. The terminal and desktop are only open to people signed in to your Beam workspace.

### Can I change the size?

Yes. Add `--cpu` and `--memory` to `beam vm new` along with `--template`, for example `beam vm new devbox --template ID --cpu 8 --memory 16384`.

### How do agents use this page?

https://www.beam.cloud/templates.md lists every template with its ID, commands and the arguments for Beam's MCP `create_vm` tool, and https://www.beam.cloud/templates.json has the same data as JSON. The installer looks up `--template SLUG` in that list.
