Agent reference overview
This section is the spec — for Agents. Field-by-field schemas, error codes, audit-trail formats, OIDC details, rate limits, build-path resolution algorithms. Everything an Agent needs to operate ERun without guessing.
Concepts
11 items
MCP protocol + tools
MCP is the typed-tool surface for an environment. Where shell-level work happens over SSH, MCP carries typed actions — inspection (idle, doctor, list, version, observe), operational wrappers around the CLI (build, push, deploy, release, expose, init, delete, and the cloud/context/platform/review families), and an escape hatch (exec_raw). Agents (and any other code that wants structured, auditable access) talk to ERun over MCP; every call lands in the same audit trail the Operator reads. The full tool index at the end of this page lists every registered tool.
Agent patterns
Common patterns for Agent authors. None are required — ERun's primitives are flexible enough that an Agent can implement any of these on top of the MCP tools and the erun API. What follows is the set most teams converge on.
erun API
6 items
Platform spec
9 items
Configuration spec
4 items