Warp introduced Factories, a platform for running fleets of coding agents across the software lifecycle. A factory is defined in code, in a factory.yaml file plus agent files checked into a repository. Work arrives from Slack, Teams, Jira, Linear, GitHub, GitLab, an API or a schedule. A coordinating agent Warp calls the foreman moves each task through triage, spec, implementation, verification, shipping and monitoring. Humans approve at gates that the team chooses, and merges stay with people. Teams can bring their own model or agent, including Claude Code, Codex and Cursor. Runs can execute in Warp's cloud or self-hosted in a customer's own private cloud. Every run is scored, and observer agents open pull requests to change the factory's own config. Access is limited to a closed early access programme, with usage-based pricing per agent run. Warp says most organisations start with roughly a fifth to a third of pull requests fully automated.
What changed
Warp sold a terminal and a standalone command-line coding agent.
What it unlocks
Defining a fleet of coding agents as a checked-in config file that runs from issues, chat or a schedule.
- up to $10,000 free factory usage
- cost per PR $80 to $30
- 20-30% of PRs fully automated
What you need to act on it
- approved request for closed early access
- GitHub or GitLab repositories
- usage-based paid runs
Sources