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.
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.
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.
Close the window and the run carries on. Come back to your context intact.
Scroll to explore or open full size.
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.
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.