Fix CI before
your next push.

Run GitHub Actions locally, with your working changes, and see why a job fails.

Licence required. £19.99

Scroll to explore or open full size.

Recorded native Runnr Results: six failures grouped under Invalid key supplied, with links to the affected PHP test source and original log.
Recorded native Runnr 0.5.0. Open the original capture.

Test what you haven’t pushed.

Runnr runs the workflows already in your repo, usually in Docker on your Mac, against the files you’re editing right now.

  1. Open your repo

    Runnr finds your existing .github/workflows files. Nothing to rewrite.

  2. Pick what to run

    A whole workflow, or just the jobs you care about, matrix included.

  3. Fix it, run again

    Jump to the failing line, edit, and run again with your last settings ready to review.

Run it without committing.

Change the code, choose Run again, and the same workflow runs against your new files. No more “fix ci” commits.

What changes in Local jobs mode?

Include the job’s dependencies. Local jobs mode bypasses job conditions and omits unselected dependencies; it does not recreate every GitHub check.

Run your first workflow

Scroll to explore or open full size.

The native Run workflow sheet for Storefront checks, with Local jobs selected and the test job checked.
Choose the workflow or just the local jobs you need.
macOS 13+ Apple Silicon & IntelGit + Docker for Linux jobs

Current Mac release 0.6.3. Release notes

See exactly why it failed.

A storefront example: a £50 order is wrongly charged shipping. Runnr shows the failing test, its source line and the original log.

Explore the storefront run

Scroll to explore or open full size.

Runnr’s actual Results panel: 5 tests, 4 passed, 1 failed; the free-shipping assertion expected zero but received 4.99, with source and log links.
The failing test, grouped with its source and log links.

Supported test summaries and JUnit reports become readable results. Compiler, lint and runtime diagnostics sit alongside them.

Scroll to explore or open full size.

The native Logs tab from the same storefront run, showing the failed shipping test and the original assertion output.
The original output from the same local run.

Follow live output by job, search retained logs and return to the lines that explain the failure.

src/cart.js
- return total > 50 ? 0 : 4.99;
+ return total >= 50 ? 0 : 4.99;

All five tests pass after the edit.

Follow the fix and next run

Every run, kept.

Logs, timings and artifacts stay in your history, so you can see what changed between a failing run and a passing one.

Compare run times

Compare your own elapsed and test times. Source, input and environment differences stay visible, so a faster run keeps its context.

Scroll to explore or open full size.

Actual Performance view comparing two storefront runs: 33 seconds and 26 seconds, with a warning that source and uncommitted changes differ.
Recorded timings, with differences between runs called out.

Local timings are observations. Cache state and system load are not controlled; a comparison is not a promised speedup.

Scroll to explore or open full size.

Runnr’s native artifact browser showing the sample’s uploaded ZIP files and a preview of shipping.xml, its real JUnit test report.
The sample’s JUnit report, collected as a local artifact.

Open what a job produced

Enable local artifacts for actions/upload-artifact@v4. Browse ZIP entries, preview supported files with Quick Look, reveal them in Finder or drag copies into another app.

Come back to any run

Save a named preset for a repeatable local check. Run again restores settings for review. History keeps the original failure alongside the next result.

Work through a fix

Next: a focused repair loop.

In development. These features are not included in the current download.

Rerun the failed job
Retain its matrix and dependencies. Compare matching test evidence as passed, failed again or not observed.
Open a GitHub job URL
Review hosted and local revisions before reproducing a supported Ubuntu job. Missing credentials and hosted-only capabilities stay explicit.
Read the development scope

Keeps going while you work.

Close the window and the run carries on. Come back to your context intact.

Scroll to explore or open full size.

Native Runnr workflow history with the original failed storefront run and the next successful run after the boundary fix, using uncommitted changes.
The failure and the fixed run, retained together.

Run in the background

Close the window. Follow the run, open logs or cancel from the menu bar.

Know when it needs you

Review pending approvals and get completion notifications, subject to your Mac’s permissions.

Start from your keyboard

Use Shortcuts or Spotlight. Spotlight actions require macOS 26+.

Keep long runs moving

Runnr prevents idle system sleep during a run. Your display can still sleep.

Local by default.

What stays on your Mac, what can reach the network, and what a local pass does not prove.

Secrets stay protected

Saved credentials are encrypted on your Mac, and secrets are redacted from logs.

Credential protection

Saved credentials are encrypted on your Mac, with a Keychain-protected key. Configured secrets are redacted before logs are displayed or saved.

Share your setup

Send teammates your project settings, without sending your secrets.

Sharing options

Import GitHub repository and environment variables as local snapshots. Share settings or passphrase-encrypted team bundles. GitHub secret values must be supplied locally.

Let your agent run it

Coding agents can start runs and read redacted logs through the CLI and MCP, with your approval.

GitHub and agent access

Publish eligible commit statuses and redacted PR comments. Use CLI or MCP for runs and results, with desktop review by default and separate deployment approvals.

Built around act

Runs through open-source act, usually inside Docker. Keep your required GitHub checks.

Read compatibility & requirements

Pay once, not monthly.

No per-run charges from Runnr. A year of updates is included, and your version keeps working after that.

Individual

£19.99 one-time purchase

One person, up to 3 Macs.

Includes one year of updates. Runnr keeps working afterwards. Renew updates for £19.99. Renewal is optional.

Workflow, job and matrix execution. Live logs, supported results and diagnostics, history, artifacts, CLI and MCP access.

