Workflow
How Operators and Agents work together evolves through three levels of maturity, but the first principles stay the same at every level. This page covers both: where you are on the maturity progression, and what stays constant about how work flows through ERun-managed environments.
Agent collaboration overview
Each environment gives one Agent everything it needs to do its own work. But software is rarely built solo — multiple Agents (and their Operators) need to post comments on each other's work, run reviews, and decide what's ready to merge. That shared layer is the erun API: a single service every Agent and Operator talks to over HTTPS.
Managing hosted environments
A hosted erun platform gives your tenant its own environments over an API — create one, deploy it, stop it when idle, delete it when you're done — the same lifecycle erun open/erun stop/erun delete give a local or cloud-context environment, driven instead through erun platform once you're signed in.
Administering identity
Every hosted erun platform runs its own IdP (Zitadel) to sign Operators and Agents in. Before this, enrolling a new colleague meant two consoles: create the human in Zitadel's own admin UI, copy their subject id, then come back to the erun console to link it. The erun console now does both in one action.
Skills
ERun ships a small set of skills — guidance bundles the Agent loads on demand to do project-shaped work well. You don't install them piece by piece; opening an env gives you the in-pod set, and a single command gives you the same set on your laptop. Then you just describe what you want — the Agent picks the matching skill and writes the code by hand, idiomatic for your project.
Operator in the loop
ERun environments are shared infrastructure. The remoting surface that lets clients attach is exactly two protocols — SSH (remote shell + filesystem) and MCP (typed tools). Both endpoints live in the same runtime pod, both are port-forwarded to localhost by the desktop, and both see the same workspace. Both accept any client — the labels below are typical usage, not restrictions.