UX runs

Route: /ux-runs

Scenario: You let your coding agent work through every page, tab and dialog of your app overnight and want to see, screen by screen, what it changed and whether anything got worse.

mushi ux run runs on your machine. It maps your running app, gives one screen at a time to the agent you choose (Claude Code, Cursor, Codex) in a separate git branch, and keeps an edit only when accessibility, layout and console measurements did not get worse. With --sync it mirrors the run here as it goes.


mushi ux ui      # pick the agent, a model from your account, a skill and the pages, then start
# or straight from the terminal:
mushi ux run --dev "pnpm dev --port {port}" --agent claude-code --sync

A synced run shows here as it goes: its phase (installing, mapping, working on “Home, attempt 2”), a progress bar by outcome, and the screen the agent is on. While an attempt runs you see its step count, the file it last read or edited, the files changed so far, and the time used out of its time box. A running run checks in every 30 seconds; when it stops, the page says how long it has been quiet and how to resume it.

Each screen keeps every attempt’s screenshot at phone and desktop width; pick one to compare it with the baseline. What the agent did in attempt N lists the files that attempt read and edited. The agent’s own words and the commands it ran stay on the machine that ran it. A run only syncs to the project its app reports to: if your login is for another project, --sync says so and stops.

Exploring your app never sends a write request: every request that is not a read is blocked, forms are not submitted, and buttons such as Delete or Pay are never clicked.

Run in the cloud

No machine to leave running? Run in the cloud starts the same pass on your repo’s GitHub Actions, with a Cursor Cloud agent making the edits. It appears on this page like a local run and ends with one draft PR. You need, in the app’s front end repo:

.github/workflows/mushi-ux.yml on the default branch, with dev-command set to how your app starts.
Secrets CURSOR_API_KEY and MUSHI_API_KEY (a key with mcp:write), the variable MUSHI_PROJECT_ID, and optionally ANTHROPIC_API_KEY for the review.
Settings → Actions → General → Allow GitHub Actions to create pull requests, or the run ends with a compare link instead of a draft PR.

Pick the model from your Cursor account’s list (with its settings, such as effort and context; this needs a Cursor key under Settings → AI keys) and, optionally, a skill from the synced skills catalog. Mushi starts it with a repository_dispatch event through your GitHub connection, at most three times an hour per app. When it cannot (no workflow, no connection, GitHub refused), the card shows the gh workflow run command to start it yourself.

A cloud run sees your app signed out: screens behind sign-in show as Could not load. Each attempt is a commit Cursor pushes to mushi-ux/<run id>; if your CI runs on every push, add branches-ignore: ['mushi-ux/**'] to it.

What you see

Status	Meaning	What to do
Moved by another fix	A change kept on another screen (often a shared component or token) changed this one.	Check it first.
Rolled back	Every attempt made a measured problem worse, so it was undone.	File it as a bug, or run again with a different model.
Could not load	The screen did not render for capture.	Run `mushi ux login` for signed-in screens, or allow the reads your app makes with POST (`--allow`).
Improved	An edit was kept.	Review it on the run’s branch.
No change needed	The agent made no edit, or nothing visible changed.	Nothing.

Select a screen to see a before/after slider, the changed pixels, the problems still measured, each attempt with its commit, and the optional review by a second model. The review is advisory: it never keeps or reverts anything.

File as bug

File as bug adds the screen to your normal bug queue (source ux_loop) with the measurements and the review’s notes. It makes no AI call.

Where the changes are

Kept edits are commits on the branch shown above the screen list (mushi-ux/<run id>). Nothing is merged for you: review the branch and open it as a draft PR. Screenshots are kept for the project’s retention window (30 days by default).