What's new in Runway

Do this after updating

• Nothing to click: Runway updates the Agent Runway skills in Claude Code and Codex by itself after this update. What's New says when it's done.
• Restart your Claude Code or Codex sessions so they load the new skills.

Fixed

• Skills now update themselves after every app update, only where they're already installed. If that fails, What's New says why and "Update the skills" is there to try again.
• Claude Code could keep running an old copy of the skills while showing the new version number. Runway now reads the version Claude Code actually uses.

Release on GitHub

Do this after updating

• In What's New, click Update the skills. It asks first, then updates Agent Runway in Claude Code and Codex.
• Restart any Claude Code or Codex sessions you have open, so they pick up the new skills.

New

• Hands-on tickets. When you file work, the parts that need you (a device, the simulator, how it feels) become hands-on tickets. Runway never starts them. They show as "Hands-on · yours", with Copy prompt and Mark done.
• The Agent Runway plugin goes to 0.3.0, with 15 skills: the new hands-on skill, and six build skills from Superpowers (writing-plans, executing-plans, subagent-driven-development, test-driven-development, systematic-debugging, verification-before-completion).
• file-tickets sorts work into Runway tickets and hands-on ones, and asks for checks a reviewer can run.

Fixed

• A long question or review no longer pushes the toolbar off the window. The ticket panel scrolls.
• The function reviewer can now run the experiment a check asks for (change a value, see a test fail), in a throwaway copy.
• Swift and iOS builds run under Codex: it may write Xcode's and SwiftPM's caches, without a looser sandbox.

Release on GitHub

• Timers on every card: a running ticket shows its stage and how long ("Build · 12 min · 38 min in all"), Up next shows how long it has waited, Needs you shows how long it has waited for you, and Done shows how long it took.
• The ticket panel has a Time section: when it started, and for a finished ticket how the time split between build, fix passes, reviews, waiting for you and the queue. runway show prints the same.
• "No" on a merge question now closes the pull request (its branch stays), the same as dropping a ticket.
• A first build now always starts from the newest copy of your base branch. Before, it could start from an older one.
• The Board, Activity and Stats tabs no longer wrap when a long status message is showing.

Release on GitHub

• A repo no longer needs a runway.json before Runway's sessions can run its tests. When you add a repo, Runway finds the check command and the build and run commands (a Swift package in a subfolder too) and keeps them in Runway, so nothing has to be committed first. A runway.json on the base branch, when it has them, still wins.
• A repo with no check command says so on the board, with "Set check command…". Right-click a repo to change its commands any time.
• "Add a repo…" in the sidebar now opens the folder picker and shows what Runway found.
• In Terminal: runway repo check <repo> shows, sets (--check, --allow) or suggests (--suggest) them.

Release on GitHub

• After an update, Runway's loop (the part that starts tickets) could stop and not come back, so nothing ran. The app now restarts it if it stops, and a new loop waits for the old one to finish instead of giving up.
• When tickets are up next but nothing can start, the board says why in one line, for example "Nothing can run: 4 tickets wait on T-4, which needs you", with a button to show that ticket. The menu and side panel say it too.

Release on GitHub

• A ticket no longer waits for "Mac is busy" when nothing else from Runway is running. The first session only waits if your disk is nearly full or memory pressure is critical.
• Runway now measures how busy the CPU really is, the same figure Activity Monitor shows. Extra sessions wait only when the CPU is under 15% idle or there isn't memory for one more. Spotlight indexing or your own sessions no longer count against it.
• A waiting ticket says what's short and the limit, for example "CPU 92% used, limit 85%". The runner shows "CPU 38% used · 9 GB free".
• "Start anyway" in a waiting ticket's panel starts it without the check, just that once.

Release on GitHub

• Several tickets in a repo now run at once when the files they touch don't overlap. A ticket that doesn't list its files runs on its own.
• Before starting another session, Runway checks this Mac has the memory, CPU and disk to spare. If it doesn't, the ticket waits and says why, and starts once there's room. Nothing that's running is stopped.
• Right-click a runner to set its max sessions. The first setup picks a number to suit your Mac.
• Blocked tickets say what they're waiting on, and the tickets holding them up say what they block. Take back a blocker from the ticket's Waits on list to finish it in your own session and unblock the rest.
• The update window now shows just these notes, not the whole release page.

Release on GitHub

• Clear things away. Right-click a repo to archive it (off the board, nothing deleted, Unarchive brings it back) or remove it (its tickets and run history go; your folder, branches and pull requests stay).
• "Clear done" on the Done column takes finished tickets off the board. They still count in stats, and Undo puts them back.
• Right-click a ticket for what fits its state: chat about it, take it back, go or no, open the PR, pin it to a runner, or delete it.
• "Chat about this ticket…" and "Chat about this repo…" copy a prompt for Claude Code or Codex that looks things over without taking anything back.
• Right-click a runner to pause or resume it, and set a repo's main computer from its menu.
• In Terminal: runway repo archive, unarchive and remove, runway clear-done, runway delete, runway show --prompt, runway status <repo> --prompt and runway repo main.
• The Agent Runway skills now update with the app: if Claude Code or Codex has an older version, What's New offers "Update the skills" (it asks first).
• Before Runway changes its database's structure, it saves a copy in ~/.runway/backups (the last five are kept). Your tickets and history carry over.

Release on GitHub

• First launch walks you through setup: what Runway does, what it found on this Mac, what it will install before it installs it, and the first prompt to paste into your agent.
• On later launches Runway checks again and only shows the walkthrough if something is missing.
• What's New: this screen. It shows after an update, and "What's New…" in the menu opens it again.
• runway doctor checks without creating anything; runway init makes Runway's folder and database.
• A real app icon: a paper plane taking off, with a matching paper plane in the menu bar.
• Install from a disk image: drag Runway into Applications. If you open it from Downloads or the disk image, it offers to move itself there, since updates only work from Applications.
• The Agent Runway plugin carries every skill its workflow uses (new: map, grill, prototype and spec), so you install nothing else.

Release on GitHub

• The first release of Runway: you shape the work in Claude Code or Codex, file it as tickets, and Runway builds and reviews them.

Build and review

• Each ticket is built in a fresh copy of your repo by Claude Code or Codex, on this Mac.
• Two fresh reviews check it: one reads the code, one tries what the ticket asked for.
• One engine is enough. With both, each reviews the other's work.

Merge or ask

• Low-risk work that passes both reviews and your checks merges on its own.
• Everything else waits for you on the board, with the question and a recommended answer.

Hands off

• The board shows how many merges needed nothing from you, how long tickets take, and what they cost.
• Take back any ticket: Runway stops, keeps the branch, and copies a prompt so you can carry on in your own session.
• When the same thing keeps stopping tickets, Runway files a retro ticket to fix it.
• Head-to-head re-runs a finished ticket with each engine, to compare them.

Release on GitHub