An event arrives
An issue opens, CI fails, or a schedule fires. Mogplex collects the repo, thread, logs, and diff that the agent needs to act.
You choose the trigger
Connect an event, a Slack message, or a schedule to the pipeline you want to run.
HOW IT WORKS
From the first event
to code you can trust.
You choose the agent and set the rules. Mogplex takes each run from trigger to review in an isolated sandbox, with the work visible at every step.
Your pipeline sets the plan
Your pipeline defines the repo, agent, context, and approval gates before work starts. Each run records the event that caused it.
Your agent, your context
Choose Mogplex Native, Claude Code, or Codex for each pipeline. Add the tools and context it needs.
A sandbox boots
The run gets an isolated microVM with a clone of your repo. The agent can change files and run commands there. Your machine stays free.
A separate place to work
Each run has its own sandbox. Hosted sandbox time draws from your usage balance.
The agent loop
The agent writes code, runs tests, and uses your connected tools. Follow the work as it happens, with each model call and tool result in view.
Stay in control
Inspect a live run, approve a tool call, redirect the plan, or stop the work.
The gates
The work reaches a pull request and the checks you set. A merge must pass your configured gates. Branch protections and required reviews still apply.
Your rules decide what ships
Set the level of autonomy per pipeline. Required checks and reviews still apply.
Reconcile, then loop
Trace a deployed change back to its run and the event that started it. The pipeline stays ready for the next feature, failed check, or maintenance task.
Keep the full history
See what requested the work, which agent did it, what it cost, and who approved it.
Your code. Your rules.
HARNESSES
The native Mogplex agent, Claude Code, and Codex. Pick the harness and model per pipeline. Every call is visible call-by-call.
SANDBOX
Every run gets a fresh, isolated microVM with a separate workspace.
GATES
Branch protections, required checks, and required reviews always win. Autonomy is a dial you set per pipeline.
SOURCE
The platform is Apache-2.0. Read what authenticates against your repos before you run it.
YOUR FIRST PIPELINE
Set the rules.
Let the work run.
Start now
Choose a repo, an agent, and the gates every change must pass.