Platform
Understand the Mogplex app, CLI, headless run surface, projects, sandboxes, and hosted API as one connected platform.
Mogplex has several product surfaces, but they share one platform: account state, GitHub coverage, reusable agents, model access, run history, sandbox state, and API-backed execution.
Start here when you need to understand where work should happen.
How Mogplex Fits Together
Object model from account state to GitHub coverage, repos, agents, routing, runs, sandboxes, and observability.
Mogplex App
Hosted control plane for account setup, GitHub coverage, repos, reusable agents, routing, sandboxes, and inspection.
Mogplex CLI
Terminal cockpit for repo-local work, live timelines, approvals, diffs, MCP, memory, models, and cost.
Headless Runs
Script and CI entry points for starting runs and tailing structured events without the interactive cockpit.
Projects and Sandboxes
Repo import, workspace launch, repo settings, preview runtimes, pinned workspaces, and stale sandbox cleanup.
Sandbox Setup Checklist
Confirm root directory, commands, ports, env, branch intent, managed access, and preview expectations before debugging runs.
Hosted API
Use the versioned public API for repositories, agents, models, sandboxes, automations, runs, and MCP.
API Quickstart
Authenticate, list repos, start a run, inspect events, cancel work, and list sandboxes from scripts.
How the platform fits together
- The app owns shared account setup, GitHub App coverage, routing, hosted state, and inspection.
- The CLI owns repo-local supervision: agents, timeline, approvals, diffs, model choice, cost, export, and attach mode.
- Headless runs use the same platform API when the job starts from CI, scripts, dashboards, or scheduled automation.
- Projects and sandboxes connect repo identity to execution state.
For the object model behind those surfaces, read How Mogplex Fits Together.