Deploy SAM
All Features Sessions That Wait

Come back days later to the same session

Sessions you leave idle go to sleep and keep their work for up to seven days.

  • Sessions normally restore home and repository state from a 7-day snapshot; VM fallback preserves the transcript and a verified Git recovery point
  • Agents dispatch subtasks to peers and send durable messages that can interrupt a busy agent
  • App deployments run Compose releases with environments, configuration, and logs
  • Six agent harnesses: Claude Code, Codex, Gemini CLI, Mistral Vibe, OpenCode, Amp
Read the guide
A sleeping chat session being woken: a banner reads Recreating your workspace, the transcript is intact, and the composer reads Waking the agent, your message will be deliveredA sleeping chat session being woken: a banner reads Recreating your workspace, the transcript is intact, and the composer reads Waking the agent, your message will be delivered

Close the tab. The session waits.

SAM normally restores the agent’s home directory and repository work from a verified snapshot for up to seven days. After repeated snapshot failures, an idle VM session can sleep with its transcript and a verified Git recovery point instead. SAM shows a notice, and the agent starts fresh on wake. Without a safe recovery point, sleep is blocked.

A finished chat session in the Sleeping state, with the full transcript still visible and a composer that reads Send a message to wake the agentA finished chat session in the Sleeping state, with the full transcript still visible and a composer that reads Send a message to wake the agent Sessions normally sleep after idle turns and wake from a seven-day snapshot

Agents that dispatch to each other

An agent can dispatch a subtask to a peer and send a durable message that interrupts a busy agent instead of waiting behind it. Work keeps moving even when one agent is heads-down on something else.

Task Hierarchy view showing a running parent task with three dispatched subtasks: one completed with a PR opened, one queued and blocked on sign-off, and one runningTask Hierarchy view showing a running parent task with three dispatched subtasks: one completed with a PR opened, one queued and blocked on sign-off, and one running A parent task and the subtasks it dispatched, with live status for each

Deploy what the agent built

App deployments turn a Compose release into a running app. Each environment has its own deployment node, public routes, configuration, logs, and volumes, managed from the same project — and a release can be submitted by an agent task. No separate deployment pipeline to wire up.

Deployment environment detail for staging showing release v14 applied and submitted by an agent task, health checks for app, node, provider, routes, disk, and config, and a public routeDeployment environment detail for staging showing release v14 applied and submitted by an agent task, health checks for app, node, provider, routes, disk, and config, and a public route A release the agent submitted, serving on its own node with health checks and a public route
Previous Schedules & Triggers Next Full Visibility & Control

Ready to try SAM?

SAM is open source. To deploy it, you need a Cloudflare Workers Paid plan, a domain on Cloudflare, and a GitHub account.

Deploy SAM Read the Docs