# Warp Goes Open-Source, And Oz Becomes Your First-Line Code Reviewer
**作者**: AlphaSignal AI
**日期**: 2026-04-28T15:48:24.000Z
**来源**: [https://x.com/AlphaSignalAI/status/2049534207412871477](https://x.com/AlphaSignalAI/status/2049534207412871477)
---
+13k stars in 24 hours. AGPL + MIT. OpenAI sponsoring. Oz reviewing.
@warpdotdev opened its agentic dev environment to the public on April 28, 2026 under AGPL v3, with the warpui framework crates released under MIT.
> **Warp@warpdotdev**: [原文链接](https://x.com/warpdotdev/status/2049153766977421444)
>
> Warp is now open-source.
>
> 
OpenAI is the founding sponsor of the new repository after releasing similar tools earlier. Agent workflows are powered by GPT models, and Engineering Lead Thibault Sottiaux is on record supporting the experiment of "how AI can help maintainers and contributors collaborate more effectively at scale."
Oz is Warp's agent platform. It auto-triages every incoming issue, conducts the first-pass review on every PR, and can be dispatched to implement issues on free credits.
> **Zach Lloyd@zachlloydtweets**: [原文链接](https://x.com/zachlloydtweets/status/2044870634711490938)
>
> We launched Oz (http://oz.dev) in February, and enterprise demand has accelerated quickly since.
> Warp’s enterprise ARR is now up 500%+ since Q4 as more companies look to move coding agents to the cloud, without giving up flexibility, governance, or control over their
>
> 
The practical effect: developers can now use the binary, fork a 63-crate Rust workspace, or ship a PR where the first reviewer is an AI agent and the implementation can also be done by an AI agent at zero cost.
## Repo Snapshot
## Why an AI is reviewing your PR
The license change is the headline. The contribution model is the story.
For five years, Warp's client was closed-source. Zach Lloyd flagged the long-term plan to open the code in his original 2022 Show HN. The April 28 release fulfills that commitment, and pairs it with a contribution flow that no comparable open-source project ships with.
Bug fixes are implicitly ready-to-implement once triaged. Feature requests sit behind a ready-to-spec gate, which means a contributor opens a spec PR with product.md (the testable behavior invariants) and tech.md (the implementation plan with file references) under specs/GH<issue#>/ before any code is written. Once the specs are approved, a code PR opens. Oz auto-reviews. After Oz approves, a Warp subject-matter expert is automatically requested.
Contributors can comment /oz-review up to three times per PR to re-request review. After that, the path is to mention @oss-maintainers to escalate to the team.
The most differentiated mechanic: contributors who do not want to write the code themselves can mention @oss-maintainers on a ready issue to dispatch an Oz cloud agent to implement it. Approved requests run on free Oz credits. There is no setup, no billing, no local agent harness.
The thesis Warp is testing is direct. Humans spec and verify, agents implement and review. Open-sourcing accelerates that test by putting the spec, the implementation, and the review surface in public.
## How Oz Sits Inside Warp's Architecture
The Warp client is a Rust workspace with 63 crates under crates/ plus the app/ binary, verified from Cargo.toml (members = ["crates/*", "app"]). The UI is a custom GPU-accelerated framework called WarpUI, which uses an Entity-Component-Handle pattern (Flutter-inspired) where a global App object owns all entities and views hold ViewHandle references rather than direct ownership. The text editor is a CRDT, which makes collaborative editing a primitive rather than a bolt-on. Native integration ships for Claude Code, Codex, Gemini CLI, and OpenCode as guest agents, with Warp's "agent toolbelt" providing rich input, code review, and notification surfaces.
The agentic contribution loop runs in four stages.
Triage. Oz auto-applies labels (ready-to-spec, ready-to-implement, needs-mocks, plus informational area:* and repro:* tags). Bugs land in ready-to-implement directly. Features go to ready-to-spec until a design is settled.
Spec. Feature contributors commit specs/GH<issue#>/product.md and specs/GH<issue#>/tech.md. The repo ships agent-readable scaffolds at .agents/skills/ for Claude Code, Codex, Gemini CLI, and Warp's built-in agent. Existing spec PRs at specs/GH408/, specs/GH1063/, and specs/GH1066/ are referenced as canonical examples.
Review. When a PR opens against a ready issue, Oz is auto-assigned. After Oz approves, a Warp SME is automatically requested. Contributors do not assign reviewers manually.
Implement. Optional. Mention @oss-maintainers on the issue to have an Oz cloud agent implement it. Free credits. No personal account required.
The architectural takeaway is that the contribution loop is also an agent loop. The same agent platform that powers Warp's user-facing features is the platform reviewing the code that improves them.
## Evidence
The initial public commit on warpdotdev/Warp is dated April 28, 2026, recorded in the GitHub commit history. Within 24 hours, the repository accumulated 38,779 stars, 2,089 forks, and 3,157 open issues, per the GitHub API as of April 29, 2026.
The license split is documented in README.md lines 36 to 38. The warpui_core and warpui crates are MIT-licensed. The rest of the codebase, including the agent loop, terminal emulation, AI integration, drive sync, and IPC, is AGPL-3.0.
Oz cloud agent execution for OSS contributions is documented in CONTRIBUTING.md line 115. Approved requests run for free on complimentary Oz credits, with no personal Oz account or compute cost required.
The 2022 Show HN thread carries the original public commitment from Zach Lloyd to open-source the Rust UI framework first and "potentially all of our client" later. The April 2026 release closes that five-year roadmap item.
Warp shipped wider open-source model support alongside the license change, including Kimi, MiniMax, Qwen, and a new "auto (open)" router, a programmatic settings file for portability, and a public roadmap on GitHub. A live triage dashboard at build.warp.dev surfaces issue status and Oz activity.
## How to Get Started
Three paths, in order of effort.
Path 1: Use it.
```
brew install --cask warp # macOS
winget install Warp.Warp # Windows
# Linux: .deb / .rpm / .pacman / AppImage from app.warp.dev/get_warp
```
The pre-built binary still requires login. AI traffic still proxies through Warp servers in default mode. BYO-key is supported for OpenAI, Anthropic, Google, xAI, OpenRouter, and AWS Bedrock.
Path 2: Build from source.
```
git clone https://github.com/warpdotdev/Warp.git
cd Warp
./script/bootstrap # platform-specific setup
./script/run # build and run Warp
./script/presubmit # fmt, clippy, tests
```
cargo run works directly. The full engineering guide is in WARP.md. Platform dependencies include the Rust toolchain, Metal on macOS, and standard GUI development libraries on Linux.
Path 3: Contribute through Oz.
```
1. File an issue (or use /feedback inside Warp to attach logs automatically).
2. Wait for ready-to-implement (bugs) or ready-to-spec (features).
3. For features: commit specs/GH<issue#>/product.md + tech.md, open a spec PR.
4. After specs are approved, open a code PR.
5. Oz auto-reviews. After Oz approves, a Warp SME is auto-requested.
6. Comment /oz-review up to 3 times to request re-review.
7. To escalate or to request an Oz cloud agent implementation, mention @oss-maintainers.
```
The third path is the one that did not exist 48 hours ago. A developer with a long-pending Warp bug can now file the issue, mention @oss-maintainers, and have an Oz cloud agent ship the fix on free credits.
## Current Limitations
AGPL is copyleft. Modifications hosted as a network service must be released under AGPL. Only warpui_core and warpui are MIT and reusable in proprietary work without that obligation. Teams considering an internal Warp fork for product use should run AGPL through legal first.
AI traffic still routes through Warp's proxy. Default mode and BYO-key both proxy through Warp servers. Local-only or air-gapped operation is not supported out-of-the-box. The open client does not change the data path.
Login is still required for the pre-built binary. The 2022 Hacker News controversy about mandatory login was not addressed by the open-source release. Building from source may bypass it but is not the documented path.
Spec-PR overhead is real. Even small UX feature requests need product.md and tech.md before any code is accepted. Bug fixes skip both steps. Contributors used to "draft a PR, discuss inline" will need to adjust.
3,157 open issues at launch. The agent-mediated review model is unproven at this scale. Throughput depends on Oz review quality and Warp SME bandwidth. The next 90 days will measure whether the model holds.
So the best recommendation is to clone the repo today, file the bug that has annoyed you for two years, and let Oz handle the rest.
## AlphaSignal Take
Warp's open-source release is Production Ready as a daily-driver terminal and Worth Watching as a contribution model.
The release does what the announcement claims. The code is on GitHub, the license files are in the repo root, Oz is reviewing PRs in public, and the engineering guide in WARP.md documents the build path including platform-specific dependencies.
Maintenance health is strong on the surface. 38,779 stars in 24 hours and Oz auto-triage are positive signals. 3,157 unresolved issues and the spec-PR overhead are friction the next 90 days will measure.
What would change the verdict on the contribution side from Worth Watching to Production Ready: Oz demonstrating it can review a non-trivial spec PR end-to-end without a Warp SME catching a missed nuance. That is the experiment to watch on build.warp.dev. If it holds, agent-first contribution becomes a pattern in other repos copy. If it does not, Warp ships a great terminal and the agent-review story stays a marketing line.
## Who Benefits and Who Doesn't
Developers shipping in the terminal who want a faster agent loop, Rust engineers studying a production GPU UI framework alongside a working multi-LLM agent codebase, OSS contributors curious about agent-mediated review, teams evaluating Claude Code or Codex or Gemini CLI as guest agents inside a host environment, and anyone with a long-pending Warp bug all benefit immediately.
Teams with strict on-prem or air-gapped requirements should hold, since AI traffic still proxies through Warp servers. Proprietary-fork builders who need permissive licensing on the agent loop should also skip, since only warpui is MIT.
Contributors who prefer human-first code review over AI-first will find the spec-PR and Oz auto-assignment workflow uncomfortable. Organizations that need an account-free terminal binary today will not get it from this release.
## Practitioner Implication
OSS-curious developers can now ship code into the terminal they use every day, with Oz reviewing the PR and an Oz cloud agent implementing the issue if asked, now that Warp's five-year closed-source period is over.
## Links
- warpdotdev/Warp on GitHub (repo, ~2 min snapshot)
- Warp is now open-source (announcement, ~6 min read)
- CONTRIBUTING.md (contribution flow, ~8 min read)
- WARP.md engineering guide (build + architecture, ~12 min read)
- docs.warp.dev (full documentation)
Follow @AlphaSignalAI for more content like this.
Subscribe at AlphaSignal.ai for daily AI signals. Read by 280,000+ developers.
## Questions?
Q: Is Warp really open-source now? A: Yes. The client codebase was published to github.com/warpdotdev/Warp on April 28, 2026 under AGPL v3, with the warpui_core and warpui UI framework crates under MIT. The 2022 commitment to open-source the client is now fulfilled.
Q: Can I use Warp's code in a proprietary product? A: Only the MIT-licensed warpui_core and warpui crates can be used without copyleft obligations. The rest of the codebase is AGPL v3, which requires source release if you distribute or host modifications as a network service.
Q: How do I build Warp from source? A: Clone the repo, then run ./script/bootstrap, ./script/run, and ./script/presubmit. cargo run works directly. The full engineering guide is in WARP.md.
Q: What is Oz and how does it work for contributors? A: Oz is Warp's cloud agent orchestration platform. It auto-triages incoming issues and conducts the first-pass review on every PR. Contributors can also dispatch an Oz cloud agent to implement an issue by mentioning @oss-maintainers, and these requests run on free credits.
Q: Does Warp still need a login or send my data through their servers? A: Pre-built binaries still require login, and AI traffic routes through Warp's proxy by default even with BYO-key. Building from source may bypass login but is not officially documented as a no-login path. Local-only or air-gapped operation is not supported.
## 相关链接
- [AlphaSignal AI](https://x.com/AlphaSignalAI)
- [@AlphaSignalAI](https://x.com/AlphaSignalAI)
- [1.6K](https://x.com/AlphaSignalAI/status/2049534207412871477/analytics)
- [@warpdotdev](https://x.com/@warpdotdev)
- [Apr 28](https://x.com/warpdotdev/status/2049153766977421444)
- [2.5M](https://x.com/warpdotdev/status/2049153766977421444/analytics)
- [releasing similar tools earlier](https://x.com/AlphaSignalAI/status/2049172133578703181?s=20)
- [Apr 17](https://x.com/zachlloydtweets/status/2044870634711490938)
- [16K](https://x.com/zachlloydtweets/status/2044870634711490938/analytics)
- [@oss](https://x.com/@oss)
- [@oss](https://x.com/@oss)
- [@oss](https://x.com/@oss)
- [The 2022 Show HN thread](https://news.ycombinator.com/item?id=30921231)
- [build.warp.dev](https://build.warp.dev/)
- [@oss](https://x.com/@oss)
- [build.warp.dev](https://build.warp.dev/)
- [warpdotdev/Warp on GitHub](https://github.com/warpdotdev/Warp)
- [Warp is now open-source](https://www.warp.dev/blog/warp-is-now-open-source)
- [CONTRIBUTING.md](https://github.com/warpdotdev/Warp/blob/master/CONTRIBUTING.md)
- [WARP.md engineering guide](https://github.com/warpdotdev/Warp/blob/master/WARP.md)
- [docs.warp.dev](https://docs.warp.dev/)
- [@AlphaSignalAI](https://x.com/@AlphaSignalAI)
- [AlphaSignal.ai](https://alphasignal.ai/)
- [github.com/warpdotdev/Warp](https://github.com/warpdotdev/Warp)
- [@oss](https://x.com/@oss)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [1:00 AM · Apr 30, 2026](https://x.com/AlphaSignalAI/status/2049534207412871477)
- [1,614 Views](https://x.com/AlphaSignalAI/status/2049534207412871477/analytics)
---
*导出时间: 2026/4/30 11:30:36*
---
## 中文翻译
# Warp 开源，Oz 成为你的代码初审员
**作者**: AlphaSignal AI
**日期**: 2026-04-28T15:48:24.000Z
**来源**: [https://x.com/AlphaSignalAI/status/2049534207412871477](https://x.com/AlphaSignalAI/status/2049534207412871477)
---
24 小时内获得 +13k 星标。AGPL + MIT 协议。OpenAI 赞助。Oz 进行审查。
@warpdotdev 于 2026 年 4 月 28 日在 AGPL v3 协议下向公众开放了其代理开发环境，同时 warpui 框架的相关 crates 以 MIT 协议发布。
> **Warp@warpdotdev**: [原文链接](https://x.com/warpdotdev/status/2049153766977421444)
>
> Warp 现已开源。
>
> 
OpenAI 是该新仓库的创始赞助方，此前曾发布过类似工具。代理工作流由 GPT 模型驱动，工程负责人 Thibault Sottiaux 曾公开支持这项实验，旨在探索“AI 如何帮助维护者和贡献者在大规模协作中更有效地合作”。
Oz 是 Warp 的代理平台。它会对每个传入的 issue 进行自动分类，对每个 PR 进行首轮审查，并可以被派遣使用免费额度来实现 issue 的修复。
> **Zach Lloyd@zachlloydtweets**: [原文链接](https://x.com/zachlloydtweets/status/2044870634711490938)
>
> 我们在二月推出了 Oz (http://oz.dev)，此后企业需求迅速增长。
> 随着越来越多的公司寻求将编码代理迁移到云端，且不牺牲灵活性、治理或控制权，Warp 的企业 ARR 自第四季度以来增长了 500% 以上。
>
> 
实际效果是：开发者现在可以使用二进制文件，复刻这个包含 63 个 crates 的 Rust 工作区，或者提交 PR，而第一个审查者是 AI 代理，实现工作也可以由 AI 代理在零成本下完成。
## 仓库快照
## 为什么 AI 在审查你的 PR
许可证变更是头条新闻，贡献模式才是核心故事。
五年来，Warp 的客户端一直是闭源的。Zach Lloyd 在他 2022 年最初的 Show HN 帖子中就标记了开源代码的长期计划。4 月 28 日的发布兑现了这一承诺，并搭配了任何同类开源项目都未曾提供的贡献流程。
Bug 修复在被分类后隐式地处于“准备实现”状态。功能请求则处于“准备规范”的门槛之后，这意味着贡献者在编写任何代码之前，需要打开一个规范 PR，在 specs/GH<issue#>/ 目录下提交 product.md（可测试的行为不变量）和 tech.md（包含文件引用的实现计划）。一旦规范获得批准，代码 PR 就会开启。Oz 会自动进行审查。在 Oz 批准后，系统会自动请求 Warp 的领域专家（SME）介入。
贡献者可以在每个 PR 下最多评论三次 /oz-review 以请求重新审查。之后，途径是提及 @oss-maintainers 来升级处理给团队。
最独特的机制是：不想自己编写代码的贡献者，可以在一个处于 ready 状态的 issue 下提及 @oss-maintainers，以派遣一个 Oz 云代理来实现它。批准的请求在免费的 Oz 额度上运行。无需设置，无需计费，无需本地代理框架。
Warp 正在测试的论点很直接：人类进行规范和验证，代理进行实现和审查。开源加速了这一测试，因为它将规范、实现和审查层都公开化了。
## Oz 如何融入 Warp 的架构
Warp 客户端是一个包含 63 个 crates 的 Rust 工作区，位于 crates/ 下，加上 app/ 二进制文件，这已从 Cargo.toml 得到验证（members = ["crates/*", "app"]）。UI 是一个称为 WarpUI 的自定义 GPU 加速框架，它使用实体-组件-句柄模式（受 Flutter 启发），其中全局 App 对象拥有所有实体，视图持有 ViewHandle 引用而非直接所有权。文本编辑器是一个 CRDT（无冲突复制数据类型），这使得协作编辑成为原语而非附加功能。原生集成支持 Claude Code、Codex、Gemini CLI 和 OpenCode 作为访客代理，Warp 的“代理工具带”提供丰富的输入、代码审查和通知界面。
代理贡献循环分为四个阶段。
**分类**。Oz 自动应用标签（ready-to-spec, ready-to-implement, needs-mocks，以及信息性的 area:* 和 repro:* 标签）。Bug 直接进入 ready-to-implement。功能请求进入 ready-to-spec，直到设计确定。
**规范**。功能贡献者提交 specs/GH<issue#>/product.md 和 specs/GH<issue#>/tech.md。仓库在 .agents/skills/ 下提供了代理可读的脚手架，适用于 Claude Code、Codex、Gemini CLI 和 Warp 内置代理。现有的规范 PR，如 specs/GH408/、specs/GH1063/ 和 specs/GH1066/，被引用为规范示例。
**审查**。当针对一个就绪 issue 打开 PR 时，Oz 会被自动分配。Oz 批准后，会自动请求 Warp SME。贡献者无需手动分配审查者。
**实现**。可选。在 issue 中提及 @oss-maintainers 以让 Oz 云代理实现它。免费额度。无需个人账户。
架构上的结论是：贡献循环也是一个代理循环。为 Warp 面向用户的功能提供支持的同一个代理平台，也是审查改进这些功能的代码的平台。
## 证据
warpdotdev/Warp 上的初始公开提交日期为 2026 年 4 月 28 日，记录在 GitHub 提交历史中。根据 GitHub API 截至 2026 年 4 月 29 日的数据，该仓库在 24 小时内积累了 38,779 个星标、2,089 个复刻和 3,157 个开放 issue。
许可证的分离记录在 README.md 的第 36 到 38 行。warpui_core 和 warpui crates 采用 MIT 许可证。代码库的其余部分，包括代理循环、终端模拟、AI 集成、驱动同步和 IPC，均采用 AGPL-3.0。
CONTRIBUTING.md 第 115 行记录了用于开源贡献的 Oz 云代理执行。批准的请求在免费的 Oz 额度上运行，无需个人 Oz 账户或计算成本。
2022 年的 Show HN 主题承载了 Zach Lloyd 最初公开承诺先开源 Rust UI 框架，随后“可能开源我们所有的客户端”。2026 年 4 月的发布结束了这一为期五年的路线图项目。
Warp 在许可证变更的同时发布了更广泛的开源模型支持，包括 Kimi、MiniMax、Qwen 和一个新的“auto (open)”路由器，一个用于可移植性的程序化设置文件，以及 GitHub 上的公开路线图。位于 build.warp.dev 的实时分类仪表板显示了 issue 状态和 Oz 活动。
## 如何开始
三种路径，按工作量排序。
**路径 1：使用它。**
```
brew install --cask warp # macOS
winget install Warp.Warp # Windows
# Linux: .deb / .rpm / .pacman / AppImage from app.warp.dev/get_warp
```
预构建的二进制文件仍需登录。在默认模式下，AI 流量仍通过 Warp 服务器代理。支持为 OpenAI、Anthropic、Google、xAI、OpenRouter 和 AWS Bedrock 自带密钥（BYO-key）。
**路径 2：从源码构建。**
```
git clone https://github.com/warpdotdev/Warp.git
cd Warp
./script/bootstrap # 特定于平台的设置
./script/run # 构建并运行 Warp
./script/presubmit # fmt, clippy, tests
```
cargo run 可以直接运行。完整的工程指南在 WARP.md 中。平台依赖包括 Rust 工具链、macOS 上的 Metal 以及 Linux 上的标准 GUI 开发库。
**路径 3：通过 Oz 贡献。**
```
1. 提交 issue（或在 Warp 内使用 /feedback 自动附加日志）。
2. 等待 ready-to-implement（Bug）或 ready-to-spec（功能）。
3. 对于功能：提交 specs/GH<issue#>/product.md + tech.md，打开规范 PR。
4. 规范批准后，打开代码 PR。
5. Oz 自动审查。Oz 批准后，自动请求 Warp SME。
6. 评论 /oz-review 最多 3 次以请求重新审查。
7. 要升级处理或请求 Oz 云代理实现，提及 @oss-maintainers。
```
第三条路径在 48 小时前还不存在。拥有长期未决 Warp Bug 的开发者现在可以提交 issue，提及 @oss-maintainers，然后让 Oz 云代理在免费额度上发布修复。
## 当前限制
AGPL 是 Copyleft 许可证。作为网络服务托管的修改版本必须以 AGPL 发布。只有 warpui_core 和 warpui 是 MIT 许可，可在专有工作中无义务地复用。考虑将 Warp 内部 Fork 用于产品用途的团队应先让法务审查 AGPL。
AI 流量仍通过 Warp 的代理路由。默认模式和 BYO-key 模式都通过 Warp 服务器代理。不支持开箱即用的纯本地或隔离网络操作。开放客户端不会改变数据路径。
预构建二进制文件仍需登录。2022 年关于强制登录的 Hacker News 争议并未通过开源发布得到解决。从源码构建可能会绕过它，但这并非文档化的路径。
规范 PR 的开销是真实的。即使是小的 UX 功能请求，也需要在代码被接受前提供 product.md 和 tech.md。Bug 修复可跳过这两个步骤。习惯于“起草 PR，内联讨论”的贡献者将需要调整。
发布时有 3,157 个开放 issue。这种代理介导的审查模式在此规模下尚未得到验证。吞吐量取决于 Oz 的审查质量和 Warp SME 的带宽。未来 90 天将检验该模式是否可行。
因此，最好的建议是今天克隆仓库，提交那个困扰你两年的 Bug，让 Oz 处理其余的事情。
## AlphaSignal 观点
Warp 的开源发布作为日常驱动终端是**生产就绪**的，作为贡献模式是**值得关注**的。
发布做到了公告所声称的内容。代码在 GitHub 上，许可证文件在仓库根目录，Oz 正在公开审查 PR，WARP.md 中的工程指南记录了构建路径，包括特定于平台的依赖项。
维护健康度表面上看起来很强。24 小时内获得 38,779 个星标和 Oz 自动分类是积极信号。3,157 个未解决的 issue 和规范 PR 的开销是摩擦点，未来 90 天将对此进行衡量。
什么能将贡献方面的结论从“值得关注”变为“生产就绪”：Oz 证明它可以端到端审查一个非平凡的规范 PR，而无需 Warp SME 发现遗漏的细微差别。这是在 build.warp.dev 上值得关注的实验。如果成功，以代理优先的贡献将成为其他仓库复制的模式。如果不成功，Warp 仍然是一个很棒的终端，而代理审查的故事将只是一句营销口号。
## 谁受益，谁不受益
在终端工作的开发者，他们想要更快的代理循环；研究生产级 GPU UI 框架以及工作多 LLM 代理代码库的 Rust 工程师；对代理介导审查感到好奇的开源贡献者；在宿主环境中评估 Claude Code、Codex 或 Gemini CLI 作为访客代理的团队；以及任何拥有长期未决 Warp Bug 的人，都能立即受益。
有严格本地部署或隔离网络要求的团队应持观望态度，因为 AI 流量仍通过 Warp 服务器代理。需要代理循环具有宽松许可证的专有 Fork 构建者也应跳过，因为只有 warpui 是 MIT。
比起 AI 优先更喜欢人工优先代码审查的贡献者，会觉得规范 PR 和 Oz 自动分配的工作流程不舒服。今天需要无需账户的终端二进制文件的机构不会从这次发布中得到它。
## 从业者启示
随着 Warp 五年闭源期的结束，那些对开源感兴趣的开发者现在可以将代码发布到他们每天使用的终端中，由 Oz 审查 PR，如果被要求，Oz 云代理还可以实现 issue。
## 链接
- warpdotdev/Warp on GitHub (仓库，约 2 分钟快照)
- Warp is now open-source (公告，约 6 分钟阅读)
- CONTRIBUTING.md (贡献流程，约 8 分钟阅读)
- WARP.md 工程指南 (构建 + 架构，约 12 分钟阅读)
- docs.warp.dev (完整文档)
关注 @AlphaSignalAI 获取更多类似内容。
在 AlphaSignal.ai 订阅以获取每日 AI 信号。拥有 280,000+ 开发者读者。
## 问题？
**问：Warp 真的开源了吗？**
答：是的。客户端代码库已于 2026 年 4 月 28 日以 AGPL v3 协议发布到 github.com/warpdotdev/Warp，其中 warpui_core 和 warpui UI 框架 crates 采用 MIT 协议。2022 年开源客户端的承诺现已兑现。
**问：我可以在专有产品中使用 Warp 的代码吗？**
答：只有 MIT 许可的 warpui_core 和 warpui crates 可以在没有 Copyleft 义务的情况下使用。代码库的其余部分采用 AGPL v3，如果您分发或将修改作为网络服务托管，则必须发布源代码。
**问：如何从源码构建 Warp？**
答：克隆仓库，然后运行 ./script/bootstrap、./script/run 和 ./script/presubmit。cargo run 可以直接运行。完整的工程指南在 WARP.md 中。
**问：Oz 是什么，它如何为贡献者工作？**
答：Oz 是 Warp 的云代理编排平台。它自动分类传入的 issue 并对每个 PR 进行首轮审查。贡献者还可以通过提及 @oss-maintainers 派遣 Oz 云代理来实现 issue，这些请求在免费额度上运行。
**问：Warp 仍然需要登录或将我的数据发送到他们的服务器吗？**
答：预构建的二进制文件仍需登录，即使使用 BYO-key，AI 流量默认也通过 Warp 的代理路由。从源码构建可能会绕过登录，但这并非官方记录的无登录路径。不支持纯本地或隔离网络操作。
## 相关链接
- [AlphaSignal AI](https://x.com/AlphaSignalAI)
- [@AlphaSignalAI](https://x.com/AlphaSignalAI)
- [1.6K](https://x.com/AlphaSignalAI/status/2049534207412871477/analytics)
- [@warpdotdev](https://x.com/@warpdotdev)
- [Apr 28](https://x.com/warpdotdev/status/2049153766977421444)
- [2.5M](https://x.com/warpdotdev/status/2049153766977421444/analytics)
- [releasing similar tools earlier](https://x.com/AlphaSignalAI/status/2049172133578703181?s=20)
- [Apr 17](https://x.com/zachlloydtweets/status/2044870634711490938)
- [16K](https://x.com/zachlloydtweets/status/2044870634711490938/analytics)
- [@oss](https://x.com/@oss)
- [@oss](https://x.com/@oss)
- [@oss](https://x.com/@oss)
- [The 2022 Show HN thread](https://news.ycombinator.com/item?id=30921231)
- [build.warp.dev](https://build.warp.dev/)
- [@oss](https://x.com/@oss)
- [build.warp.dev](https://build.warp.dev/)
- [warpdotdev/Warp on GitHub](https://github.com/warpdotdev/Warp)
- [Warp is now open-source](https://www.warp.dev/blog/warp-is-now-open-source)
- [CONTRIBUTING.md](https://github.com/warpdotdev/Warp/blob/master/CONTRIBUTING.md)
- [WARP.md engineering guide](https://github.com/warpdotdev/Warp/blob/master/WARP.md)
- [docs.warp.dev](https://docs.warp.dev/)
- [@AlphaSignalAI](https://x.com/@AlphaSignalAI)
- [AlphaSignal.ai](https://alphasignal.ai/)
- [github.com/warpdotdev/Warp](https://github.com/warpdotdev/Warp)
- [@oss](https://x.com/@oss)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [1:00 AM · Apr 30, 2026](https://x.com/AlphaSignalAI/status/2049534207412871477)
- [1,614 Views](https://x.com/AlphaSignalAI/status/2049534207412871477/analytics)
---
*导出时间: 2026/4/30 11:30:36*