Skip to content

Runner 0.6.4

Choose a tag to compare

@github-actions github-actions released this 25 Aug 13:42
· 891 commits to main since this release

The headline is terminals: a pane can now hold a real shell instead of a chat, so git diff --stat or a long pnpm dev runs beside the agent editing the code it serves — without leaving the app or burning a chat on it.

What's new

  • A pane can hold a terminal. Your $SHELL in a real PTY, in any pane a split can build. Start one from New terminal — in the Recent and project + menus, which open it in a new single-pane tab, in an empty pane's placeholder, or from the command palette. There is no modal: a terminal has nothing to configure that cd does not cover. It opens in the cwd of the focused sibling session, else the active project's directory, else your default working directory, else $HOME, so it lands where the agent beside it is working.
  • Split shortcuts. ⌘D adds a side-by-side pane and ⇧⌘D a stacked one, growing a tab from one pane to two to at most three. The new pane stays empty so you choose New chat or New terminal in place. The layout button's tooltip advertises both.
  • A slimmer pane identity line. The pane header drops from 34 px to a 26 px line — icon, name, status dot, ⋯, with × alone at the far right. ⋯ holds Stop (⌘.), Rename…, and Archive.
  • Rename a pane. ⋯ → Rename…, or a double-click on the name, edits it inline. Enter commits, Escape reverts, and an emptied value restores the default. The name survives closing and reopening the pane, moving it to another pane, and relaunching the app.
  • ⌘. stops the session in the focused pane — chat or terminal.
  • Terminals come back live after a relaunch. A fresh shell at the pane's recorded cwd: no command replay, no scrollback. Chats still follow your resume-on-launch setting. If the recorded directory no longer exists, the shell opens at the nearest existing parent and says so in the pane rather than silently landing in $HOME.
  • Shell exited card. A shell that exits shows its exit code, shell, and cwd with Restart and Close — the terminal twin of Chat paused.
  • Terminals never nag for attention. No status dot, and they are left out of working / unread / needs-you: a streaming pnpm dev is not "working", and its going quiet is not "done".

Closing a terminal is permanent

A chat archives and can be restored from Settings → Archived; a terminal cannot. So Runner asks before it takes one away. Closing a single terminal confirms only when a foreground process is still running — a shell sitting at its prompt closes silently. Archive all on a tab that mixes chats and terminals always confirms, and says how many of each it will touch.

Upgrading

Sparkle offers this update to every 0.6.x install on Apple Silicon. 0.5.x installs still bridge automatically: they land on 0.6.0 first, then Sparkle brings them here — the bridge stays in place through the 0.6.x line.

Download

  • Apple Silicon: Runner-0.6.4-arm64.dmg. macOS is packaged for ARM64 only since 0.6.2; Intel Macs are not supported.