A simple guide to three releases reshaping how AI coding agents are built, deployed, and managed. Written for founders, PMs, designers, and operators — not just engineers.

TL;DR

The unit of work is shifting from prompt to ticket. Engineers are moving from babysitting one chat at a time to managing fleets of agents through boards and pipelines. Three releases in one week made this concrete:

• Warp open-sourced its terminal — but the contributions are written by AI agents, not humans
• Cursor SDK lets you run Cursor's coding agents from anywhere — your CI, your backend, your product
• OpenAI Symphony turns your Linear board into the control panel for autonomous agents

Whoever owns this orchestration layer owns the next dev tools stack.

1. Warp goes open source 🦀

What is Warp?

Warp is a modern terminal app — the black window where developers type commands. Most terminals haven't changed in 40 years. Warp rebuilt it from scratch in Rust with a block-based interface (each command and its output is a clean visual block) and built-in AI (you can type "find files larger than 100MB" in plain English and it generates the right command).

Over time it evolved from a terminal into what they now call an agentic development environment (ADE) — a place to run and manage AI coding agents.

What just happened

On April 29, 2026, Warp open-sourced its client on GitHub under AGPL-3.0, with OpenAI as founding sponsor. Within 24 hours it had 35K+ stars; now over 41K.

The unusual twist

The contribution model is unlike any other open-source project. Instead of humans writing PRs:

1. You file an idea or bug as a GitHub issue
2. A maintainer tags it ready-to-spec (needs design discussion) or ready-to-implement (just needs code)
3. You tag @oss-maintainers
4. An AI agent (Warp's Oz platform) writes the actual code