Buy Runnr for Mac

For your team

£15 per seat

Minimum 2 seats.

One person per seat, up to 3 Macs each. A separate licence key for every team member, with encrypted project sharing.

Each seat includes one year of updates. Runnr keeps working afterwards. Optional renewal is £19.99 per seat.

Buy team licences

Four short guides.

Written for the released Mac app, from first run to reading a failure.

Questions before you buy.

Requirements, licensing, privacy and what’s included, answered plainly.

Ask a question
What do I need to get started?

A Mac running macOS 13 or later, Git, a repository with GitHub Actions workflows and an activated Runnr licence. Start Docker Desktop, OrbStack or another Docker-compatible engine for Linux jobs. Use the managed act runner or the bundled Runnr beta engine, selected in Project settings.

Do I need to rewrite my workflows?

No. Runnr discovers your .github/workflows files. Run a whole workflow or selected local jobs, including static matrices. Local jobs mode removes unselected jobs, their dependencies and selected jobs’ top-level conditions; step conditions remain. Running writes a separate execution snapshot, leaving the workflow in your checkout unchanged.

Can I test changes I haven’t committed?

Yes. Working-tree checkout includes your local edits by default. Project settings can instead allow a remote actions/checkout checkout. A passing local subset only verifies the selected scope, with the environment and inputs used in that run.

What failures can Runnr explain?

Results reads supported test summaries and uploaded JUnit XML. It also groups supported compiler, lint and runtime diagnostics, with source and log links when available. Pest/PHPUnit, Jest/Vitest, pytest, XCTest and Cargo summaries can supply totals. Go failures are supported; upload JUnit for complete Go test totals. Unknown output stays in the logs without invented counts. Optional on-device explanations require compatible Apple Intelligence hardware and macOS 26 or later.

Does a local pass guarantee a pass on GitHub?

No. Local container images, tooling, event context and GitHub-hosted features can differ. OIDC, environment policies and token permission enforcement are among act’s limitations. Keep the hosted checks your repository requires. Runnr does not disable or cancel workflows triggered by a push.

Where do credentials and logs go?

Saved credentials are encrypted on your Mac, with the encryption key protected by Keychain. Runnr redacts configured secrets before displaying and retaining logs. History and artifacts stay local. Workflow code can still use the network and the credentials you supply. Optional GitHub integration can publish eligible commit statuses and PR comments with redacted failure excerpts. Licensing and update checks also use the network.

Can I import secrets and share a team setup?

Import repository or environment variables from GitHub as a local snapshot. GitHub only exposes secret names, so you must supply secret values locally. Share settings without secrets, or export an encrypted .runnr-team bundle protected by a passphrase. Protected secrets require authentication; importing a bundle does not start a workflow or enable imported automation.

Can I use Runnr with my coding agent?

Yes. The CLI and MCP interface can list workflows, request runs, read redacted logs, wait for results and request failed-job reruns. Keep Runnr open and copy the connection details from Runner & app settings. Requests need desktop approval by default. Project access can be enabled explicitly; deployment approvals and protected-secret authentication remain separate.

How do deployment approvals work?

Recognised deployment jobs and jobs you explicitly mark for approval wait before starting, including each matrix shard. Approve or reject them in Runnr. These are local approval gates; they do not reproduce GitHub environment reviewer policies.

Can runs keep going in the background?

Yes. Closing the window leaves Runnr and the workflow running. The menu bar shows the active step and elapsed time, opens logs and recent results, and lets you cancel. The Dock shows progress. Runnr prevents idle system sleep during a run while allowing display sleep. Completion notifications require macOS notification permission.

What works with Spotlight, Shortcuts and Raycast?

Spotlight indexes projects and workflows. Shortcuts can open a project, prepare or repeat a run, open the latest failure and read the latest result; preparation returns to the app for review. Spotlight actions require macOS 26 or later. Raycast extension source and Quicklinks can be exported from settings; Raycast Store availability is upcoming.

Which debugging tools are included?

The current native app includes named run presets, preset-based watch mode, job graphs and expanded Git tools. Interactive step debugging, breakpoint controls and automatic failed-job retries are not included. Exportable Raycast source and Quicklinks are available; Raycast Store availability is upcoming. Focused failure repair and GitHub job URL import are in development, not in the current download.

Is Runnr a subscription?

No. An individual licence costs £19.99 for one person on up to 3 Macs. Includes one year of updates. Runnr keeps working afterwards. Renew updates for £19.99. Renewal is optional, with no automatic renewal payments or per-run charges from Runnr. Third-party services used by your workflows may have their own costs.

How do purchase, download and activation work?

Register or log in and verify your email in the customer portal, then continue to Stripe-hosted Checkout. Licence keys arrive by email and remain in your account. Download the universal Mac installer from the portal and enter your key in Runnr. Initial activation needs internet access; successful validation allows up to 7 days of offline use between checks.

What happens after a year?

Includes one year of updates. Runnr keeps working afterwards. Renew updates for £19.99. Renewal is optional. Each team seat also includes a year of updates, with optional renewal at £19.99 per seat. Downloading the latest installer and receiving new updates require current update access.

Stop pushing
to find out.

Run your existing GitHub Actions on your Mac, with the changes you haven’t committed yet.

Download for Mac

Scroll to explore or open full size.

The native Run workflow sheet for Storefront checks, with Local jobs selected and the test job checked.
Choose the workflow or just the local jobs you need.