Desktop app overview
The ERun desktop app is how most people use ERun day-to-day. It runs on macOS and Windows and gives you a single control panel for everything: your projects, your environments, the Agents attached to them, and the cloud machines that back them.
Control panel
The sidebar and its environment rows are where most sessions with the desktop app start and end — a live status for every project and environment, without typing a command.
Deploying a version
An environment's settings → Runtime tab is where you point an environment at a published version, choose the chart it installs, and keep a fleet of environments current.
Resources and usage
Below an environment's resource sliders, two readings tell you what the environment itself is doing — separate from what the node underneath it looks like.
Reviews
The tenant dashboard is where the desktop surfaces your hosted tenant: its reviews, and — on a separate tab — the tenant's own registration state.
Activities and recovery
Every deploy, open, and build the desktop runs lands in the Activities panel, and a failed one carries the evidence and the recovery actions right there instead of sending you to a terminal.
Settings and ports
- Settings in one place. Runtime sizing, AI tooling configuration, port mappings, SSH keys, and cloud bindings — all editable from one screen per environment.
Orchestrators
Above your environments, the sidebar's ERUN section lists your host-side orchestrators — AI sessions that coordinate work across the environments you link to them. For a remote-agent or local-agent environment that means reviewing its code on your machine and delegating every change to the Agent inside it; for a host environment it means working in that environment's directory directly, since a host environment is a plain directory with no pod and therefore no Agent in there to delegate to and nothing that syncs over your edits; for a runtime environment, linked with the Runtime role below, it means operating that environment directly instead. Open an orchestrator's … menu to manage it: restart, delete, or reveal the guidance it operates under.
Diagnostics console
The panel at the bottom of the terminal area follows whatever you're looking at, so it always has real evidence rather than a blank pane:
Terminals and editors
Opening an environment in the desktop is opening it in your editor of choice, backed by terminals that keep running even while you're looking elsewhere.
Working with an Agent
Works with or without an Agent
Workspace sync
For a remote-agent env, the worktree lives in the pod. Workspace sync mirrors it down to a folder on your machine so you can review and act on it host-side — open it in a host IDE, read the synced files, and run binaries the Agent built in the pod — without reaching into the pod for every step. It's the piece that makes an agent-driven env comfortable on Windows, where the pod-side worktree isn't directly openable by a host editor.
Contribute to ERun from any environment
The titlebar's Contribute toggle (the git-fork icon) lets you patch ERun itself without leaving the env you're working in. It is available for any non-erun agent env (local-agent or remote-agent); it is hidden for runtime envs and for the special erun tenant.