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).
Roadmap.
What we’ve shipped, what we’re building now, and what’s on deck. Watchfire is open source, so everything here is also where you can help.
Now shipping.
The most recent releases — pulled straight from the changelog so this stays current automatically.
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.
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.
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.
Browse the full release history in the changelog.
In progress.
Actively in flight. These are the pieces being shaped, prototyped, or merged behind a flag right now.
Windows daemon support
Bring `watchfired` to Windows with native service installation, signed binaries, and a Windows-shaped sandbox replacement for `sandbox-exec`. macOS and Linux already ship; Windows is the last gap.
Per-task cost tracking in the GUI
Surface live token spend and cumulative cost per task in the Electron GUI, broken down by agent backend. Backed by transcripts already written to disk — no extra telemetry.
OpenAI Codex CLI backend stabilization
Lock in Codex CLI as a first-class backend alongside Claude Code: tighter error surfaces, consistent transcript layout, parity with the chat/task/start-all modes.
Editor-mode TUI keybindings
Vim and Emacs profiles for the TUI — modal navigation, named registers for task IDs, customisable bindings via `~/.config/watchfire/keys.toml`.
Beacon v2 protocol
Second iteration of the daemon's two-way integration surface: streaming task updates, scoped capability tokens, and a stable wire format for third-party clients.
Docs search powered by the local daemon
Replace the static search index on `/docs` with a daemon-served endpoint so search results reflect the version of Watchfire you actually have installed.
On deck.
The next quarter's intended pickups. Order is rough and priorities shift — `lib/roadmap.ts` is the source of truth.
Linux GUI builds
Ship `Watchfire.app` as a signed AppImage and a `.deb` so Linux users get the same multi-project view macOS already has.
Per-project secrets vault
First-class secrets storage scoped to a project — encrypted at rest, surfaced to agents only inside the worktree, never leaked into transcripts.
Cron-triggered task runs
Schedule recurring tasks natively in `project.yaml` (`schedule: "0 9 * * 1"`) so the daemon fires drafts on its own — no external runner required.
Multi-user daemon mode
Let `watchfired` accept connections from more than one operator with per-user identity, audit log, and project-level ACLs. The piece teams keep asking for.
Marketplace for community task templates
A browsable index of community-contributed task templates, installable with one command — built on the same YAML schema as `/templates`.
JetBrains and Zed integrations
Editor plugins that mirror the VS Code workflow: open a task, jump to its worktree, watch the transcript inline.
How to help.
Watchfire is Apache-2.0 open source. Every item on this page maps to a GitHub label — the easiest entry points are tagged `good-first-issue` and `help-wanted`.
Not sure where to start? Drop into GitHub Discussions — design conversations and rough ideas land there before they become issues.