Your workflows, running on your machine. Debug the failing step,
get your build green, and push with a little more confidence.
.github/workflows/ci.yml$ npm test✓ auth.test.ts (6 tests)✓ workflow.test.ts (12 tests)Test Files 2 passed (2)Tests 18 passed (18)Less waiting.
More building.
CI should feel like part of your development loop. Runnr brings the workflow, the run and the reason it failed into one workspace.
Set a breakpoint before a workflow step. Inspect its environment and captured contexts, check your watches, then step forward or continue.
Step debugging- name: Install dependencies run: npm ci- name: Run testsPaused run: npm test22Re-run failed matrix shards and their required dependencies. Set automatic retries and keep every attempt in history.
Focused reruns20Passed22Retrying failed shard24PassedKeep the passing jobs. Focus on the failure.
Follow dependencies in a visual graph. Pick the jobs and matrix combinations you actually need to run.
Workflows & matricesStore credentials in the OS vault. Import GitHub variables and keep configured secrets masked in logs.
Secrets & variablesDesktop alerts tell you when a run finishes. Jump straight back to its result with a click.
Completion notificationsNo wall of terminal output to untangle. Explore dependencies, configure a run and come back to a result you can use.
Follow the jobs that depend on each other. Drag, zoom and explore the workflow graph.
Actual app screenshotStart with the workflows you already have. Keep the feedback loop on your machine until you’re ready to push.
Runnr discovers workflows, jobs, inputs and matrices from your .github/workflows directory.
~/projects/your-next-big-thingPick an event, configure your secrets, and select jobs. Save a preset for the next time around.
Follow live logs, inspect a paused step and retry failures. Push when you’ve got the feedback you need.
Give your coding agent a local CI feedback loop with Runnr’s CLI and MCP interface. Review run requests in the desktop app, and keep deployment approvals in your hands.
RunnrYour workflows. Your machine.
A little less friction between the two.
One-time purchase. No per-run fees.
We’re preparing the launch. Purchasing will be available here when the store opens.
Local CI, with the details out in the open.
A Mac, Git, and a repository with GitHub Actions workflows. For Linux jobs, start Docker Desktop, OrbStack or another Docker-compatible engine. Runnr can install its pinned act runner from inside the app. Apple Silicon and Intel Mac builds are signed and notarized.
Yes. Runnr discovers the workflows in .github/workflows and uses act to execute them locally. Your repository files stay unchanged. You can run a complete workflow or select local build and test jobs, and Runnr shows any adaptations in the generated workflow.
Local runs give you earlier feedback, but they cannot reproduce every hosted feature. Runner tooling, OIDC, GitHub environment policies and some other behaviours differ. Runnr surfaces compatibility notes; keep hosted checks for final verification where you need them. Host mode is experimental.
Run history and logs are stored locally, and saved secrets use the OS credential vault. Workflow steps can access the network and any credentials you supply. Optional GitHub integration can publish a commit status and a redacted result excerpt to your pull request; full logs stay local.
Yes. Runnr includes a JSON CLI and an MCP interface for discovering workflows, requesting runs, reading redacted logs and retrying failures. Requests go through the desktop approval inbox by default. Deployment approvals still need you.
The launch offer is a one-time purchase of Runnr for Mac. There is no per-run charge from Runnr. Workflows may still call third-party services that have their own costs. Checkout will show the final price and applicable taxes before purchase.