Topic
13 facts from 1 episode, in date order. These are what speakers said on the shows, each linked to the moment it was said. They aren't independently verified.
Undated
Zach Lloyd says Warp's cost per pull request was about $80 when it first adopted the factory approach, partly because it used Opus where it was not needed.
“when we first started using the factory approach, it was costing us about eighty per PR because we were using, like, Opus, where we shouldn't have.”
Undated
Zach Lloyd says Warp tuned its factory until cost per pull request fell to roughly $15 to $20.
“we were able to get the cost per PR down to, like, twenty bucks or fifteen bucks, something like that.”
Undated
Zach Lloyd says Warp's pull request throughput rose by about 40 after tuning its factory over the previous month.
“we can measurably improve the throughput of our PRs over the last month. It's gone up by forty.”
Undated
Warp defines each software factory in a YAML file that lists the repositories the agents can use, along with integrations and workflow.
“So for us, we basically have a YAML file which says, okay, these are all the repos that you can be using.”
Undated
In Warp's model, a company has one software factory for each product surface, such as a mobile app or server app.
“You can orchestrate it, you can measure it. You have one factory per product surface,”
Undated
Zach Lloyd says about 60% of Warp's internal factory work starts in Slack.
“the most obvious one is Slack, and, like, we're doing, like, 60% of our work is starting in Slack.”
Undated
Zach Lloyd says Warp uses Namespace as its primary agent sandbox provider for compute.
“We use namespace as our primary one.”
Undated
Zach Lloyd says Warp tests iOS apps by running a Mac virtual machine where an agent operates the simulator.
“the way that we test, like iOS apps, is you're gonna wanna have the ability to run a MacVM and actually, like, have it run the simulator and click around.”
Undated
Zach Lloyd says Warp factories let customers plug in their own agent harness, including Pi or any ACP-compatible harness.
“You can even plug in your own harness, which I think is a pretty big deal. So, you know, you you can orchestrate things like Pi, like I mentioned earlier, and basically any ACP compatible harness.”
Undated
Zach Lloyd says Warp's evals work as an LLM-as-judge setup in which a chosen judge model grades stored agent runs.
“the eval is, again, think of it as LLM as a judge. So you're picking a a judge model.”
Undated
Zach Lloyd says self-improvement agents can open pull requests against Warp's factory definition to improve the factory.
“because you have your whole factory defined as code, and these are coding agents, they can essentially make a pull request against the factory definition to try to improve the factory itself.”
Undated
Zach Lloyd gives an example in which Warp's self-improvement agents found 54 triage failures that a sub-agent could have avoided.
“we have fifty four failure cases of this particular form, where it would've been better if our triager had been able to spawn a sub-agent to do its investigation.”
Undated
Zach Lloyd names Uber and Ramp as examples of companies that are a poor fit for Warp factories because they build their own systems.
“our our kind of not a good fit customer for this, for instance, would be like Uber or Ramp.”
Episodes