Skip to main content

Devboxes for development

Devboxes are the best default for development on Morph Cloud:

  • VSCode/Cursor integration: one-click connect from the Devboxes UI.
  • SSH when you want it: treat your devbox like a real machine.
  • tmux integration for CLI agents: automate interactive sessions while keeping a human in the loop.
  • “Infinitely many workspaces”: use snapshots/branching to spin up parallel workspaces from a known-good state.

Quick start: open a devbox in your editor​

  1. Create a devbox: https://cloud.morph.so/web/devboxes/new
  2. Open it in VSCode or Cursor from the devbox actions menu.
  3. Commit early and often inside the devbox (it’s a real VM).

SSH workflow (CLI)​

export MORPH_API_KEY="..."

# Start a devbox from a template (pick one you have access to)
morphcloud devbox template list
TEMPLATE_ID="<template-id>"
DEVBOX_ID=$(
  morphcloud devbox start "$TEMPLATE_ID" --name "dev" --json | jq -r '.id'
)

# Run commands via SSH
morphcloud devbox ssh "$DEVBOX_ID" uname -a

Automate CLI agents with tmux (API)​

Devboxes expose a tmux API that lets you programmatically:

  • create sessions
  • send keystrokes
  • capture state

This is a good fit for running CLI agents (Codex, Claude Code, Gemini CLI) with human-in-the-loop supervision.

See the tmux quickstart in Getting started.

Parallel workspaces (snapshots + branching)​

When you have a devbox in a “known-good” state (tooling installed, repo checked out, services running), checkpoint it. Then you can spin up parallel workspaces from that checkpoint for:

  • separate feature branches
  • code review / debugging sandboxes
  • “one workspace per agent”

If you need direct control over snapshot primitives (and very high fan-out), use the primitives path: