Show: All · Platform · CLI · Mac app
Follow along with the RSS feed.
CLI v0.18.0
CLI release · November 20, 2026
New
relayrunner blacksmith connectconnects your Blacksmith organization so Settings › Providers shows its real usage. You approve an org token in your browser as a Blacksmith org admin, and only that token is sent to RelayRunner. If Blacksmith’s CLI isn’t installed, it offers to download it into~/.relayrunner/bin.relayrunner initno longer skips a job just because it can request OIDC tokens (id-token: write), such as for a Turbo or Vercel remote cache. It’s still a deploy job when it uses the token to sign in to a cloud or publish a package; otherwise it’s ready, with a warning.--allow-deploy <jobs>routes jobs that look like deploy jobs, once you’re fine giving the machine their secrets.
CLI v0.17.0
CLI release · November 20, 2026
New
relayrunner init --autowritesautoin place of a Linux x64 job’s runner label, so you set the job’s size on the dashboard’s Router page instead of in the workflow file. macOS and Arm jobs keep their labels.
CLI v0.16.0
CLI release · November 19, 2026
New
- The Mac Jobs window opens with the jobs it last showed and refreshes them in the background, and a job you’ve already opened shows its steps at once. Jobs running or waiting on the Mac come first. Filter by result, repo, workflow and time, and drag the line between the list and the job to resize them. Clicking a job in the menu’s History tab opens it in the Jobs window.
relayrunner jobslists running jobs first and gains--repo,--workflow,--resultand--since.
Mac app v0.6.0
Mac app release · November 19, 2026
New
- The Mac Jobs window opens with the jobs it last showed and refreshes them in the background, and a job you’ve already opened shows its steps at once. Jobs running or waiting on the Mac come first. Filter by result, repo, workflow and time, and drag the line between the list and the job to resize them. Clicking a job in the menu’s History tab opens it in the Jobs window.
relayrunner jobslists running jobs first and gains--repo,--workflow,--resultand--since. - A simpler menu. It shows the switch, what this Mac is doing and each running job, then Pause New Jobs, Jobs, Open Dashboard, Settings and Quit, with no icons. The Now, Queue and History tabs, the empty slot rows and the CPU and memory meters are gone: the Jobs window lists running, waiting and finished jobs. There is one pause control, which becomes Resume New Jobs while paused. The offer to take one more job at once moved to the Jobs window. Show Log and Check for Updates moved to Settings › About.
Fixes and improvements
- The menu no longer shows a running job’s usual time once it passes it. The bar turns orange only when the job is clearly slower than usual: at least 30 seconds and a quarter over its usual time.
Agents can change your routing
Platform update · November 19, 2026
- Allow changes for an agent. Turn on Allow changes for a connected agent under Settings → Agents, and it can change the runner order, the default and per-job sizes for auto jobs, automatic retries and AI, and pause or resume runners. You turn it on for your own agents, per workspace. The agent acts as you, so it can’t change what you can’t. See MCP server.
- Settings changes in Activity. Changes to the runner order, sizes, retries and AI now show in Activity, with who made them and whether it was through an agent. Filter by Settings to see only those.
Send job logs to your tools or your own bucket
Platform update · November 19, 2026
- Job logs with your traces. Under Settings → Telemetry, choose Failed jobs or Every job for Job logs, and each finished job’s log goes to the endpoint that gets your traces. Each line carries its step’s span, so a tool that shows traces shows a failed step’s output under it. See Job logs.
- Log archive. Keep job logs in a bucket you own on Amazon S3, Cloudflare R2, Google Cloud Storage or any other service that speaks the S3 API, as one gzipped NDJSON file per job. It works with or without a telemetry endpoint. See Log archive.
- Nothing kept on the way. Each log streams from GitHub to where you send it. Anything that looks like a credential is replaced with
[redacted], and a log over 20 MB keeps its first 16 MB and last 4 MB. - Changes in Activity. Turning job logs or the archive on or off, pointing telemetry at another endpoint or the archive at another bucket, and changing headers or access keys all show in Activity.
Route a repo from the dashboard
Platform update · November 19, 2026
- Route a repo. The Router page takes you through one repo at a time: pick the repo, pick its jobs from recent runs, then copy a prompt for your coding agent or the
initcommand. The page then waits for the repo’s first routed run and tells you when it’s routed. See Route repos from the dashboard. - Sizes before the first run. Pick each job’s size while you route it, and the first routed run uses it.
- Runner group check. Repos your org’s Default runner group leaves out are marked, with a link to fix it, before you route them.
relayrunner init --auto. Writesautoin place of a Linux x64 job’s label, so you set its size on the Router page.
Clearer run times and job sizes for members
Platform update · November 19, 2026
- Run times on History. The chart shows one workflow at a time, the busiest first, as a median line with a band for the middle 80% of runs. Failures show as marks, and cancelled runs sit behind a legend toggle.
- Live on Runners. The Runners page says Live while it’s current, with exact times on hover. Once it falls behind, it shows when it last updated.
- Members can size jobs in their repos. Members can change an auto job’s size and first provider in repos they can push to on GitHub, since they could already change its runner in the workflow file. Workspace-wide settings stay with owners and admins. See Roles.
CLI v0.15.0
CLI release · November 18, 2026
New
relayrunner initrecognises Lizard labels (lizard-medium-ubuntu-2404and the like), keeps them as a job’s fallback, and writes relays pinned torelay.yml@v1.0.0-beta.8, which takes alizardinput.- RelayRunner for Mac has a Jobs window (Jobs… in the menu, ⌘J while it’s open). It lists every job the Mac ran in the last week, sortable by how long each waited and ran. Pick one to see its steps on a timeline and, for a failed job, the step that failed, GitHub’s annotations, the end of its log and, when the workspace has AI on, the likely cause. The CLI gains
relayrunner jobsandrelayrunner jobs <id>, which read the same from the gateway with the machine’s own token.
Mac app v0.5.0
Mac app release · November 18, 2026
New
- RelayRunner for Mac has a Jobs window (Jobs… in the menu, ⌘J while it’s open). It lists every job the Mac ran in the last week, sortable by how long each waited and ran. Pick one to see its steps on a timeline and, for a failed job, the step that failed, GitHub’s annotations, the end of its log and, when the workspace has AI on, the likely cause. The CLI gains
relayrunner jobsandrelayrunner jobs <id>, which read the same from the gateway with the machine’s own token.
CLI v0.14.0
CLI release · November 18, 2026
New
connectkeeps a history of the jobs it runs in~/.relayrunner/history.jsonl, andrelayrunner historylists them with each one’s result and time. When it starts a job it now names it, and with--eventstherunevent says which job it is and how long it usually takes on this machine.relayrunner initrecognises StarSling, Monk CI, Runloft, Latchkey, BerryBox, Celesto and InstaBox labels, keeps them as a job’s fallback, and writes relays pinned torelay.yml@v1.0.0-beta.7, which takes an input for each.- The Mac menu and
connect --eventsnow say how many jobs are waiting for a slot on this machine.
Fixes and improvements
- The Mac menu’s Queue names each waiting job and its workflow once GitHub has said which job it is. When jobs went to hosted runners because every slot was busy, a button allows one more job at once: the app pauses new jobs, waits for the running ones to finish, and comes back with the extra slot, or goes back to the earlier setting if it can’t.
- The Mac menu has Now, Queue and History tabs. Queue lists the jobs waiting for this Mac and how long each has waited, and says when jobs went to hosted runners in the last hour because every slot was busy. History shows the last 12 hours as a bar per hour, with the latest jobs, all or only failed.
connect --eventsaddsqueueandspilledtowaitingandstate. - The Mac menu shows a row for each job slot, free ones included, with a bar against each job’s usual time, and this Mac’s CPU and memory while the menu is open.
connect --eventssays how many slots the machine has instate. - New installs connect to https://app.relayrunner.dev and link to relayrunner.dev. Machines already connected keep their saved server, https://app.relayrunner.app, which keeps working.
Mac app v0.4.0
Mac app release · November 18, 2026
New
- The Mac menu’s Queue names each waiting job and its workflow once GitHub has said which job it is. When jobs went to hosted runners because every slot was busy, a button allows one more job at once: the app pauses new jobs, waits for the running ones to finish, and comes back with the extra slot, or goes back to the earlier setting if it can’t.
- The Mac menu has Now, Queue and History tabs. Queue lists the jobs waiting for this Mac and how long each has waited, and says when jobs went to hosted runners in the last hour because every slot was busy. History shows the last 12 hours as a bar per hour, with the latest jobs, all or only failed.
connect --eventsaddsqueueandspilledtowaitingandstate. - The menu shows how long each running job has taken and about how long it has left, based on its usual time on this Mac. It also lists the last five jobs this Mac ran, with a link to each on GitHub and a total for the day, and lets you pause new jobs for an hour, four hours or until tomorrow morning.
- The Mac menu shows a row for each job slot, free ones included, with a bar against each job’s usual time, and this Mac’s CPU and memory while the menu is open.
connect --eventssays how many slots the machine has instate. - The Mac menu and
connect --eventsnow say how many jobs are waiting for a slot on this machine.
Fixes and improvements
- New installs connect to https://app.relayrunner.dev and link to relayrunner.dev. Machines already connected keep their saved server, https://app.relayrunner.app, which keeps working.
Mac app v0.3.1
Mac app release · November 18, 2026
Fixes and improvements
- The menu bar menu is now a real macOS menu, so it has the system’s shape and look.
- The menu bar panel closes when you pick Settings or another item, and Settings stays in front while you use the menu bar.
CLI v0.13.2
CLI release · November 18, 2026
Fixes and improvements
connect --eventsreports each job’s result, so the Mac app can tell you when a job fails.
Mac app v0.3.0
Mac app release · November 18, 2026
New
- A welcome window on first launch moves the app to Applications, signs your Mac in and turns on opening at login. You can also turn on a notification for when a job fails on your Mac (off by default).
- Quitting while a job runs asks first. You can quit once the job is done, quit now, or cancel.
Usual times, job history and the Mac queue
Platform update · November 18, 2026
- Time left for running jobs. The Runners page and the History run panel show about how long each running job has left, from how long it usually takes on that runner, and flag one that’s slower than usual. See Self-hosted runners.
relayrunner history.connectkeeps a history of the jobs it runs, andrelayrunner historylists them with each one’s result and time. CLI 0.14.0. Seehistory.- RelayRunner for Mac 0.4.0. The menu has Now, Queue and History tabs: a row per slot with each job’s usual time and time left, the jobs waiting for this Mac by name, and the last 12 hours of jobs. When jobs go to another runner because every slot is busy, one click allows one more job at once. Pause new jobs for an hour, four hours or until tomorrow. It updates itself. See RelayRunner for Mac.
CLI v0.13.1
CLI release · November 17, 2026
Fixes and improvements
- The Runners page shows when a machine runs through the Mac app, with the app’s version beside its CLI’s.
Mac app v0.2.1
Mac app release · November 17, 2026
Fixes and improvements
- The Runners page shows when a machine runs through the Mac app, with the app’s version beside its CLI’s.
CLI v0.13.0
CLI release · November 17, 2026
New
relayrunneris now a native binary rather than a Node.js program, so it’s a smaller download and starts faster. npm installs the one for your computer, and the commands are the same.
Mac app v0.2.0
Mac app release · November 17, 2026
New
- The app now bundles a Rust build of the CLI, which takes it from about 89 MB to about 6 MB and uses a few MB of memory while connected.
RelayRunner for Mac
Platform update · November 17, 2026
- One switch in the menu bar. Turn your Mac on as a runner, pause new jobs and see what’s running, without a terminal open. Each job still runs in its own Linux VM.
- Settings for every
connectoption. Jobs at once, VM CPUs and memory, macOS jobs, local network access and which workspaces the Mac takes jobs from. - Install. Download it or run
brew install --cask relayrunner/tap/relayrunner. It updates itself. Needs Apple silicon and macOS 14. See RelayRunner for Mac.
CLI v0.12.0
CLI release · November 16, 2026
New
relayrunner initrecognises Boat labels (boat,boat-largeand the like), keeps them as a job’s fallback, and writes relays pinned torelay.yml@v1.0.0-beta.6, which takes aboatinput.connect --eventswrites JSON events to stdout and takespauseorresumeon stdin, for apps that runconnect. Only oneconnectruns on a computer at a time now.
Fixes and improvements
relayrunner workspaces list --jsonincludes each workspace’s logo.
Pick runner sizes on the dashboard
Platform update · November 16, 2026
autorelay inputs. Writeautoin place of a label, such asblacksmith: auto, or leave the relay’s inputs out. The Router then picks that provider’s label for the job’s size. A label you write still runs as written. See Auto sizes.- Job sizes on the Router page. Click a workflow’s auto jobs under Workflows to pick each job’s size in vCPUs and a provider to try first. A provider without that size gets the next size up, or is skipped.
- A default size. Set the size auto jobs get when nobody picked one in Router → Settings.
CLI v0.11.0
CLI release · November 15, 2026
New
connectnow keeps GitHub’s runner up to date while it stays open. Every 6 hours it checks for a newer release and switches to it between jobs, so a job that’s running finishes on the runner it started with. Before, a machine left connected for weeks fell behind until GitHub stopped sending it jobs.
CLI v0.10.1
CLI release · November 14, 2026
Fixes and improvements
- When the gateway refuses a request,
pause,share,whoamiandworkspacesnow show its reason and error code, such as “Only a machine with an owner can do this (MACHINE_NOT_OWNED)”, instead of only the HTTP status.
CI traces in your observability tool
Platform update · November 14, 2026
- Telemetry. Send each workflow run to your observability tool as an OpenTelemetry trace, with a span for every job and step and the time each job waited for a runner. Spans also say where each job ran, whether the Router retried it, and the CPU and memory it used on your machines. Set it up in Settings → Telemetry. See Telemetry.
CLI v0.10.0
CLI release · November 13, 2026
New
- Report how much CPU and memory each job uses. The dashboard’s History page shows it for jobs on your machine.
CLI v0.9.2
CLI release · November 13, 2026
Fixes and improvements
relayrunner connectnow tells the dashboard how many CPUs and how much memory each job VM gets, so the Runners and Performance pages can show it.
Retries, queueing and provider usage
Platform update · November 13, 2026
- Automatic retries. The Router can re-run a job that failed because of its runner, not its own steps: the runner never started it, its machine went offline, or GitHub lost touch with it. The retry routes again, so it can land on a different runner. Turn it on with Retry jobs when their runner fails on the Router page, or per repo with
retry. See Automatic retries. - Jobs wait for a busy machine. When every machine that fits a job is busy and nothing later in your runner order can take it, the job now waits for a free slot instead of failing. See When every machine is busy.
- Skip providers that stop picking up jobs. When a hosted provider leaves jobs waiting with no runner, the Router sends new jobs further down your runner order until it recovers. See When a provider stops picking up jobs.
- Real usage from your providers. Connect Depot, Namespace or WarpBuild with a read-only token in Settings → Providers, and the dashboard pulls your real usage from them every hour.
CLI v0.9.1
CLI release · November 12, 2026
Fixes and improvements
relayrunner connectnow checks that its Linux VMs can look up hostnames before it builds the job image. When they can’t, often because of VPN or DNS filtering software that’s still running when its app is closed, it says so and how to check, instead of failing to build the image.
CLI v0.9.0
CLI release · November 12, 2026
New
-
relayrunner firewall onadds a firewall on your Mac for isolated jobs. Job VMs can reach the internet, not your Mac or your local network, and no job can remove it, even with Docker. It asks for your password, stays on after a restart, andrelayrunner firewall offremoves it. -
On a Mac with Apple silicon and Apple’s container tool,
connectnow runs each job in its own Linux VM, away from your files.--macosalso takes macOS jobs on the Mac itself, and--no-isolatedruns every job there. Without the container tool, jobs run on the Mac andconnectsays how to set it up.New
--cpusand--memoryflags set the size of each job’s VM, like a hosted runner’s size. With a size and no--concurrency, as many jobs run at once as fit. -
relayrunner connect --isolated --macostakes both kinds of job on one Mac. Linux jobs run in a VM, and macOS jobs such as Xcode builds run on the Mac itself. -
Isolated jobs now find the everyday tools a job written for
ubuntu-latestexpects: Node with npm, pip, compilers andmake,wget,zip, Git LFS, Docker Compose and theghCLI. An image given with--imageis used as it is.
Fixes and improvements
- License the CLI under Apache 2.0 and ship the LICENSE file in the npm package.
connectsays where jobs run when it starts, and how to take macOS jobs too. With--macosor--no-isolatedit warns that those jobs can read your files.initno longer warns about Docker or Linux packages on a Mac that runs jobs in a VM.
CLI v0.8.0
CLI release · November 12, 2026
New
- Docker works in isolated jobs.
relayrunner connect --isolatednow starts Docker inside each job’s VM, so jobs withservices:,container:ordocker buildrun.--local-networkuses the same job image as the default, so it builds that image once too. relayrunner connect --isolated(experimental) runs each job in its own Linux VM on a Mac with Apple silicon, using Apple’scontainertool. The VM starts from GitHub’s runner image with none of your files mounted, can reach the internet but not your Mac or local network, and is deleted when the job ends.--local-networklets jobs reach your network, and--imagestarts from another runner image.connectremoves the images it got for older runner versions, and keeps a log of what it did in~/.relayrunner/isolated.log.relayrunner workspacesshows which of your workspaces this machine runs jobs in and which it doesn’t, with its sharing.relayrunner workspaces add <name>andremove <name>change that, by workspace name, slug or id, or from a list when you leave the name out. Adding a workspace while the machine runs anyone’s jobs warns that anyone who can push to that workspace’s private repos can run jobs on it. After you approve a new machine,connectprints the workspaces it runs jobs in and how to change them, andconnectandwhoamitell a machine that isn’t in any of your workspaces apart from an account with no workspace yet.
Fixes and improvements
relayrunner connectsuggests--isolatedon Macs that can use it.- After its connection drops,
relayrunner connectwaits a few random seconds before reconnecting, so machines don’t all reconnect at the same moment after a RelayRunner update.
CLI v0.7.0
CLI release · November 11, 2026
New
relayrunner connecttells you when npm has a newerrelayrunner, with the command that updates it (npx relayrunner@latest connect, ornpm install --global relayrunner@latestfor a global install). It asks npm at most once a day, in the background, so it never slows down connecting, and aconnectleft running checks again each day. It only checks when someone is at the terminal and not in CI.connectalso tells the gateway which CLI version the machine runs, andrelayrunner --versionprints it.relayrunner connectruns several jobs at once: 2 on a computer with 8 or more CPU cores, otherwise 1.--concurrency <n>changes it. Each slot runs its jobs in its own copy of the runner (~/.relayrunner/runner/<version>/slot-<n>/), and with more than one slot each line of a job’s output starts with its slot.
CLI v0.6.0
CLI release · November 11, 2026
New
- A machine is now in every workspace you’re a member of, so signing in no longer means picking one.
relayrunner connectandloginprint the workspaces the machine is in, andwhoamilists them. The sharing question shows when any of your workspaces has someone else in it, andanyonemeans any job in your workspaces. If you aren’t in a workspace yet, signing in still works: the CLI says so and links to the GitHub install, and the machine takes jobs once you’re in one.~/.relayrunner/machine.jsonno longer saves a workspace, and files from earlier versions still load. relayrunner initkeeps a job’s Depot, Namespace, WarpBuild, Ubicloud or RunsOn label as its fallback, the same way it keeps a Blacksmith label.
CLI v0.5.0
CLI release · November 11, 2026
New
relayrunner connectnow names its terminal tab after the machine and what it’s doing, such as “RelayRunner · M3P0 · Waiting for jobs”, “Running a job” or “Paused”, and puts the old title back when it exits. Presspto pause or resume the machine without disconnecting, the same as pausing it on the Runners page.
Fixes and improvements
- On a Mac without a hostname of its own, the suggested machine name is now the Computer Name from System Settings (such as “Zach’s MacBook Pro”) instead of a generic one like
Mac.local. A hostname you set still comes first. The download message also says thatactions/runneris GitHub’s official runner.
CLI v0.4.0
CLI release · November 11, 2026
New
-
relayrunner connectgets a new machine token from the gateway each time it comes online and the old one stops working, so a copiedmachine.jsoncan’t sign in as the machine for long. If another copy does sign in while this one is online, the person who approved the machine gets an email.Before it runs a job,
connectchecks the job’s runner config: only GitHub’s files, only GitHub servers over https, and a runner named for that job. Anything else is refused and reported as a failed job. The terminal now shows which repo each job is from.--server,RELAYRUNNER_URLand saved sign-ins must use https, except forlocalhostwhile developing.The sharing prompt now says that “Anyone in the workspace” only covers jobs from repos you can open.