Morph Cloud

An agent on Morph reaches outside systems through what runs in its VM. Secrets stored in the Morph account come preconfigured in devboxes, an agent token can let the agent read and write its own devbox's secrets, and volumes serve shared files to any S3 client. There are no connectors, tool catalog or MCP gateway for an agent to call.

Sourcecloud.morph.so/docs/devboxes/agent-tokensread 2026-11-05

There is no workflow logic in Morph Cloud. Branching copies a running instance into many that continue from the same state, and TTLs stop or pause instances on a timer, but sequencing, retrying and routing an agent's steps stay in the customer's own code, which builds any fan out on these primitives.

Sourcecloud.morph.so/docs/concepts/mental-modelread 2026-11-05

No retrieval index or knowledge base over the customer's content comes with the platform. Volumes and the VM filesystem hold files an agent's code reads, and any retrieval runs as the customer's own software inside the instance.

Sourcecloud.morph.so/docs/documentation/overviewread 2026-11-05

Work in an instance has no approval step, consent checkpoint or escalation to a person. People can watch and step in by hand, since devboxes are shared live with the organization and open in VS Code, Cursor or a terminal over SSH, and a remote desktop guide serves a Linux desktop in the browser. Agent tokens limit what an agent can do to its own devbox but do not hold an action for review.

Sourcecloud.morph.so/docs/devboxes/sharing-and-collaborationread 2026-11-05

Organizations have admin and member roles with invitations, and one account can belong to several organizations. API keys act for the user, agent tokens confine an agent to one devbox and a set of scopes such as snapshots, HTTP services and secrets, and SSH public keys are registered with expiry dates, with an organization view of which keys have access. Morph's terms commit to encryption in transit and at rest, least privilege access and audit logging, and offer third party attestations such as SOC reports on request, with no certification named.

Sourcecloud.morph.so/web/legal/terms-of-serviceread 2026-11-05

The machine is measured and the agent is not. Each instance reports point in time CPU and memory use, usage and quota APIs break consumption down by service, command output streams back from exec calls, organizations can review which SSH keys have access, and the GitHub Actions console streams live events and logs for CI runs. Nothing traces or logs the steps an agent takes.

Sourcecloud.morph.so/docs/api-reference/get-instance-metrics-instance-instance-id-metrics-getread 2026-11-05

An agent's working state carries across sessions as machine state. A paused instance resumes with its memory intact, and a snapshot captures the whole running machine, processes included, so an instance booted from it carries on where the original stopped. Snapshot TTLs set how long saved states are kept, and volumes hold caches, checkpoints and datasets. This is machine state the developer manages, with no memory layer of stated scope that can be reviewed or deleted as memory.

Sourcecloud.morph.so/docs/developersread 2026-11-05

Morph Cloud runs as a hosted service with no choice of region and no self hosted or customer cloud option, even though Morph's terms refer to region availability.

Sourcecloud.morph.so/docs/documentation/overviewread 2026-11-05

Starting points come as templates and guides. Devbox templates bundle a base snapshot, build steps and integrations and can be shared with teammates by a short alias, and guides set up Claude Code workspaces, a browser based Linux desktop, Docker BuildKit, build caches and GitHub Actions runners. These are environments a developer builds from, not prebuilt agents a business adopts.

Sourcecloud.morph.so/docs/examples/claude-coderead 2026-11-05

A paused instance wakes without the customer's code calling it. With wake on HTTP, a request to an exposed service resumes the instance, and wake on SSH does the same for SSH sessions and exec calls, so an agent served from a Morph workspace starts when traffic arrives and pauses again when its TTL runs out. Morph's own guide builds agent workspaces this way. There is no scheduler or webhook.

Sourcecloud.morph.so/docs/documentation/instances/wake-onread 2026-11-05

The customer chooses the agents and models that run on Morph. Any CLI agent can run in a devbox, Morph's guide installs Claude Code with the customer's own Anthropic key, and model calls happen in the customer's code. Morph supplies the machines, not the models.

Sourcecloud.morph.so/docs/examples/claude-coderead 2026-11-05

Morph Cloud is driven through a REST API with a public OpenAPI specification, Python and TypeScript SDKs and the morphcloud CLI, which cover images, snapshots, instances, branching, devboxes, volumes, organizations, secrets, usage and SSH keys, and the CLI accepts plugins. Morph offers no MCP server.

Sourcecloud.morph.so/docs/api-referenceread 2026-11-05

There are no test cases, scoring or quality gates for an agent's behavior. Morph presents faster agent evaluations and capturing the exact state of a failed CI run as uses of snapshots and branching, with the datasets and scoring left to the customer's own harness.

Sourcecloud.morph.so/docs/developersread 2026-11-05

No browser or desktop for an agent to drive comes with the platform. Morph's remote desktop guide installs an XFCE desktop with VNC and a noVNC web client so people can use it in the browser, and an agent that needs a browser installs and drives one itself inside the VM.

Sourcecloud.morph.so/docs/examples/remote-desktopread 2026-11-05