Godspeed Code 0.5.9

Added

• Review and merge from the PR pane. Approve, request changes or comment; reply to review
  threads and resolve or unresolve them; merge with the methods the repository allows (after a
  confirmation that names the repository, PR, base, head and method, and only if the branch hasn't
  moved); enable or disable auto-merge; mark a draft ready; close or reopen. Each action shows
  progress and GitHub's reason when it refuses (for example "Review required by branch
  protection"). Uses your gh login; GitHub only for now.
• PR watch that wakes the chat. A watched pull request is polled every 90 seconds (backing off
  on errors and rate limits, pausing when the app is idle). Newly failed checks (with the failing
  log tail), new review comments and a new merge conflict are queued into the PR's chat and shown in
  Needs you. On by default for PRs a Godspeed chat opened, toggled per PR from the PR pane; the
  sidebar badge shows an eye on watched PRs. Each event is reported once, the agent's own comments
  never wake it, and wakes are capped per PR per hour. Optional per-PR "auto-merge when green"
  turns on GitHub auto-merge once checks pass and the PR is approved; nothing is ever approved for
  you.
• More agents from the ACP registry. Settings → Providers → More agents lists the public ACP
  agent registry (name, publisher, version, install size) and installs, updates or uninstalls an
  agent in one click, into Godspeed's own data folder. Factory Droid, GitHub Copilot CLI, Gemini
  CLI and Kimi CLI run through the ACP driver like any other provider. Registry data is treated as
  untrusted: nothing runs unless it is pinned to a checksum (SHA-256 for binaries; exact npm
  versions checked against npm's sha512, installed without lifecycle scripts).
• Several instances of one agent. Each provider can have named instances with their own
  binary, config dir (CLAUDE_CONFIG_DIR, CODEX_HOME, …), env vars, default and custom models
  and account. Secret-looking env values go to the OS keychain, never to settings or logs. Pick an
  instance in the model picker, where it lists under its provider; existing chats keep the default
  instance. Receipts name the instance; usage and telemetry still count by provider.
• Run on a server. Settings → Devices → "Run on a server…" installs the headless engine on a
  Linux machine over your own SSH (keys, agent and ~/.ssh/config; never a password), or on a
  Tailscale machine picked from a list. It checks the connection (with clear host-key and auth
  errors), downloads the release for the server's arch from GitHub and verifies its sha256,
  installs into ~/.godspeed/app without sudo, signs the server into your workspace (you sign in
  in the browser and paste the code) and starts it as a systemd --user service with lingering
  (or a nohup supervisor plus @reboot cron). The server then shows up as a device to start
  chats on, so agents keep running with the laptop closed. Saved servers show Online, version and
  uptime, with Update, Stop, Start and Uninstall; re-running setup or checking status never
  restarts a running engine. godspeed login --stdin-code [--org ID] is the sign-in it drives.
• Linux release builds. Every v* release gets godspeed-<v>-linux-x86_64.tar.gz and
  -linux-aarch64.tar.gz with sha256 files and a manifest-linux.json, built by GitHub Actions.
  Linux installs update from that manifest; a release whose Linux build isn't uploaded yet is
  skipped instead of downloaded unverified.
• Sub-agents in their own worktree. MCP create_chat and create_chats take worktree:
  "new" starts the chat in a fresh git worktree on its own branch, off the parent's branch or a
  named base, set up like the app's worktrees (copied .env files, ports, setup commands);
  "parent" (the default) shares the parent's checkout; or name an existing worktree by folder or
  branch. Conductor caps still apply, and a refused chat leaves no worktree behind. A side chat on
  its own branch shows it on the parent's card (ported from T3 Code).
• Worktree cleanup and storage. Settings → General → Worktrees can delete worktrees whose
  branch is merged, or that sat untouched for 7, 14 or 30 days (both off by default), running their
  teardown commands. Worktrees with uncommitted changes, unpushed commits or a running chat are
  always kept. A storage list shows every Godspeed worktree with its size on disk, branch, last
  activity, state and chat, with "Delete now" and "Delete all eligible" (ported from T3 Code).
• Select several sessions at once. Cmd-click or Shift-click sidebar rows (Cmd+A in the sidebar
  takes them all, Esc lets go) and settle, snooze, mark read or unread, pin, archive or delete them
  together from the bar at the foot of the sidebar. Cmd+Z undoes a whole batch (ported from T3 Code).
• Prompt recall and stash. Up in an empty composer brings back the prompts you sent in that chat
  (Down goes forward again). Cmd+S sets the draft aside, attachments included, and the "Stashed"
  chip brings it back or deletes it; stashes stay on this Mac across restarts. Rebind it in
  Settings → Shortcuts (ported from T3 Code).
• Dock badge with the number of chats waiting on an approval or an answer. Turn it off in
  Settings → Appearance → "Show badge on Dock icon".

Changed

• Parallel agents share build slots. Agents and terminals run their cargo and make builds
  through one shared jobserver, so three or four agents building at once no longer start a rustc
  per core each (in testing, peak rustc processes went from 24 to 9 and memory from 4.7 GB to
  2.0 GB). Your own CARGO_BUILD_JOBS, MAKEFLAGS or build.jobs still win. sccache is used
  when it's installed. Settings → General → Builds shows the slots.

Fixed

• A chat whose worktree folder was deleted gets it recreated before its next turn, instead of
  failing.