6 posts tagged “how-to”.
6 min
When a task gets stuck, the answer is almost always in watchfired's log. Here is where it lives, what its lines actually look like, and the five events plus three walkthroughs you'll reach for when an agent won't start, a worktree won't spawn, or an auto-merge never fires.
10 min
Watchfire runs six coding agents on the same task contract. Knowing you can swap them is not the same as knowing which one to reach for. Here is the opinionated version: given the shape of a task, which backend to pick and which to fall back to.
10 min
The acceptance_criteria block is the single field the daemon, the agent, and the human reviewer all read the same way. It is also where most failed Watchfire runs are decided — long before the agent picks a file to edit. Here is how to write criteria that hold.
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.
10 min
Most failed agent runs aren't model failures — they're prompt failures. After a year of running Watchfire on itself, here's what we've learned about writing tasks an agent can actually complete on the first try.