Automations

Factory's Automations turn its Droid coding agent from an interactive tool into a standing worker. A team writes a plain description of a recurring job, attaches a trigger such as a schedule, a Slack message, a GitHub event or a webhook, and picks which model and machine the run uses. Templates cover ticket-to-PR, fixing code review comments, security audits, CI failure triage and Slack briefs. Choosing the model per automation matters for cost, since routine triage rarely needs the strongest model while a security audit might. The shift also moves the hard questions from prompting to operations: who reviews what the automation produces, what credentials it holds, and how failures get noticed when nobody is watching the session. Teams adopting it should start with read-only or PR-producing jobs before granting merge or deploy rights.