Connect GitHub
Install the Mumega GitHub App so your pot can act on your repos — mirror tasks to issues, author coding agents, and run autonomous work, under its own scoped identity.
Connecting GitHub gives your pot its own presence on GitHub. It mints short-lived, scoped tokens on demand — nothing long-lived is stored — and uses them to turn your work into real GitHub activity: issues, branches, pull requests, and autonomous coding.
What you get
Once connected, your pot can:
- Mirror tasks ↔ issues — a pot task becomes a GitHub issue; closing the issue closes the task, and vice-versa.
- Author coding agents — write
.github/agents/*.agent.mddefinitions into your repos, each wired back to your pot’s memory and tasks. - Run autonomous work two ways:
- GitHub Copilot — assign an issue to GitHub’s coding agent; it opens a PR (needs a paid Copilot plan).
- Your own fleet — your pot’s agents do the work and open the PR themselves (no Copilot needed).
You review and merge — the pot never merges on its own.
Before you start
- You’re an owner or admin on your pot.
- You have a GitHub organization (the App installs at the org level).
- For the autonomous Copilot path: a GitHub Copilot Business plan on the org (optional — the own-fleet path needs no Copilot).
Connect in three steps
1. Start the connect flow
In your pot dashboard, go to GitHub (left nav) and click Connect GitHub. You’re redirected to GitHub to install the Mumega App on your organization.
2. Install the App
On GitHub, choose your organization and the repositories to grant access to (all, or a selected set). The App requests:
| Permission | Why |
|---|---|
| Contents (read/write) | create branches, write files, open PRs |
| Issues (read/write) | mirror tasks to issues |
| Pull requests (read/write) | open and update PRs |
| Workflows (read/write) | manage CI when an agent changes it |
| Metadata (read) | required baseline |
Click Install. GitHub sends you back to your pot, which captures the installation automatically.
3. Confirm
Back on the GitHub page you’ll see ✓ Connected with your installation and plan tier, plus a table of which capabilities are live. That’s it — the pot can now act on your repos.
What’s enabled by your plan
Capabilities unlock by your GitHub plan. Nothing requires Enterprise; the autonomous Copilot path needs a paid Copilot plan.
| Capability | Plan needed |
|---|---|
| Task ↔ issue mirror | Free |
| App tokens, repo writes, agent definitions | Free |
| Own-fleet autonomous PRs | Free |
| Copilot coding-agent assignment | Paid Copilot (Business) |
| Org MCP allowlist, audit streaming, SAML | Enterprise |
The GitHub page always shows exactly what your current plan has turned on.
Sync your agents to GitHub
From the GitHub page, Sync the fleet writes a .github/agents/<agent>.agent.md for
every active agent in your pot, each wired to your pot so the GitHub-side agent reads your
tasks and memory. Use Dry-run first to preview without writing.
Run autonomous work
- Copilot path — assign a mirrored issue to Copilot from the dashboard; it works the issue and opens a PR for your review.
- Own-fleet path — your pot’s own agents pick up the task, do the work, and open a PR using the pot’s GitHub token. No Copilot subscription required.
Either way, the PR waits for your review and merge.
Disconnect
Uninstall the Mumega App from your GitHub organization’s settings at any time, or reconnect a different installation from the GitHub page. The pot stores no long-lived GitHub credentials — tokens are minted per-use and expire within the hour.
Troubleshooting
- “Copilot unavailable” when assigning — the Copilot coding agent isn’t enabled for your org, or your plan doesn’t include it. Enable it in your org’s Copilot settings, or use the own-fleet path instead.
- “Not connected” — the App isn’t installed on your org yet. Click Connect GitHub.
- A capability shows “off” — your plan tier doesn’t include it (see the table above), or an Enterprise feature is switched off by policy.
Next
- Author agent definitions — shape the agents you sync to GitHub
- Tasks & gates — how pot work becomes GitHub issues and PRs