Warp

With software factories, our team has flipped from mainly terminal sessions to inviting agents into our workspaces: - Slack / MS Teams - GitHub PRs - Linear / JIRA / Azure DevOps The reason? Human attention. Here's Warp engineer Lili showing how we hop between tools today:

Three months since adopting software factories, we’re at 40% more PRs merged and 67% lower cost per PR. We got there by measuring agent quality, benchmarking models, and using self-improvement loops to make our factory better. Here's how you can do this too in Warp Factories:

3. Have agents suggest roadmap items from customer feedback. For example, you can use @GrainHQ to record transcripts on customer discovery calls, and have coding agents pull out insights. Here, an agent goes through prior customer interviews with a scheduled automation and looks for commonalities in where customers get stuck. From there, you can fully close the loop by connecting your taskboard via MCP to drive the next agent task. More on integrations: docs.warp.dev/factories/conn… 🔖

1. Have agents fix their own bugs. @sentry alerts are a good starter: When errors are thrown from full stack systems, have an alert tag in an agent to investigate. A simple version of this is having an agent read your codebase and report findings on that alert to Slack. A better version, though, is to give an agent the tools it needs to fix the issue and send the PR. This means a cloud environment, computer use verification, and adversarial code review. Implementation-wise, this will be a webhook that can trigger an agent on an always-on computer. In Warp Factories, we configure this using an automations file, which binds a trigger referencing a webhook and sets an agent prompt and model to go address that alert. To set this up with webhooks: docs.warp.dev/factories/webh… 🔖

You can now use ChatGPT Go subscriptions in Warp for any terminal question or coding task 👏

Shout out to Hotel Bardo for their hospitality! If you want to join us next time, we're hiring: warp.dev/careers

The Warp team came together in Savannah for our fall off-site! Our agenda: - Engineer the software factory - Let it run - Go kayaking 🛟

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 use - Automations: the events and schedules that kick off work - Access and environments: repositories, secrets, MCP servers, and runners - Measurement: scorers and benchmarks for understanding and improving performance Because it’s all code, both engineers and agents can propose changes to the factory itself. That makes it possible to test new configurations, benchmark them, and even have your factory propose improvements as PRs.

GPT 6.1 Sol is now in Warp, ready to use with your Codex / ChatGPT subscription

You can now sign in with ChatGPT from the Warp Terminal and the Warp Agent CLI! Sign in to Warp with your ChatGPT account and use your subscription’s included Work and Codex usage for your agent conversations.