envend docs

envend is an environment gateway. A harness asks it for a Linux machine, it makes one on whichever provider you connected, and it connects you to that machine over a single encrypted tunnel — a filesystem mount, a shell, and any port you choose to publish.

If you have never used it, read Concepts first: it defines every word the rest of these pages use. If you just want it working, go straight to From a harness or The CLI.

Guides

Concepts

The four planes, a sandbox's lifecycle, the capability vocabulary, the tunnel and the one egress hole, identity, workspaces and profiles, and who owns which file.

From a harness

Registering the MCP endpoint with Claude Code, Codex or any MCP client; the instruction block a harness needs; working on the mount; running over ssh.

The CLI

Every envend command, what it does, and where its configuration lives.

Profiles & workspaces

The four strings that set a machine up, who they run as, where a command lands, and the omega profile as a worked example.

Sharing a port, linking a file

How a sandbox with no public port ends up on a public URL, and what it costs.

Connectors

Writing one: the twelve callbacks, the capability vocabulary, and what a connector is not allowed to decide.

Reference

MCP tools

All thirteen tools and every argument, as the gateway describes them to a model.

The envd contract

Every variable a machine is booted with, and which part of the agent reads it.

FAQ

The questions that come up first, answered against what the code does today.

Elsewhere

The living topology diagram — every component, every wire, and five scenarios. The repository, where the long-form design notes live in docs/.