Introducing Scorers: Agents that grade your agents.
Use LLM-as-a-judge to grade past coding agent sessions on:
• Quality
• Efficiency
• Compliance
• Or any custom dimension
Scores feed into performance measurements and automatic self-improvement for software factories
Warp now supports linked billing with Claude Platform.
Link your Claude Platform organization directly to Warp, with no API key to share. Anthropic bills your Claude organization for Claude API usage in Warp, on your existing terms. You can set a monthly spend limit and unlink at any time in the Claude Console.
My definition of a software factory:
A measurable, improvable cloud-based system for scaling coding agents for maximum ROI and productivity across your organization.
I just wrapped up a keynote at @aiDotEngineer Code Summit on how Software Engineering is becoming Factory Engineering.
The core idea is this: using coding agents is an engineering problem, not a prompting problem. Every company should strive to define the system in code, measure what it produces on your codebase, and keep iterating.
Everyone has agents. The hard (and fun) part is engineering the factory around them so they reliably ship better software.
We now support Gemini 4 Carbon across the Warp Factories and the Warp terminal.
This extends to our benchmarking tool for software factories. Try benchmarking Gemini 4 Carbon against your previous agent tasks to see if it's worth it for your team.
I recorded a session on addressing code review bottlenecks! Especially relevant if you're building a software factory. We cover:
- Building your own code review agent
- Verification with e2e computer use checks
- Risk assessment using /merge-risk
youtu.be/uPCH2axUpbc
I started having agents run a /merge-risk assessment skill as a last-mile step to catch risky changes before it makes a PR:
- Strip out unaligned changes to avoid drive-by fixes
- Add error monitoring on new paths for better tracking
- Break up high-impact changes into stacked PRs for simpler review
- Avoid code sensitive paths if it can achieve the same outcome
- And of course, verify work end-to-end with screenshots and recordings
I was talking to an engineer the other day about this question:
How do you make a codebase easy-to-navigate by both agents and humans, when everything from the hello world is agent-built?
The answer is system architecture. Agents (like humans) copy bad patterns like a virus. It's a ball of clay that needs constant reshaping.
You can write down best practices into your factory's skills, yes, but keeping the codebase itself on the right path is the real goal.
It's too expensive to have an agent review the universe constantly, spitting out architecture change PRs no one wants to look at. But, say, a weekly automation with a frontier reasoning model (Fable 5.2 is a good one to try) that pulls out one improvement to your system architecture is a start. I like @steveruizok's prompt to "look for implicit state machines."
Will experiment with a factory automation like this and see how it goes.
Get code review agents off of GitHub! I don't want to see the noise in my PR description.
Agents should run through their own internal code review process before a PR ever reaches a teammate.
Lots of discussion about what a "software factory" is.
Also useful to call out what a software factory is not:
1/ A loose collection of automations around cloud agents
2/ A team of "AI Engineers" that developers manage interactively
3/ A set of skills and MCPs that individual engineers all adopt across a team
4/ A personal agent swarm
These are all useful things, but they aren't the right primitives for engineering scalable agent systems across an organization.
The right primitives allow you to define all your agentic workflows in code, run them entirely in the cloud, and, crucially, measure, test and improve those workflows over time to maximize agent productivity while minimizing cost.
If you start thinking from first principles "what is the system we should build as a company to get the most out of coding agents" you will end up with something like this.
I'll be live in just a moment to talk code review bottlenecks! We'll break down:
- Code review loops and how to benchmark their usefulness
- End-to-end verification skills
- A /merge-risk skill to mitigate risk ahead of PR
RSVP to join: warp.dev/events/solving-the-…
Fable 5.2 is a great systems thinker.
Try using it to find implicit state machines in your apps to make your codebase easier for agents to navigate.
Live in Warp Factories + the Warp terminal