Native on macOS and Windows · Linux beta · MIT

Where terminal agents work together.

Claude Code, Codex, OpenCode, Cursor CLI, Grok Build, Antigravity CLI, Copilot CLI and pi on the same task, in one mission. Each agent keeps its own TUI in a real terminal, and the lead brings the decisions to you.

Runner is a desktop app. Send yourself the link, then install it on your Mac or PC.

macOS 12+ · Apple Silicon / Intel · Also for Windows x64 and Linux beta

Windows 10 1809+, x64 · Also for macOS and Linux beta

Linux beta · ARM64 and x64 · .deb or tarball

macOS (Apple Silicon and Intel), Windows x64 and Linux beta.

macOS 12+ (Apple Silicon and Intel) · Windows 10 1809+, x64 · Linux beta

Remote control across computersPrivate beta
Fix the cancel status

youGOAL

Esc or Ctrl+C should leave the slot Idle, not Working. @coder fixes it, @reviewer reviews, @qa reproduces it live before and after.

@coder→ @reviewer

Pushed fix/783-cancel-status. The Esc path now sets the hook interrupt; three new reducer tests cover Esc, Ctrl+C and a cancel during a tool call.

@reviewer· signal · review_findings ·

Ctrl+C during a tool call still reports Working for about a second.

@coder→ @reviewer

Fixed: Ctrl+C during a tool call now goes straight to Idle. Added a fourth test.

@qa

Reproduced on 0.12.7, fixed on the branch, with Codex and Claude Code.

@coderASKS YOU

Review is clean and CI is green on macOS and Windows. Open the pull request?

Add role

Its session stops and it leaves the team. Its messages stay in the feed, and its handle cannot be reused in this mission.

‹ Fix the cancel status ⌄ ···

youGOAL

Esc or Ctrl+C should leave the slot Idle, not Working. @coder fixes it, @reviewer reviews, @qa reproduces it live before and after.

@coder→ @reviewer

Pushed fix/783-cancel-status. The Esc path now sets the hook interrupt; three new reducer tests cover Esc, Ctrl+C and a cancel during a tool call.

@reviewer→ @coder

Ctrl+C during a tool call still reports Working for about a second.

@coder→ @reviewer

Fixed: Ctrl+C during a tool call now goes straight to Idle. Added a fourth test.

@qa

Reproduced on 0.12.7, fixed on the branch, with Codex and Claude Code.

@coderNeeds your input

Review is clean and CI is green on macOS and Windows. Open the pull request?

This is a live demo. Answer @coder on either one and both move on.The desktop app, scaled to fit. Switch scenes above.

Claude Code
Codex
OpenCode
Cursor CLI
Grok Build
Antigravity CLI
GitHub Copilot CLI
pi

Use each agent’s own models and effort choices. Manage supported Skills and MCP catalogs from its Settings page.

Answer your agents from anywhere.

Runner for iPhone connects to Runner on your computer, where the agents keep running.

  1. Open a session that needs youAmber marks show what's waiting on you.
  2. Answer the leadPick a choice in the mission feed, and the crew carries on.
  3. Approve an editTap ↵ in Claude Code's real terminal.

Private beta on TestFlight. Needs Runner on a Mac, Windows or Linux computer.

+

AGENTS 7⌄

TERMINALS 1⌄

Windows PCOffline · seen 2 h ago

This is a live demo. Tap a session that needs you.

Your agents,
across computers.

Pick another computer in Runner and keep working with its live terminals, chats and missions.

  • Start chats and missions remotely
  • Pair once with a PIN
  • Encrypted end to end

Private beta · Join the waitlist for an invite.

Mac Studio · Claude CodeIdle

› Draft the release notes.

The release notes are ready.

✓ Summarized the changes
✓ Linked the merged pull requests

Ready for your review.

● Read(crates/runner-daemon/src/remote/channels.rs)
└ Read 212 lines

● The grant goes back once the frame is drawn, so a slow reader only stalls its own channel. Running the remote tests next.

● Bash(cargo nextest run -p runner-daemon remote)
└ 148 tests run: 148 passed

Try switching computers. This is a local preview.

Role, crew, mission.

Running agents side by side is easy. Runner is for the other thing: one task, different roles, a shared feed, and one lead who pulls you in when the decision is yours.

Running agents side by side is easy. Runner is for one task, different roles, a shared feed, and a lead who pulls you in when the decision is yours.

01 role

A reusable agent: a runtime, a model, a system prompt and a working directory.

02 crew

Roles composed into named slots with exactly one lead, plus the team conventions every mission inherits.

03 mission

One goal, a team that can change. Start with a crew, add or remove roles as needed, and keep the same feed and live terminals.

One agent, configured once.

