Warp

The Warp team is changing our mindset from building our product to building a cloud software factory that builds our product for us. I firmly believe this is how software is going to be built and that engineers need to adjust from directly shipping product features, to building a factory that ships the features for them.

Introducing Agent Memory: shared context that helps agents remember what works across conversations. It's cross-harness (Claude Code, Codex, Warp Agent), portable (turnkey hosting or self-hosted), and shared across your team. Now in research preview. Join the waitlist here: https://lnkd.in/eK3DVmjq

Introducing multi-agent orchestration in Oz, with support for Claude Code, Codex, and the Warp Agent. Use /orchestrate to delegate complex tasks across a team of agents, locally or in the cloud. Multi-harness orchestration is available to all users while in beta.

You can now orchestrate subagents running in Claude Code, Codex, or the Warp Agent. Let the agent create a delegation plan, and watch subagents coordinate with message passing. Each agent gets its own worktree for isolation. Here's how it works with eng Matthew Albright: Claude Code and Codex subagents are now in beta. Try it out in the latest version of Warp by running /orchestrate with your next Warp Agent prompt!

You can now plan out a task locally, and kick off implementation to a team of agents in the cloud. Get usolated cloud environments for each agent, and message passing to coordinate and ship a PR. Plus, it's multi-harness, supporting Warp, Claude Code, and Codex. Here's eng Matthew Albright to show how it works:

Major launch today! With Oz, engineering teams can now orchestrate any cloud agent at scale including Claude Code, Codex, Warp Agent, and whatever comes next.