# Quickstart (/quickstart)



Use this path when you want the first credible Mogplex setup for one repo.

The goal is not to configure every capability. The goal is to prove that
Mogplex can see the repo, has the right GitHub App coverage, can run locally,
and can route the next hosted job through the smallest surface that fits.

## 1. Connect the account [#1-connect-the-account]

Open [Settings](/web/settings), sign in, and connect the account state Mogplex
needs before it can do useful work:

* GitHub identity
* GitHub App coverage for the user or org that owns the repo
* plan-backed model access
* managed sandbox access when the repo needs previews or workspaces
* CLI access tokens if you plan to use the terminal cockpit
* Slack workspace and channel links if work should start from Slack
* shared connections and MCP definitions, if the repo needs external tools

GitHub sign-in alone does not give Mogplex repository access. The repo owner's
GitHub App installation must be linked to you: install the App on your personal
account, or on an org where you are an org owner. Use
[Installations](/web/installations) to confirm coverage before debugging
triggers or automations. The
[GitHub integration guide](/integrations/github) explains the full setup model.

## 2. Open the repo [#2-open-the-repo]

Open **Settings → Repositories** and select **Sync GitHub**. Then open Command
Center and pick the target repo in the project picker. See
[Projects](/web/spaces).

Command Center is where hosted work starts. Check that the repo appears once,
belongs to the expected owner, and has the coverage state you expect. If the repo needs sandbox-backed previews, confirm the account plan has
managed sandbox access before debugging workspace launch.

## 3. Check agents and models [#3-check-agents-and-models]

Open [Agents](/web/agents) and confirm at least one reusable agent is ready for
the job. Use [Available Models](/web/models) if model pickers, agents,
automations, or CLI runs do not show the models you expect.

Use [Agent Authoring](/configure-and-extend/agent-authoring) when the agent's
job, slug, prompt, model, rules, or routing fit is still unclear. Use
[Model Selection and Cost](/guides/model-selection-and-cost) before connecting
a high-volume route to a model choice.

## 4. Choose the smallest routing surface [#4-choose-the-smallest-routing-surface]

Use the lightest surface that matches the job:

| Job shape                                                    | Start here                                                             |
| ------------------------------------------------------------ | ---------------------------------------------------------------------- |
| One GitHub event should wake one agent                       | [Triggers](/web/triggers)                                              |
| One repo owns recurring or standing work                     | [Assignments](/web/assignments)                                        |
| The work needs branching, delays, drafts, or parallel agents | [Automations](/web/automations)                                        |
| The event starts in GitHub and you need a recipe             | [GitHub Routing Cookbook](/guides/github-routing-cookbook)             |
| The request starts from Slack                                | [Slack](/integrations/slack)                                           |
| You are not sure yet                                         | [Choose the Right Routing Surface](/web/guides/choose-routing-surface) |

## 5. Run locally [#5-run-locally]

Install the [Mogplex CLI](/cli/installation), then run:

```bash
mogplex
```

The CLI opens the terminal cockpit for live agents, timeline events, approvals,
diffs, MCP, memory, model selection, cost, and run control.

For scripted or CI-driven work, use [Headless Runs](/cli/automation/headless-runs)
instead of the interactive cockpit. Use [API Quickstart](/reference/api#quickstart)
when another system should start and inspect runs directly.

## 6. Verify the run [#6-verify-the-run]

Use [Observability](/web/observability) once work is running. A healthy first
pass should show:

* the repo you expected
* the surface that started the work
* model calls and token usage
* tool calls and sandbox activity when relevant
* enough status detail to understand whether the run is active, blocked,
  complete, or failed

## Read next [#read-next]

<Cards>
  <Card title="How Mogplex Fits Together" href="/https/docs.mogplex.com/platform/how-mogplex-fits-together" />

  <Card title="GitHub Routing Cookbook" href="/https/docs.mogplex.com/guides/github-routing-cookbook" />

  <Card title="Slack" href="/https/docs.mogplex.com/integrations/slack" />

  <Card title="Observability Runbook" href="/https/docs.mogplex.com/guides/observability-runbook" />

  <Card title="Sandbox Setup Checklist" href="/https/docs.mogplex.com/guides/sandbox-setup-checklist" />

  <Card title="Platform" href="/https/docs.mogplex.com/platform" />

  <Card title="Capabilities" href="/https/docs.mogplex.com/capabilities" />

  <Card title="Configure & Extend" href="/https/docs.mogplex.com/configure-and-extend" />

  <Card title="Troubleshooting" href="/https/docs.mogplex.com/guides/troubleshooting" />
</Cards>
