Skip to main content
Watchfire
Changelog

What shipped,
and when.

A highlights view of recent Watchfire releases. The exhaustive version-by-version record — every fix, every migration note — lives in the docs changelog.

v9.3.0FirestormLatest

Firestorm 9.3.0

A cleanup release. The per-session agent home directories under ~/.watchfire/<agent>-home/ accumulated forever — one directory per session for every non-Claude backend — and deleting a project left all of its directories behind indefinitely (#47).

  • Per-session agent home dirs are removed at session end
  • Deleting a project sweeps its leftover session homes

Earlier releases

v9.2.0Firestorm

Firestorm 9.2.0

A dashboard-legibility release. The list view showed different information for different projects for reasons that had nothing to do with the projects, and neither chart in the Fleet insights card rendered a single number.

  • List-view task counts no longer vanish while an agent is working
  • The per-row "shipped" chip is no longer restricted to five projects
  • The fleet insights cache is versioned
v9.1.0Firestorm

Firestorm 9.1.0

A bug-fix release for Insights. Project Insights, fleet Insights, the CSV/Markdown exports and the weekly digest all showed zeros or near-zeros, because almost no completed task ever received a completed_at timestamp — and every rollup filters on it.

  • The daemon now stamps completed_at on the done transition
  • Insights recovers the ~580 pre-9.1 tasks
v9.0.0Firestorm

Firestorm 9.0.0

Firestorm turns Watchfire inside out: instead of only driving coding agents, Watchfire is now driven by them. watchfire mcp serve exposes the whole orchestrator to any MCP-capable client — Claude Code, Codex, Gemini CLI, opencode, Copilot CLI, or a custom agent — as an 18-tool factory. The outer agent plans and reviews; Watchfire manufactures the code in sandboxed, git-worktree-isolated runs and merges the results. The canonical loop is create_task → run_task → wait_for_task → get_task → get_task_diff → iterate.

  • watchfire mcp serve — the stdio MCP server
  • Project tools:
  • Task-factory tools:
v8.0.0Inferno

Inferno 8.0.0

Inferno is the parallel-workspaces tentpole — the first feature-forward major since v4 "Beacon", built for supervising many projects at once. The Electron GUI goes multi-window: a main-process window registry replaces the single mainWindow, opening one independent window per project (single-instance lock, per-window state + session restore, Cmd+N and window cycling, IPC fan-out, and per-window PTY routing so a terminal's bytes and OS notifications never cross windows). Each project window flips to a chat-primary layout with the agent terminal as the wide left pane and Tasks/Definition/Insights/Secrets/Trash/Settings as a right reference region. The plain markdown <textarea>s become a real CodeMirror rich editor (formatting toolbar + source ⇄ split ⇄ preview, closing #22), wildfire mode lands in the GUI behind a confirm-gated start with a live Execute → Refine → Generate phase indicator, and the promoted Dashboard becomes mission control — a live home window with per-project wildfire phase, cross-project needs-attention with click-through, and a stretch always-on-top mini-monitor. Finally, code-output analytics measure what the agents actually shipped: per-task <n>.metrics.yaml captures commits/files/lines/merge-kind, rolled up into project and fleet Insights, the GUI's KPI cards and churn-by-day chart, mission-control "shipped" lines, and the CSV/Markdown exports plus weekly digest.

  • Multi-window GUI foundation
  • Per-window state + session restore
  • "Open in new window" affordances + window shortcuts
v7.4.0Forge

Forge 7.4.0

Forge 7.4 closes a class of "wildfire stops even though there's a ready task sitting right there, and drops back to chat" reports. Traced live on a real project, the symptom turned out to be three independent daemon bugs plus a runaway log that buried the evidence: Generate produced a ready task, the chain stamped it started, but no agent ever ran it — and the one log line that would have explained why was drowned under hundreds of MB of self-referential watcher spam. This release fixes the runaway log at the source, moves the verbose per-project trail into per-project log files so the global daemon.log stays readable, makes a launch failure unable to strand a ready task, and stops the issue detector from false-positiving on ordinary agent output.

  • The daemon log no longer feeds an infinite fsnotify loop
  • First run after upgrade reclaims an oversized legacy daemon.log
  • A launch failure can no longer strand a ready task and silently drop to chat
v7.3.0Forge

Forge 7.3.0

Forge 7.3 is primarily a GUI release. The Electron app gains a focus-chat mode that collapses the center column so the right panel (Chat / Branches / Logs) takes the full row, and the running Watchfire version now sits under the sidebar logo so you no longer have to dig through Settings → About to know what you're on. The version bump to 7.3.0 lands across version.json, gui/package.json, and gui/package-lock.json. One daemon-side fix closes the size-cap deferral v7.2.1 left open: ~/.watchfire/daemon.log is now bounded after a user's log grew to 300 GB.

  • GUI focus-chat mode
  • GUI version under the sidebar logo
  • All shipped components advertise 7.3.0

Looking for every patch release, breaking change, and upgrade note? See the full changelog.

Subscribe by email

Get every new post in your inbox. Roughly one a fortnight — opt out from any email.

Subscribe by feed

Or wire it into your feed reader.