Quickstart
Install, sign in, start a run, and confirm the CLI cockpit is working end-to-end.
The shortest useful loop:
- install the binary
- start
mogplex - sign in (in-app)
- start a run with
/run - watch agents and timeline; approve or kill as needed
1. Install
See Installation.
2. Start the cockpit
mogplexIf you are not authenticated, the in-app login screen appears. Pick one:
- Sign in with Mogplex — opens a browser for account-backed login. This reuses your plan-backed model access, synced model catalog, and remote MCP definitions.
Stored credentials live in ~/.mogplex/auth.json (file mode 0600).
The CLI ships to end users — auth and config are in-app. Environment variables exist as escape hatches only. See Configuration and Flags.
3. Start a run
In the composer:
/run review the staged diff for regressionsThe Agents panel populates as core spawns workers. The Timeline streams structured events. The Header shows model, mode, run status, and transport health.
4. Drive the run
| Action | Command |
|---|---|
| Pause / resume | /pause then /resume |
| Kill the run | /kill |
| Switch models | /model (opens picker drawer) |
| Open the diff | /diff |
| See cost so far | /cost |
| Open MCP detail | /mcp |
| Inspect memory | /memory |
| Export the run | /export |
| List slash commands | /help |
| Quit | /quit (alias /exit) |
Full reference: Commands.
5. Approvals
If the active permission mode is approval (the default), tool calls that touch the workspace pause and surface in the Approval drawer. Approve or reject inline. See Concepts → Approvals and Concepts → Permissions.
6. Attach to an in-flight run
If a run was started somewhere else (web app, CI, another shell), you can pull up its cockpit with:
mogplex --attach <runId>See Concepts → Attach.
What "working" looks like
mogplexopens cleanly to the cockpit (or to the login screen on first run).- Header shows
transport: nominalonce core is connected. /run <task>produces agents in the Agents panel and events in the Timeline.- Approvals appear in the Approval drawer when the run touches the workspace.
- Ctrl+C does not quit — it logs a soft-interrupt. Press it twice within 1500ms (or type
/quit) to exit.
Common first-run issues
- Login succeeds but no models available — check Available Models and the account plan. Account-backed login inherits managed hosted access.
- Header says
transport: offline— core is unreachable. Check network and retry; the daemon transport surfaces a reconnect banner. - A slash command "doesn't work" — check
/helpfor the actual registry.
Read next
- Concepts → Architecture for the mental model.
- Concepts → Permissions for
approvalvsautomodes. - Reference → Keybindings for focus rotation and exit behavior.
- Guides → Authentication for credential precedence.