Zach Lloyd founded Warp, a developer-tools company whose terminal grew into an environment for working with coding agents. He writes about organizing software development around automated workflows and measuring their cost and quality.[1][2][3]
Start with The Factory Stack →
Links
Warp writingFounder · Warp
Career
Before Warp, Lloyd was a principal engineer working on Google Sheets and the Google Docs suite. Warp began as a redesigned terminal and expanded into an agentic development environment paired with Oz, a platform for running and managing cloud coding agents. Warp’s April 2026 announcement made the client source available and described an agent-assisted contribution workflow.[1]
Contributions
A versioned software factory
The Factory Stack turns that argument into a system design. Lloyd proposes storing agent configurations, repositories, triggers, integrations and scorers in code, allowing changes to be versioned and tested. Agent traces and cost records feed replay and benchmarking, while the runtime launches work and tracks failures. The connection matters: teams need both reproducible configurations and records of past work to tell whether a proposed change improves the process.[3]
Opening the Warp client
Lloyd’s open-source announcement describes a contribution model in which people propose and refine changes while agents support implementation workflows. It invites community participation in the client through an AGPL-licensed repository. This combines a concrete source release with a broader proposal for how the company wants to manage development.[4]
Ideas
In a memo to the Warp team, Lloyd argues that engineers should improve the system that triages, plans, implements, reviews and verifies software changes. His proposed measures are the share of work completed automatically and the cost of completing it, including human time and inference. It is an organizational argument about where engineering effort should go as agents do more implementation, rather than evidence that every task can already run autonomously.[2]
Tools, writing & talks
Writing, research & talks
Start here
The Factory Stackwarp.devA technical breakdown of configuration, context, compute, measurement and orchestration for coding agents.
Read this after trying a coding agent on a real repository. It gives a concrete checklist for the infrastructure around an agent, especially what must be recorded before you can compare configurations or replay failures.
Author[3]Warp's Zach Lloyd argues software engineering is becoming factory engineering, walking through concrete factory stages from triage to monitoring and explaining why Warp open-sourced after five years closed.
Catalog workOriginal sourceA team memo arguing for improving the economics and reliability of automated development.
Author[2]- Warp is now open-sourcewarp.dev
Explains the client release and the proposed contribution workflow.
Author[4]