Hello from Watchfire
Welcome to the Watchfire blog. We are building a remote control for AI coding agents: a daemon that takes clear specs, scopes them into tasks, and runs each one inside a sandboxed git worktree so the work stays reviewable. The full story, the architecture, and the install guide live in the docs, and the source is on GitHub.
This post ships alongside v7.1.0 Forge. Forge focuses on the rough edges of long sessions: the chat input no longer drops keystrokes during heavy agent output, mode switches surface a quick toast so you can confirm where you landed, and the prompt is visible the whole way through a task instead of disappearing once execution starts. Small fixes, but they make Wildfire mode feel a lot less like an experiment.
What to expect from this blog: short release notes when a new version cuts, longer pieces when we change something interesting under the hood (sandbox policy, the gRPC schema, how worktrees get reused), and the occasional behind-the-scenes look at the agent loop. No newsletter sign-up yet, no comments. If you want to follow along, the post list lives at /blog and there is an RSS feed at /blog/feed.xml.
More posts
Firestorm 9.3: cleaning up after ourselves
4 min
Every non-Claude agent session materializes a scratch home directory under ~/.watchfire — and until now, nothing ever deleted it. One directory per project × mode × task, forever, surviving even project deletion. 9.3 fixes the leak twice: sessions clean up after themselves, and deleting a project sweeps whatever its sessions left behind. The interesting part is deciding what not to delete.
Firestorm 9.2: charts that state their numbers
5 min
9.2 is a legibility release for the dashboard. The list view hid task counts exactly when an agent was working, a leaderboard cap silently ate the 'shipped' chip for any project ranked sixth or lower, and both Fleet insights charts rendered shape without a single number on them. Here's what was wrong, why each bug is a little embarrassing in an instructive way, and what changed.
Firestorm 9.0: Watchfire becomes a factory agents can drive
7 min
For nine majors Watchfire drove coding agents. Firestorm inverts that: watchfire mcp serve exposes the whole orchestrator to any MCP-capable client as an 18-tool factory, so an outer agent plans and reviews while Watchfire manufactures the code in sandboxed, worktree-isolated runs. It is the fourth thin client, it holds no orchestration logic of its own, and it is local-only by construction.