Support
Find the right Mogplex troubleshooting path for setup, routing, models, CLI auth, sandboxes, integrations, and docs issues.
Use this page when something is not working and you need the fastest path to the surface that owns the state.
Mogplex issues usually become easier to debug once you separate account setup, repo coverage, routing, execution, and local CLI state.
Start with the symptom
| Symptom | Start here |
|---|---|
| A charge, invoice, credit balance, payment method, or due date looks wrong | Plans & Billing, then email support@mogplex.com |
| Repo is visible but GitHub events do not start work | GitHub and Installations |
| A model is missing from a picker or CLI run | Available Models and Model Selection and Cost |
| Hosted run cannot call an external service | Connections and MCP, Settings, and Connection Scope and Overrides |
| Slack mention does not start repo work | Slack, Settings, and Observability Runbook |
| Sandbox or preview launch is failing | Sandbox Setup Checklist, Vercel, Projects, and Sandboxes |
| CLI signs in but does not inherit expected hosted state | Settings, CLI Authentication, and Configuration and Flags |
| CLI says that the model returned no output | Open /model. Choose another model, then retry the task. The CLI stops before an automatic retry can add cost. |
| A slash command does not behave as expected | Slash Commands, Slash Commands guide, and Custom Slash Commands |
| You need the API error shape or status code | API Quickstart and API Errors |
| You need to know what is safe to share | Security and Data Handling |
| A doc link or claim looks wrong | Docs source |
For a longer decision tree, use Troubleshooting.
First checks
Before changing routing or agent configuration, check these in order:
- Settings: GitHub identity, App coverage, managed access, CLI tokens, and shared connections.
- Installations: whether the repo owner has App-backed coverage.
- Projects: whether the repo is imported once, covered, and configured for the right runtime.
- Available Models: whether the expected model is enabled and available for the account.
- Observability: whether the failing run, model call, tool call, or sandbox event exists.
If there is no relevant Observability record, debug the source surface first: GitHub, Projects, Triggers, Assignments, Automations, CLI, or API.
What to capture
When you ask someone else to help diagnose a Mogplex issue, include:
- the repo owner/name
- whether the repo is visible in Projects
- whether the repo owner is covered in Installations
- the surface that started the work, such as CLI, Trigger, Assignment, Automation, API, Slack, or GitHub mention
- the run ID, sandbox ID, or API request details when available
- the model selected and whether it appears in Available Models
- the exact GitHub comment, mention, event, or CLI command that should have started work
- the first error message, status, or failed API response, not only the last retry
For billing help, include the account name, invoice number, charge date, and charge amount when available. Do not send a full card number, security code, password, API key, or access token.
Email support@mogplex.com after you collect these details.
Docs issues
The docs source lives in Mogplex/docs. If a page is stale, missing a route, or points at the wrong product surface, use the page's GitHub link or the repository itself as the source path for a docs fix.