Pull requests
Route: /repo (sidebar: More pages → Fix → Pull requests. It is a Lab: switch it on under Settings → Display & sidebar → Labs to keep it in the sidebar)
This page shows every open pull request in the GitHub repositories connected to your Mushi Mushi app, the branch of every fix attempt with its CI status, and a log of what the fix agents did. It is where code changes land.
Summary
A banner and a snapshot strip come first. The counts are fix attempts: Branches / PRs open / CI passing / CI failing / Merged / Stuck. PR open counts every attempt with an open pull request, whatever CI says, the same way the Fixes page counts.
The page has three tabs: Pull requests, Activity and Clean up.
Pull requests tab
Open pull requests
Every open pull request in the connected repos, fix or not, grouped by what you can do:
| Group | Shows |
|---|---|
| Mergeable now | Required checks passed; a Mushi Mushi fix also has an Opus merge verdict on its latest commit |
| Needs a fix | A required check fails, or Opus said fix first. Open the fix to send it back |
| Hold | Opus said hold: a person decides. Merge is disabled here; the fix page shows the findings |
| Waiting | CI or a review is still running, or the PR is a draft |
Merge asks you to confirm first. Nothing merges from this list on its own.
Fix attempt branches
A closed panel under the open pull requests lists every fix attempt’s branch as a card. Filter by All, PR open, CI passing, CI failing, Merged or Failed.
| Field | Description |
|---|---|
| CI badge | Passing, failing, running or action required |
| Branch name | For a Cursor cloud agent, <prefix>/MUSHI-<report id>-cursor-cloud, with the prefix taken from the bug category |
| PR link | External link to the GitHub pull request |
| Report summary | Title and severity of the original report |
| Files / Lines | Diff size |
| Category | Bug category from the classifier |
| Timeline | A small graph of the fix agent’s events on this branch |
Activity tab
A log of fix events across the app, newest first. Filter by event type:
| Event | Description |
|---|---|
| Dispatched | A fix run started for a report |
| Branch | Branch created |
| Commit | Commit pushed to the fix branch |
| PR opened | Pull request opened |
| CI result | CI checks completed |
| Opus review | The agent PR review gave its verdict |
| Review follow-up | An agent was sent back to fix the review’s findings |
| Completed | Fix run succeeded |
| Failed | Fix run failed |
Clean up tab
Deletes the branches Mushi Mushi made whose pull request merged or closed, closes Mushi Mushi’s own stale, replaced or held fix PRs, turns on GitHub’s automatic branch deletion, and restores a branch Mushi Mushi deleted. Nothing changes on GitHub from one click: anyone who can edit the app asks for a list, an owner or admin approves exactly that list (it expires after an hour) and runs it once, and Mushi Mushi checks every item again when it runs.
Managing the GitHub connection
Repository settings, a closed panel near the foot of the page, lists the linked
repos with their default branch, GitHub App and index status, and an Open on
GitHub ↗ link. Its Manage link opens /integrations/config, where you
update the GitHub token, repository URL and default branch.
API
GET /v1/admin/repo/overview?project_id=<pid>
GET /v1/admin/repo/activity?project_id=<pid>&limit=100
GET /v1/admin/projects/<pid>/pull-requests
POST /v1/admin/projects/<pid>/pull-requests/<owner>/<repo>/<number>/merge { method }
GET /v1/admin/projects/<pid>/repo-cleanupRelated pages
- Fix drafts — full fix-worker run detail and streamed logs
- Integrations — configure the GitHub App connection
- Reports — the source of dispatched fixes