5 posts tagged “wildfire”.
7 min
Wildfire mode runs the task queue, refines drafts, generates new work, and at some point it stops. The signal that stops it is one empty file. Here is why that signal, and not a timer or an iteration cap, is the one we keep.
11 min
Watchfire itself is free, but every task it runs spends real money against an agent backend. Here is a practical, numbers-forward breakdown of what each backend costs, which mode burns the most, and three concrete ways to stay under a monthly budget.
10 min
Wildfire only stays on the rails when the project definition does the bounding. After a year of running Watchfire on its own marketing site, here is what a definition needs to contain so the loop produces work you actually want to merge.
8 min
Six agent modes is one more than you can hold in your head when you are staring at the GUI for the first time. Here is a practical, opinionated decision tree for picking the right one without burning a session.
7 min
Wildfire mode turns a project definition into a self-refining queue of tasks. Here is how the loop is shaped, why each phase exists, and where the safety rails are.