Warp open-sources its client codebase under a split MIT (UI crates) + AGPL v3 (everything else) license, with OpenAI as founding sponsor.
Key Takeaways
The warpui_core and warpui Rust crates are MIT-licensed; the rest of the repo is AGPL v3, a meaningful distinction for forks and embeds.
OpenAI is the founding sponsor; agentic management workflows run on GPT models by default, though Claude Code, Codex, and Gemini CLI are all supported as bring-your-own agents.
Warp now positions itself as an “agentic development environment” rather than a terminal, with a built-in coding agent alongside the traditional shell.
The repo uses a structured issue-to-PR contribution flow with ready-to-spec and ready-to-implement labels; @oss-maintainers is the escalation path.
Build toolchain is Rust-heavy; ./script/bootstrap && ./script/run gets you a local build, with script/presubmit covering fmt, Clippy, and tests.
Hacker News Comment Review
Commenters broadly feel the product has drifted from terminal to coding agent, with several noting the UI has become overwhelming and that they’ve migrated to Ghostty or stayed on iTerm2.
Skepticism runs high on the OpenAI sponsorship angle and the repo’s rapid star count, with at least one commenter questioning whether the star velocity was organic.
A persistent complaint surfaces about AI being forced into the shell workflow uninvited, with users describing accidental AI invocations and difficulty escaping back to a plain command line.
Notable Comments
@shimman: Alleges Warp was built on an Alacritty fork that earned a $50M round while contributing nothing back upstream, and sees the OpenAI partnership as consistent with that pattern.
@morgango: Paying user who enjoys Warp but reports accidental AI mode triggers: “My ESC key is wearing out.”
