GitHub
Connect Mogplex to GitHub identity, App coverage, repo import, comments, PRs, issues, reviews, triggers, and automations.
GitHub is the first integration most Mogplex accounts need.
It does two separate jobs:
- the GitHub connection (GitHub OAuth) identifies your GitHub account and reads your org memberships
- the Mogplex GitHub App gives Mogplex access to repositories and sends the webhooks that start work
Repository access comes from a Mogplex GitHub App installation that is linked to you, or from repositories a teammate has shared to your Mogplex team. Neither GitHub sign-in nor the GitHub connection grants repository access on its own.
Setup order
- Open Settings → Account and select Install GitHub App. If your GitHub account is not connected yet, GitHub asks you to authorize Mogplex first.
- Install the App on your personal account, or on an org where you are an org owner. Mogplex links the installation when GitHub returns you to Mogplex.
- Confirm the installation under Settings → Account (see Installations).
- Sync repos in Projects.
- Choose the routing surface that matches the work: Triggers, Assignments, or Automations.
- Verify the first run in Observability.
Repository access
| State | What you can use |
|---|---|
| GitHub connected, no installation linked | No repositories, except repositories shared to your Mogplex team |
| Installation linked | Every repository in that installation, for repo work, webhooks, triggers, and automations |
| Installation linked and repos synced | Full GitHub-backed setup |
The rules that decide this:
- You can link an installation on your own personal account, or on an org where you are an org owner. Linking gives you the installation's whole repository set.
- Org members who are not owners do not link the org installation. They use team-shared repositories instead. See Who can link an installation.
- If an installation is uninstalled or suspended on GitHub, your access to its repositories ends. See When an installation is removed.
For how linking happens, see How an installation gets linked. If an org you belong to is missing, see An org you belong to does not appear.
Self-hosted deployments without a GitHub App work differently: there, the GitHub OAuth app lists and imports repositories. See Self-hosted GitHub App.
Repository creation
Creating a repository from Mogplex has its own requirements:
- In an organization, you must be an org owner, and the org's installation must be linked to you. An org owner must also accept the App's Repository creation permission on GitHub. If Mogplex says the App "cannot create repositories yet", the request is still pending or the organization's repository creation policy blocks it. If you self-host, see also GitHub App troubleshooting.
- In your personal account, the App must be installed on your account, so Mogplex can work in the new repository. Then select Authorize GitHub when Mogplex asks. Mogplex creates personal repositories with your own GitHub authorization, so it acts as you there. Mogplex renews the authorization in the background; you authorize again only if it goes unused for about six months or you revoke Mogplex in GitHub Settings → Applications. If you self-host, configure the App client credentials.
What GitHub can start
Mogplex GitHub routing can start work from issue comments, PR comments, PR review comments, commit comments, repo events, and the specific routing events exposed by the current trigger or automation surface.
The important choice is scope:
- use Triggers for one GitHub event waking one agent
- use Assignments for durable repo-owned work
- use Automations for graph-shaped work with branching, delays, publishing, or parallel agents
Mention routing
Mogplex recognizes two mention forms in GitHub comments:
@mogplex@mogplex/<agent-slug>
Bare @mogplex routes only to the default mention target. Targeted mentions
route by agent slug.
Use GitHub Mention Routing for the exact rules, including entry-agent behavior in automations.
Where to check state
- Settings: GitHub connection state and account-level setup
- Installations: linked installations, repo eligibility, and synced repo state
- Projects: imported repo list, repo settings, and workspace entry points
- Observability: run status and failure trail after a GitHub event starts work
Common failures
- An org you belong to does not appear: the org's installation is not linked to you. An org owner installs or configures the App; see An org you belong to does not appear.
- Triggers are empty: no installation is linked to you for the repo owner.
- Mention does not wake the expected agent: the comment may be bare
@mogplexwhen it needed@mogplex/<agent-slug>, or the wrong route is marked default. - Automation cannot find the expected repo: check installation coverage and repo sync before editing the automation.
- PR review work starts in the wrong shape: use an Assignment for standing repo responsibility, not a one-off Trigger.
Dependabot alerts
GitHub can also start work when it reports a vulnerable dependency. See Dependabot to have Mogplex open a reviewed fix PR for each new alert.
Read next
Integrations
Every system Mogplex connects to, including GitHub, Slack, Linear, Notion, Sentry, Supabase, Neon, model providers, agent harnesses, webhooks, the API, and MCP clients.
Dependabot
Have Mogplex open a reviewed fix PR when GitHub reports a new Dependabot alert, using the Dependabot autopilot workflow template.