docs
// Execution Management (EEM)

Operations

The Operations page at /ops is where owners and operators decide waiting tool calls, follow runs as they happen, and see which Erebine Execution Managers (EEMs) serve which workspaces.

Overview

Operations is for a project's owners and operators. Members see no link to it. The page has two tabs, Activity (/ops) and Topology (/ops/topology), plus an Agents link to the EEM list at /agents/eem.

Every /ops path is a signed-in dashboard route for the project you have open. For the project-scoped execution API, use /:project_id/v1/exec/*, documented in the EEM overview.

Setup Steps

Until execution is fully set up, Activity opens with "Set up execution": five steps, each marked done or to do, with a link to the place that completes it.

  1. Enroll an execution agent: done once an EEM is online.
  2. Create an execution workspace: done once the project has an operational workspace.
  3. Have an agent serve it: done once an online EEM declares an operational workspace by its name.
  4. Link a chat to it: done once a chat runs its tools in an execution workspace.
  5. Make sure someone is told: done once an approval request can reach an approver by email link, browser or iPhone notification.

The steps disappear once all five are done.

Activity

One list of tool runs, newest first or grouped by state, with columns Tool, Status, Risk, Workspace, Agent, Chat, Requested, Duration, Decided by and Decided at. It stays current while the page is open.

  • State: All, or any mix of Waiting, Running, Failed, Timed out, Rejected, Cancelled and Succeeded. Waiting and Running show how many calls are in them now. Failed includes runs lost to a restart.
  • Show: every run, irreversible runs only, or runs a person or the decider decided.
  • Sort: newest first, or by state: waiting calls first, then running, then failed, timed out, rejected, cancelled and succeeded, newest first within each.
  • A change applies at once without reloading the page, and the address bar keeps a link to it. The browser remembers your choice when preferences are on and shows it the next time you open /ops.
  • Search: by tool, workspace, EEM or chat.
  • Waiting rows show how long the call has waited and when its deadline falls. Opening one shows the decision dialog: the call named by its tool, its risk, EEM, workspace, requester, chat and deadline, what the tool does, its arguments and request, the decider's verdict when it was asked, an optional note, Approve, Reject and Cancel call. An irreversible call needs I approve typed first. A write call can also be approved with the "Also allow <domain> writes in <workspace> from now on" switch, a standing permission (see Standing Permissions).
  • Other rows open the run panel: status, risk, workspace, EEM, chat, requester, requested time, duration, who decided and when, any error, what the tool does, the request, the arguments, the result, and a timeline from request to finish. Times read relative, with the timestamp on hover.
  • Deep links: /ops?invocation=<id> opens that run. Approval notifications and webhooks link here.

Keyboard: Alt + / search, Alt + F next state (All, then each state alone), Alt + A approve and Alt + R reject the focused run.

To cancel a waiting or running call, use Cancel call on its chat card or erectl exec cancel <invocation-id>.

Topology

A graph of the project's EEMs, shared EEMs and operational workspaces. Edges show which EEM is bound to which workspace, which bindings are paused, and which workspaces an EEM advertises. Drag a node to move it; Enter on a workspace opens its settings, and on an EEM, its row on Agents.

Show or hide each kind: Agents (Alt + A), Shared agents (Alt + S), Workspaces (Alt + W), Paused bindings (Alt + P) and Advertises (Alt + D). Fit (Alt + F) frames the graph; Reset (Alt + R) restores it. A screen reader gets the same bindings as a table.

From a shell, erectl ops topology prints the same graph as three tables: the EEMs, the operational workspaces, and one row per binding or advertised workspace. -o json prints the nodes and edges.

Health Line

Under the page title, one line sums up execution:

2 EEMs online - 1 waiting 4m - 0 failures in the last hour

The count of online EEMs, the number of waiting calls and the age of the oldest, and the runs that failed in the last hour. A rejection or a cancel is not a failure.

From a shell, erectl ops health prints the line, the counts behind it and, when execution is degraded, why. -o json prints the counts as fields.

erectl ops health erectl ops topology -o json

Both need an owner's or operator's API key with the management or execution scope, and show what that person sees on Operations: an operator sees only the workspaces they can open, and a key limited to some workspaces sees only those.

Audit Export

Export audit on Activity downloads the runs for a date range, up to 31 days, as CSV or JSONL. Only owners and operators can export. The file holds the rows Activity would show you, with arguments and results redacted as the run panel shows them. The last three columns say who approved a run: approval_source (person, policy, decider or autonomous) and, for a run autonomous trust approved, who turned the trust on and when (autonomous_enabled_by, autonomous_enabled_at). In CSV, a cell that starts with =, +, -, @ or a tab begins with ' so a spreadsheet shows it as text.

GET /ops/api/activity/export?format=csv&from=2026-10-01&to=2026-10-14

Live Updates

Activity keeps itself current over Server-Sent Events from /ops/api/stream. The events are change signals: on each one the page fetches the changed row again. The stream is a signed-in dashboard route, not part of the public API.

EventWhen it fires
ox.connection.connectedThe stream opened.
ox.connection.heartbeatAbout every 30 seconds while the stream is open.
ox.execution.startedA run was queued or started.
ox.execution.completedA run finished.
ox.execution.failedA run failed, timed out, or was rejected or cancelled.
ox.approval.requestedA call started waiting for approval.
ox.approval.decidedA waiting call left the queue by a decision or a cancel.
ox.approval.timed_outA waiting call timed out.

Approval Links

Approval emails carry one-time Approve and Reject links to /ops/approval/:id, available when the deployment enables one-time approval links. That page works without signing in. Each link is bound to the person it was sent to, works once, and is refused if that person can no longer decide the call.

The rules for who decides, what waits and when a call times out are on EEM approvals.