A role is a reusable agent: a runtime, a model, a system prompt and a working directory. Any crew can put it in a slot, and it brings its prompt and settings along.

A role is a reusable agent: a runtime, a model, a system prompt and a working directory. Any crew can put it in a slot.

  • Claude Code, Codex, OpenCode, Cursor CLI, Grok Build, Antigravity CLI, Copilot CLI or pi
  • Model, effort and prompt saved with the role

Implementation (Claude)

@impl-claude

Runtime
Claude Code
Model
opus[1m]
Effort
xhigh
Command
$ claude
Working directory
~/repos/runner

Crews using this role · 2

claude pair LEADas @coder
›
release crewas @implementer
›
System prompt48 lines · 2.9 KB

Implementer

You take a concrete task and ship the code, the tests and the migration of state if any, without expanding scope or freelancing on parallel work.

Before you start

  • Read the brief once, carefully, before touching code.
  • Ask when a load-bearing detail is ambiguous: a missing path, a contract you cannot infer. Don't ask about naming or style; those are reversible and cheap.

Pull requests

If the mission authorizes a PR, watch CI after opening or updating it:

gh pr checks <pr> --watch
Show all 48 lines

Match the surrounding code. Run the checks before reporting back. Keep side effects within the mission authorization.

Set up a crew once.

A crew puts roles into named slots with exactly one lead. Its conventions are added to every slot's prompt when it runs a mission, and its page keeps every mission it has run.

A crew puts roles into slots with one lead. Its conventions join every slot's prompt when it runs a mission.

  • Override runtime, model or effort for one slot
  • Start a mission straight from the crew page

release crew

5 slots · lead @lead

Slots · 5

• overridden for this slot

Team conventions16 lines · 0.7 KB

Branch

  • One crew, one release branch. The lead owns the plan and the merge order; nobody merges without the lead's go.

Reporting

Run the checks before you report back, and paste the tail of the output when they fail:

make verify
  • Ask the lead, not the human, when a detail is ambiguous.

Release

  • Nobody tags, publishes or cuts a nightly. The human does.

Added to every slot's prompt when this crew runs a mission. Direct chats ignore it.

Missions14 run · none live
ⓥ Release v0.11.21h 12m Sep 23
ⓧ Release v0.11.1 aborted18m Sep 15
Show all 14 missions
Release v0.11.0 Sep 8

One mission. A team that adapts.

Add a role when the work needs another pair of hands. Remove it when its part is done. The mission keeps its feed and every remaining agent’s conversation. Each terminal is one tab away.

Add roles as the work grows; remove them when their part is done. Keep the same feed and the remaining agents’ conversations.

  • Add and remove roles while the mission runs
  • Stop, resume or restart one session independently
Fix the cancel status

• Explored
 └ Read reducer.rs
  Search fn interrupt in session

• Ran cargo test -p runner-backend reducer
 └ test result: ok. 214 passed; 0 failed

• Edited reducer.rs (+18 -4)

• Working (42s • esc to interrupt)

gpt-5.6-sol xhigh · fix/783 · weekly 92% left

Add role

Its session stops and it leaves the team. Its messages stay in the feed, and its handle cannot be reused in this mission.

Quit Runner. Your agents keep working.

Runner’s local daemon, runnerd, keeps chats and missions alive when you quit, or if the app crashes. Reopen Runner to reconnect to the same sessions.

Runner’s local daemon keeps chats and missions alive when you quit, or if the app crashes. Reopen to the same sessions. The CLI works with the app closed.

  • Crew coordination continues in the background
  • The CLI works with the app closed

Quit Runner

3 sessions running · 1 working

Interactive website demo. These controls only affect this example.

What happens to the demo agents on quit

Know when an agent needs you.

While Runner is in the background, native macOS and Windows notifications bring you back for input, a finished chat turn, or an error. Choose which chat and mission events notify you in Settings → Notifications.

Get native notifications while Runner is in the background. Click to open the chat or mission. Chat alerts start on; mission alerts are opt-in.

  • Click a notification to open its chat or mission
  • Chat alerts on by default; mission alerts opt-in

Notifications

Choose when Runner notifies you while the app is in the background.

System

Notifications are onBanner style and sound are set in System Settings → Notifications → Runner.
Chats
Missions

Try the switches. Changes stay in this preview.

Split chats. Work side by side.

Keep multiple agents in view without switching tabs. Split right or down as far as the window allows, and drag a pane by its grip to rearrange it. Each pane keeps the agent’s own TUI in a real terminal.

Keep multiple agents in one tab. Split right or down, and drag a pane by its grip to rearrange it. Each pane keeps the agent’s own TUI.

  • ⌘D and ⇧⌘D split right or down
  • A spinner or a dot on every tab that needs a look

