Warp

Warp is a Rust-based agentic development environment, born out of the terminal. The client codebase opened in April 2026 with OpenAI as founding sponsor, AGPL-3.0 for the application code and MIT for the warpui and warpui_core UI framework crates. It crossed 54,000 GitHub stars in the weeks after the open-source release. Almost all of it is Rust, with a small amount of Objective-C, C, and WGSL shader code on the rendering edges.

The defining design choice is that this repository is built for AI agents to read and contribute to. The .agents/skills/ directory ships twenty SKILL.md files that any compatible agent harness can pick up. The specs/ directory holds 142 product-and-tech spec pairs (mostly under specs/GH<issue>/ or specs/APP-<ticket>/) that anchor implementation work. WARP.md at the root is the engineering guide. .mcp.json wires up the GitHub MCP server. .claude/skills is a symlink to .agents/skills so Claude Code reads the same content. Agent contributions go through Oz, Warp's automated triage and PR-review system that sits between issue and human reviewer.

Architecturally, Warp is a 60+ crate Cargo workspace. app/ is the main binary; crates/warpui and crates/warpui_core are a custom UI framework with an Entity-Component-Handle pattern, wgpu-backed text rendering, and a font-kit rasterizer. crates/warp_terminal holds the terminal grid model (parts adapted from Alacritty under a separate license). crates/ipc is a typed request/response IPC built on Unix domain sockets and Windows named pipes. The Tokio multi-threaded runtime lives behind a Background executor in warpui_core.

The repository root is the Cargo workspace. Cargo.toml declares members = ["crates/*", "app"] with a smaller default-members list so the everyday cargo build skips integration-only crates. app/ contains the binary entry points (app/src/bin/oss.rs, local.rs, stable.rs, dev.rs) which all wrap the same warp::run() function in app/src/lib.rs. The lib.rs file is around 2,900 lines and orchestrates the whole app: AI, auth, terminal, drive, settings, workspace.

The async story is unusual for a Tokio app. warpui_core::async::executor::Background wraps a tokio::runtime::Runtime built with new_multi_thread() and worker threads sized to num_cpus::get(). The same crate also exposes a Foreground executor that runs on the main UI thread for view updates. The IPC server in crates/ipc spawns four background tasks per client connection (listen, accept, inbound, outbound) all on this shared runtime.

Text rendering is GPU-accelerated. crates/warpui/src/rendering/wgpu/renderer.rs sets up three pipelines: rect, glyph, image. The glyph pipeline reads crates/warpui/src/rendering/wgpu/shaders/glyph_shader.wgsl, which implements brightness-scaled contrast enhancement adapted from Microsoft Terminal's DirectWrite shader to compensate for sRGB blending making light-on-dark text appear too thin. Glyph rasterization itself is on the CPU via font_kit, with results uploaded to a texture atlas (crates/warpui/src/rendering/atlas/). Subpixel positioning, anti-aliasing strategy, and thin-stroke compensation are configurable per glyph.

Shell integration is escape-sequence based. app/assets/bundled/bootstrap/ contains zsh, bash, fish, and PowerShell init scripts that the spawned shell evals on startup. They define a private OSC namespace (OSC 9277 for command output framing, OSC 9278 for general events, OSC 9279 for grid reset) and a DCS-based JSON protocol so structured shell hooks reach the client without polluting visible output.

The agent-facing surface is concentrated in three places. .agents/skills/ is twenty kebab-case directories, each with a SKILL.md whose YAML frontmatter (name, description) lets a harness route requests. specs/ holds product/tech spec pairs that ground implementation work in current code with line-numbered references. WARP.md documents commands, architecture, and coding conventions for any agent that lands here.