Welcome to Mogplex

Choose the right Mogplex starting point, platform area, capability, configuration path, guide, or reference page.

Mogplex is an agent workbench for software teams. These docs are organized by how the product is used: platform areas, capabilities, configuration, integrations, guides, and reference.

The web app, CLI, hosted API, and extension paths are still documented in full, but they are not the main decision tree. Start from the job you are trying to finish, then drill into the product surface that owns it.

Documentation index

Fetch the complete docs index at /llms.txt. Use /llms-full.txt when you need the full text of every docs page for an agent or external reader.

Start here

Quickstart

Connect GitHub, sync a repo, choose a routing surface, run locally, and inspect the first run.

How Mogplex Fits Together

Understand the object model from account state and routing to missions, tasks, Worktrees, Sandbox compute, runs, and observability.

Control Execution Environments

Choose Sandbox compute or a task Worktree, then use each lifecycle action without changing the other resource.

Common Use Cases

Pick the right Mogplex surface for review, triage, CI, mentions, local work, headless runs, sandboxes, and API usage.

GitHub Routing Cookbook

Use concrete recipes for mentions, PR review, issue triage, CI failure response, scheduled work, and direct run starts.

Troubleshooting

Debug setup, routing, models, CLI auth, sandboxes, API, and observability from the owning surface.

Observability Runbook

Trace failed, stuck, expensive, or noisy work from source surface to run events, tool calls, sandboxes, and API state.

How to Work With Mogplex

Write clearer requests for CLI runs, GitHub mentions, assignments, automations, and headless jobs.

Available Models

Understand the live model catalog, enabled models, defaults, plan access, CLI sync, and repo-level exclusions.

Model Selection and Cost

Choose models across settings, agents, automations, CLI runs, repo exclusions, and cost observability.

Plans & Billing

Coming soon: plan tiers, billing setup, included usage, limits, invoices, and account entitlements.

Support

Find the right troubleshooting path for setup, routing, models, CLI auth, sandboxes, integrations, and docs issues.

Product map

Core capabilities

Configure and extend

Connect your stack

Reference paths

The shortest reliable first-day path

  1. Open the web app and connect GitHub in Settings.
  2. Confirm the right user or org has Mogplex GitHub App coverage in Installations.
  3. Sync repos and open the target repo in Projects.
  4. Check or create the reusable agents you want in Agents.
  5. Choose the smallest routing surface that fits the job: Triggers, Assignments, or Automations.
  6. Install the CLI, run mogplex, and start a local task in the repo.
  7. Use Observability once work is actually running.

What working should mean

After the first hour, these should all be true:

  • Mogplex can see the repos you expect.
  • The repo owner has GitHub App coverage, not only OAuth visibility.
  • At least one reusable agent is configured the way you expect.
  • One local CLI run completes successfully.
  • You know whether the next job belongs in Triggers, Assignments, or Automations.

If one is still false, start with the Quickstart, Settings, Installations, Mogplex App, or Mogplex CLI, depending on where the setup breaks.

Edit on GitHub

On this page