You wouldn't trust a deploy pipeline you couldn't inspect. Same rule here. This is the full path of a single run — from the event that wakes it to the deploy that closes the loop — and what is guaranteed at every station.
timestamps from a representative nightly-deps run · your repo · your gates
T+00:00.0 · STATION 00
An issue opens. CI fails. A schedule fires. Someone asks in Slack. A standing assignment comes due. Mogplex catches the event, dedupes it, and assembles the context that matters: the repo, the thread, the logs, the diff.
▪ held — one event, one run. Nothing polls your repo, nothing runs on your machines.
T+00:00.8 · STATION 01
The pipeline you wired decides everything up front: which repo, which agent (Claude Code, Codex), what context it gets, and which gates its output must pass. That decision is recorded before any work starts.
▪ held — every run traces back to the exact event that caused it.
T+00:04.2 · STATION 02
A fresh microVM boots with a clone of your repo. Nothing is shared between runs, and the sandbox dies when the run ends. Compute is covered during the private beta — there's no cloud account to connect before your first run.
▪ held — per-run isolation. Your code never executes on shared infrastructure you can't see.
T+00:06.5 · STATION 03
The agent writes code, runs your tests, and calls your MCP tools, iterating until the work holds together or its budget stops it. Model access is provided by Mogplex, and every call — model or tool — is metered and logged.
▪ held — open any live run call-by-call. Approve the next tool call, redirect the plan, or kill it.
T+04:12.9 · STATION 04
Output leaves the sandbox only one way: as a PR, a check run, or a merge that passed the gates you configured. Branch protections always rule — Mogplex cannot bypass required reviews, required checks, or protected branches.
▪ held — nothing ships that your rules wouldn't let a human ship.
T+04:40.1 · STATION 05
When the change deploys, the deploy reconciles back to the run, the run back to the event. The audit trail reads end to end: what asked for this, what did the work, what it cost, who approved it. Then the pipe loops back to trigger.
▪ held — “who did this and why” always has an answer.
MODELS
Model access included. Pick the agent and model per pipeline; every call is visible call-by-call.
SANDBOX
Every run gets a fresh, isolated microVM. It dies with the run, and nothing is shared between runs.
GATES
Branch protections, required checks, and required reviews always win. Autonomy is a dial you set per pipeline.
SOURCE
The CLI is open source under MIT. Read what authenticates against your repos before you run it.
RECONCILED. the deploy points back at the run ↺
SHEET 03 — END
private beta, approving in batches. free while we learn what you need.