Claude Code v2.1.278
Opus 5 (1M context) · Claude Max
~/repos/runner

~/repos/runner | Opus 5 (1M context) · xhigh
⏵⏵ auto mode on (shift+tab to cycle)

CurrentSessionsIssuesPull requestsGists

Copilot v1.0.83 uses AI.
Check for mistakes.

Tip: /theme└ View or set color mode

~/repos/blogPlan: 106/1,500 (7% used)

← open sidebar · / commands · ? helpGPT-5.6 Terra

pi v0.85.1
escape interrupt · ctrl+c clear/exit · / commands

[Skills]
runner, commit

What changed in the last release?

Planning to read the changelog

read CHANGELOG.md
(ctrl+o to expand)

⠋ Woolgathering...

~/repos/runner
↑3.1k ↓120 $0.012 1.2%/272k gpt-5.6-sol • high

• Explored
 └ Read reducer.rs
  Search fn interrupt in session

• Ran cargo test -p runner-backend reducer
 └ test result: ok. 214 passed; 0 failed

• Edited reducer.rs (+18 -4)

• Working (42s • esc to interrupt)

gpt-5.6-sol xhigh · fix/783 · weekly 92% left

Read the files. Stay with the agent.

Browse your project and read the agent’s work beside its terminal. Open code with syntax highlighting, or read Markdown as a page.

  • File tree with live git status
  • Jump from a terminal path to the file
  • Open in your editor when it’s time to edit
Choose a file to preview
Add a health checkCodex

› Add a health endpoint and document it.

• Explored
 └ Read package.json, src/server.ts

• Edited src/health.ts (+8 -0)
 └ README.md (+11 -0)

• Ran npm test
 └ Tests: 12 passed; 0 failed

─ Worked for 24s ─────────────────

Added a lightweight health check.

gpt-5.6-sol xhigh · feat/health · weekly 92% left

FilesRead-only
acme-web2 changed
src
{}package.json
import { uptime } from 'node:process'; export function health() {  return {    status: 'ok',    uptime: Math.floor(uptime()),  };}

Health check

GET /health

Check that the service is running.
Returns its status and uptime in seconds.

{ "status": "ok", "uptime": 42 }
# Health check

`GET /health`

Check that the service is running.
Returns its status and uptime in seconds.

```json
{ "status": "ok", "uptime": 42 }
```
Try it: select health.ts or README.md. Switch Markdown between its rendered page and source.File preview guide

Also in the box

Multi-window

A mission on one screen, a wall of chats on the other.

Skills and MCP per agent

Browse each agent’s Skills and MCP tabs. For Claude Code, catalogs follow the account you choose.

Resume stopped agents

Choose to stop agents on quit, and they resume their conversations on the next launch.

Projects

Bind a directory once; chats and missions started there inherit it.

Plan usage at a glance

Track Claude Code and Codex limits. Choose sidebar badges, refresh intervals and near-limit alerts.

Active view

See running work and items that need you across projects. Switch views with ⌘. on macOS or Ctrl+. on Windows and Linux.

Light and dark

Follow your system or choose a mode. Each has its own terminal palette.

Launch options

Choose how agents start and copy the exact chat or mission command before launching.

Background agent updates

Update supported agent CLIs while other panes stay usable. Required updates finish before the waiting chat starts.

Drive Runner from your agents.

Everything in the app is a runner command too, on macOS, Windows and Linux beta. Runner installs a skill for every agent it finds, so agents can start missions themselves, and Runner tells them when one settles or needs you.

Everything in the app is a runner command too, including on Linux beta. Runner installs a skill for every agent it finds, so agents can start missions themselves, and Runner tells them when one settles or needs you.

$ runner help
runner — operate Runner from a shell or a mission session

USAGE
  runner status
  runner project list|show|create|rename|delete
  runner role list|show|create|update|delete
  runner crew list|show|create|update|delete|add|set|…
  runner mission list|show|start|stop|resume|link|unlink|feed|…
  runner chat start
  runner msg post|read
  runner ask --human <prompt> --choices <a,b,...>
$ runner help
USAGE
  runner role list|show|create|…
  runner crew list|show|create|…
  runner mission start|feed|…
  runner chat start
  runner msg post|read
  runner ask --human <prompt>
Runner

Put your agents on one mission.

Signed builds for macOS on Apple Silicon and Intel, and Windows x64, with Linux in beta. Updates in place.

Apple Silicon / Intel · Also for Windows x64 and Linux beta

Also for macOS and Linux beta

Linux beta · ARM64 and x64 · .deb or tarball

macOS (Apple Silicon and Intel), Windows x64 and Linux beta.