Fair questions.

The 11 things skeptical engineers ask before they wire an agent into their repo. Short answers live here. The long answers live in the docs and in the anatomy of a run.

What is Mogplex, in one sentence?

A system that builds and maintains software. Events go in: GitHub events, schedules, and Slack asks. Agents plan, build, test, and review the work in sandboxes. Reviewed, running code comes out through your gates.

Which agents does it run?

The native Mogplex agent, Claude Code, and Codex, with your MCP tools available inside every run. You pick the harness and model per pipeline. Hosted model access uses your Mogplex balance, so you do not need to set up API keys. Prefer your own model billing? Add your AI Gateway key in Settings → API Keys. Your runs then use it.

Can an agent merge to main without a human?

Only if you configure a pipeline that way. Your branch protections still rule. Mogplex cannot bypass required reviews, required checks, or protected branches. Most teams start with draft-PR-only gates and loosen from there.

Where does the code run?

In a fresh microVM for each run: a Vercel Sandbox that holds a clone of your repo. Runs share nothing. Nothing runs on your machines.

What does it cost?

Individual plans start with Pro at $20 a month. Each plan includes parallel agent runs, Storage, and Inference. Each $1 of inference credit pays for $1 of model usage at the provider price. Business and Enterprise plans use custom terms.

What are parallel agent runs?

Parallel agent runs are active runs that work at the same time for one billing account. Pending work does not use a run slot. When all slots are in use, new work waits until a run finishes or you stop one.

What can trigger a run?

GitHub events can start a run: issues, comments, mentions, pushes, pull requests, CI failures, labels, and tag pushes. Schedules, Slack mentions, signed webhooks, and standing assignments can also start runs.

Can I see what an agent did — or stop it?

Every run is visible call-by-call. The system meters and logs each model call and tool call. You can enter a live run to approve the next tool call, redirect the plan, or stop it from the web app or CLI.

How is this different from assigning tasks to an AI teammate?

Delegation is a transaction: you ask, it answers, and when you stop asking, everything stops. A pipeline is infrastructure. You wire it once. Work continues while you sleep or build something else.

What does "maintains" mean, concretely?

It is the work nobody staffs. A run bumps your dependencies each night and tests the result. Another run reproduces and bisects CI failures. Other runs open docs PRs when your API drifts, backfill tests, or draft release notes. You wire each pipeline once.

Is it open source?

Yes. The platform at github.com/mogplex/mogplex is Apache-2.0. You can read what authenticates against your repositories before you run it. You can also self-host it.

How do I start?

Choose an Individual plan, create your account, and connect a repo. Your plan shows the capacity available before you wire a pipeline. You can also self-host the Apache-2.0 application with no license fee.

  SHEET 04 — END

Still skeptical?
Good. Bring that.

Start now

the best feedback comes from people who don't trust us yet.