Skip to main content
CHANGELOG

What shipped

Released versions of Harmony only, read from the product's Keep a Changelog file. Unreleased work is not listed here: if it is not in a version heading, it has not shipped.

Latest released v3.25.8 · · 65 releases

Download the current build from /download. Channel and exact version always come from the live release manifest.

Releases 16–20 of 65

Page 4 of 13

v3.14.0

Added

  • Channel mentions now reach agents in any workspace, not just the one you're looking at. A mention addressed to a pane in a background workspace used to sit undelivered until you switched to that workspace. The renderer now polls the event stream across all local workspaces in a single request (union scope), so a cross-workspace mention lands on its target pane immediately and the agent answers without you having to switch.

Fixed

  • Reattaching no longer floods a reused shell with cursor-position replies (CPR feedback storm). On reattach the daemon replayed persisted scrollback verbatim and xterm re-executed the one-shot terminal queries (DSR/CPR, DA, DECRQM, OSC color, DCS) a prior TUI had emitted, each firing a live auto-reply into the fresh shell. A pane left running while detached could accumulate thousands; reattach answered them all at once, pinning zsh and the daemon near 100% CPU. Query sequences are now stripped from the replay before xterm sees them; live output is untouched.
  • A mention to an idle background agent now delivers instead of hanging until an unrelated repaint. An agent idle since its pane attached never re-emits a status pattern, so its status stayed unknown and the paste gate held it busy forever. Unknown status is now held only for a short grace window, then delivered, guarded so a genuinely running-but-quiet agent is never pasted mid-turn (an output-quiet check plus a hard hold ceiling).
  • Splitting a pane no longer crashes zsh on macOS. The zsh shell-integration prompt marker (OSC 133;B) was appended without a %{...%} zero-width guard, so zsh's line editor miscounted the prompt width and could crash (SIGBUS in zle) during the resize sweep a split triggers. The marker is now width-guarded, matching the bash and PowerShell integrations.

v3.13.0

Added

  • Agent panes are now first-class channel members (R2 Principal registry). The channel roster lets you add a specific agent pane (e.g. w8-1(claude)) as a member directly, not just a workspace. The roster reads as "you + agent panes", each agent showing a live/stale dot for whether its pane is alive. Previously every member was an anonymous local-ui row, which caused the "I added it as a member — why doesn't it hear me?" confusion.
  • New daemon Principal registry (principals.json) that unifies every actor (human / pane-agent) under one address space. On daemon restart, pane-agents are backfilled to stale (the daemon cannot prove a pane is still alive) and only a renderer re-registration flips them back to live — this structurally blocks the stale-read-as-live class of state drift.

Changed

  • The channel wake worker now targets a member's pane PTY directly via its principal coordinate. This fixes a defect where the auto-name memberId (w8-1(claude)) never matched the old agent-slug heuristic, so per-pane mentions now reach the exact pane.
  • Removed the internal local-ui token from message senders and the roster — it now renders as "you" (the on-disk schema stays backward compatible).

Fixed

  • Added a channel-membership cleanup hook on workspace/pane deletion — dead-workspace member rows no longer linger in the channel roster forever.

v3.12.4

Fixed

  • Dev only: npm start no longer opens to a blank, flickering window on macOS. Electron loaded the renderer from http://localhost:5173, which macOS resolves to IPv6 (::1) first, while the Vite dev server listens on IPv4 (127.0.0.1) — so the load failed and Electron retried in a loop. The dev-server URL is now normalized to 127.0.0.1. No effect on packaged builds.

v3.12.3

Fixed

  • Splitting panes no longer randomly kills shells. Splitting a pane (or reattaching after a reboot) could kill a pane's shell with a bus error, leaving "[process exited]" — seemingly at random. The real trigger: during a split or layout transition the pane is momentarily only a few characters wide, and resizing zsh below 7 columns crashes it outright (a macOS zsh 5.9 bug, reproduced 100%). wmux now never applies a terminal size below a safe floor (10 columns), and skips resize signals that don't change the size. Verified: the same narrow-resize test kills 5/5 shells on the old build and 0/5 on this one.

v3.12.2

Headline: you can now @-mention an agent running in your own workspace from a channel — the mention reaches that exact pane, while an agent still never pings its own pane in a loop.

Added

  • Same-workspace @-mentions now deliver. Before, a channel message could only mention agents in other workspaces — your own workspace's agent panes were hidden from the @-picker and any mention of them was dropped. Now the composer offers same-workspace agent panes as mention targets, and a mention routes to that specific pane as an inbox task. A human mentioning their own workspace's agent, and an agent mentioning a sibling pane, both work.

Changed

  • Channel messages carry the sender's pane identity (senderPtyId). This lets the receiving side tell a legitimate sibling mention (pane 1 → pane 2 in the same workspace) apart from a true self-loop (an agent mentioning its own pane). Self-loops are dropped; a workspace-level mention with no specific pane on a self-authored post stays conservative and is not routed. Older messages without the field degrade safely.