正在加载视频...
视频加载失败
Agents are getting complex to manage: models, skills, automations, permissions, cloud environments, orchestration patterns... So, we built the Terraform for agents: one repository that configures all of your agents as code. The Warp Factories configuration spec defines: - Agents and orchestration: how work gets routed and which models agents... show more
5 条评论

Check out the interactive guide and clone the example templates to learn more about how it works. We'll help you deploy with $10k in usage for qualified companies 🔖

What happens to work already running when a config PR merges? Does each task stay pinned to the old definition, including its child agents? “Reproduce this run” gets interesting if the factory changed halfway through it.

The spec covers the whole factory: routing and models, automations, permissions and environments, plus scorers and benchmarks. That gives teams a place to test configuration changes before rolling them out.

Agents-as-code is the right shape when permissions ship with the factory. Operator twin: every agent config should name the finish artifact and the revoke path — otherwise Terraform just codifies open-ended burn.

managing agents is becoming its own discipline. we went from 'just prompt it' to needing a whole platform in like a year



