Paneflow vs Warp
Paneflow and Warp are both Rust + GPU + cross-platform terminals that ship AI today. They diverge on incentive structure, not category. Paneflow is MIT throughout, no login, no telemetry, no paid tier, no server backend - a single binary that launches the CLI agents (Claude Code, Codex, OpenCode) you already use, on Zed’s GPUI engine. Warp is AGPL-3.0 on the client (MIT for the warpui crates) with a closed-source backend, paid tiers at $20-$50 per user per month, a telemetry requirement on the Free tier for AI access, and a separate cloud-orchestration product called Oz. OpenAI is the founding sponsor of the new open-source repo. Pick Paneflow if you want a local-first, MIT, no-strings agent host. Pick Warp if you want a built-in AI agent, a shared team command library (Warp Drive), and an enterprise commercial path.
A note on context
Warp open-sourced its client codebase in late April 2026 - a real shift from the pre-2026 closed-source SaaS model, and worth acknowledging honestly before comparing. Per Warp’s own master/README.md NOTE block: “OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.” Anyone evaluating Warp should treat the open-source pivot as the headline change of 2026.
One non-obvious twist: the source code lives on the master branch of github.com/warpdotdev/Warp, not on main(which is still an issues-only repo with a stale “currently closed-source” LICENSE file). The repo’s actual Cargo.toml, LICENSE-AGPL, and LICENSE-MIT all sit on master. A reader who checks main alone will reach the wrong conclusion - worth flagging up front because it changes how you read the rest of this page. All Warp source-code references below point at master URLs.
The open-source pivot does not erase the underlying business model. Warp’s server backend stays closed-source, the Free tier gates AI behind a telemetry requirement, and paid tiers ($20-$50 per user per month) are the path to AI without telemetry and to team features (Warp Drive, SSO, Zero Data Retention). Paneflow has none of that machinery - the entire product is a single MIT binary.
Quick comparison
Grouped in three zones - license & data posture (where Paneflow leads), core terminal parity (where both are equivalent), and the agent + team surface (where Warp has shipped much more).
License & data posture
| Paneflow | Warp | |
|---|---|---|
| License (client) | MIT throughout | AGPL-3.0 client + MIT for warpui crates |
| Backend | n/a (no server) | Closed-source server stays proprietary |
| Login required to use terminal | No | No (lifted Nov 2024) |
| Telemetry required for AI on Free tier | n/a (no Free tier; no AI service) | Yes (Warp docs verbatim) |
| Per-seat pricing | n/a | Build $20/mo, Business $50/user/mo |
| Paid tiers / credit caps | n/a | Free 75 cr/mo (150 first 2 mo), Build 1500/mo, Business 1500/user/mo |
| Founding sponsor / commercial backing | Indie (Arthur Jean) | Denver Technologies, Inc.; OpenAI founding sponsor of OSS repo |
| Embed in closed-source product | Yes (MIT) | warpui crates only (MIT); rest is AGPL-3.0 |
Core terminal parity
| Paneflow | Warp | |
|---|---|---|
| Language | Rust | Rust |
| GPU stack | GPUI/Blade over Vulkan + Metal | Custom Rust + Metal-direct (forked Alacritty grid model, custom renderer) |
| OS support | Linux + macOS (Windows planned) | Linux + macOS + Windows GA |
| VT emulator | alacritty_terminal 0.26 (upstream) | Forked from Alacritty grid model |
| Pane layout + tabs | Yes | Yes |
| Session restore | Yes | Yes |
| Themes | Bundled + JSON override | Bundled + YAML override (cloud-synced) |
| Cross-platform breadth | Linux + macOS now | Linux + macOS + Windows now |
Agent & team surface
| Paneflow | Warp | |
|---|---|---|
| AI agent model | Launches external CLI agents (Claude Code, Codex, OpenCode) | Built-in AI agent + supports launching CLI agents |
| Cloud orchestration layer (parallel server-side agents) | n/a | Oz (available from Build $20/mo) |
| Shared team command library | n/a | Warp Drive |
| SAML / SSO | n/a | Business tier ($50/user/mo) |
| SCIM / team admin console | n/a | Business tier |
| Zero Data Retention enforcement | n/a (no data collected) | Business tier (team-wide enforced) |
| Shared credits pool | n/a | Business tier |
| Commercial support contract | n/a | Available via Enterprise tier |
Versions: Paneflow v0.2.16 (May 2026), first commit 2026-04-01. Warp client open-sourced 2026-04-28 (Denver Technologies, Inc., copyright 2020-2026). Pricing: Paneflow free MIT. Warp Free 75 credits/month (150 for the first two months) + Build $20/month + Business $50/user/month + Enterprise custom.
Which one is right for you?
The honest version: the choice is mostly about how you want your terminal to relate to a vendor backend. If you want zero relationship with a backend, Paneflow. If you want a polished built-in AI agent + a team-scale path, Warp.
Choose Paneflow if
- -You want local-first - no login, no telemetry, no server backend, no paid tier ever
- -You want MIT throughout, so embedding terminal code in a closed-source product is straightforward
- -Your agent workflow is launching the CLI agents (Claude Code, Codex, OpenCode) you already use, not vendoring a chat surface
- -You prefer an indie maintainer aligned with the Zed philosophy over a venture-backed product with paid tiers
- -You do not need shared team command libraries, SSO, or commercial support
- -You want a single binary you can audit, fork, and ship without a license boundary inside the codebase
Choose Warp if
- -You want a polished built-in AI agent inside the terminal, not just CLI agents launched in a pane
- -You want a shared team command library (Warp Drive) and cloud-synced settings
- -You need SAML SSO, SCIM, team admin features, or central billing
- -You want Oz cloud orchestration to spawn parallel coding agents server-side at scale
- -You are comfortable with AGPL-3.0 on the client (or only need the MIT warpui crates) and accept a closed-source backend
- -You want OpenAI as the founding sponsor and direct commercial support paths via Enterprise tier
- -You will pay $20-$50 per user per month for AI credits, ZDR enforcement, and team features
Architecture deep-dive
Warp is a Rust workspace with crates including app, warp_terminal, warpui, warp_completer, editor, markdown_parser, and others - the workspace Cargo.toml declares license = "AGPL-3.0-only" with the warpui crates carved out as MIT. The renderer is custom: Warp forked Alacritty’s grid and VT model but wrote its own GPU renderer that talks to Metal directly on macOS, via about 200 lines of custom shaders. Alongside the local app, Warp ships a closed-source server backend that powers AI features, Warp Drive, and cloud-synced settings; Oz, the cloud orchestration product, runs agents server-side and connects via “handoff” from the local terminal.
Paneflow is a pure-Rust application built on Zed’s GPUI engine - no language boundary between UI and terminal, no closed-source backend, no AI service to feed. Terminal emulation is upstream alacritty_terminal0.26 from crates.io (where Warp uses its own fork of the grid model). The GPU layer is GPUI’s Blade renderer over Vulkan on Linux and Metal on macOS. The agent surface is intentionally thin: Paneflow provides workspaces, panes, branch detection, and three first-class CLI agent buttons (Claude Code, Codex, OpenCode). Any binary you can run in a shell runs in a Paneflow pane; unlike Warp, there is no vendored multi-vendor chat. No telemetry, no analytics service, no login.
The IPC surfaces are also instructive. Warp talks to its backend over GraphQL (the graphql crate ships in the workspace) plus a telemetry pipeline that is required for Free-tier AI per Warp’s own docs. Paneflow exposes a single JSON-RPC 2.0 server over a Unix socket at $XDG_RUNTIME_DIR/paneflow/paneflow.sock with roughly thirteen methods - no telemetry, no analytics. For most developers the difference is invisible; for one who cares about local-first posture, it is the whole product.
Pricing
The licensing and pricing models differ sharply.
- -Paneflow: MIT, Copyright (c) 2026 Arthur Jean. Single free tier, no paid plans, no per-seat pricing, no AI credits, no telemetry. Embed it in commercial products without concerns.
- -Warp: hybrid license (AGPL-3.0 client + MIT warpui crates), Copyright (c) 2020-2026 Denver Technologies, Inc. Four tiers: Free ($0, 75 AI credits/month after a 2-month bump, telemetry required for AI), Build ($20/month, 1 500 credits + BYOK), Business ($50/user/month, SSO + enforced team-wide Zero Data Retention + shared credits), and Enterprise (custom, with commercial support).
Migrating from Warp to Paneflow
There is no automatic path. Warp uses a YAML config plus cloud-synced settings tied to your Warp account; Paneflow uses a static JSON file at ~/.config/paneflow/paneflow.json on Linux and ~/Library/Application Support/paneflow/paneflow.json on macOS. Plan ten minutes for a fresh setup: default shell, theme, keybindings, agent buttons. Three Warp features do not have Paneflow equivalents and the migration plan is “keep using Warp for those” rather than “recreate locally:”
- -Warp Drive: shared team command-and-snippet library. No Paneflow equivalent. If Warp Drive is core to your team, stay on Warp.
- -Built-in AI agent: Paneflow does not ship a vendored chat surface. The migration is to use the CLI agent of your choice (Claude Code, Codex, OpenCode) launched as a pane.
- -Oz cloud orchestration: no Paneflow equivalent. If you need parallel server-side agents at scale, Oz is the right tool.
- -SSO + team admin: no Paneflow equivalent. Paneflow is built for individual developers, not for orgs that need centralized terminal management.
When NOT to choose Paneflow
The honest dealbreakers. If any of the five below matters to you, Warp is the right tool today - no point fighting it:
- 1.You want a vendored, built-in AI agent inside the terminal. Warp ships a polished in-terminal AI chat - Paneflow only launches external CLI agents (Claude Code, Codex, OpenCode) as panes. If your workflow is “chat about my terminal output without leaving the terminal app,” Warp is the right fit.
- 2.You want a shared team command library (Warp Drive). Warp Drive is the unique product feature that Paneflow cannot replicate without a backend. If your team depends on shared commands, snippets, and notebooks, Warp is the right tool.
- 3.You need SAML SSO, SCIM, or central team admin. Warp Business at $50/user/month ships these for orgs that need centralized auth, audit, and provisioning. Paneflow has no team tier and no admin console.
- 4.You want a commercial support contract. Warp Enterprise offers paid support; Paneflow is an indie project with no commercial-support track. If you need a phone number to call when something breaks, Warp is the right fit.
- 5.You want cloud-synced settings. Warp syncs settings, themes, and workflows through your account. Paneflow stores everything in a local JSON file - portable via git or dotfiles, but no built-in cloud sync.
Frequently asked questions
Is Paneflow a fork of Warp?
No. Warp is a Rust + Metal terminal built by Denver Technologies, Inc., open-sourced in April 2026 with a hybrid license (AGPL-3.0 for the client, MIT for the warpui_core and warpui crates). Paneflow is a separate Rust + GPUI codebase by Arthur Jean, MIT throughout. The two share no source code and ship under different business models (Warp has paid tiers + a closed-source backend; Paneflow is a single MIT binary).
Both are Rust + GPU + cross-platform. What is the actual difference?
Incentive structure and agent architecture. Warp is AGPL-3.0 on the client but the server backend stays closed-source, Free-tier AI requires telemetry, and team features (Warp Drive, SSO, ZDR, shared credits) sit behind $20-$50 per-user-per-month tiers. Paneflow is MIT throughout, no login, no telemetry, no paid tier, no backend. Warp ships a built-in AI agent plus Oz (cloud orchestration); Paneflow only launches the CLI agents (Claude Code, Codex, OpenCode) you already use.
Is Warp's source code actually public? I checked github.com/warpdotdev/Warp and saw 'currently closed-source.'
Yes, the source is public, on the master branch - which is a non-obvious twist. github.com/warpdotdev/Warp has two branches: main is configured as an issues-only repo with a stale LICENSE file that still reads 'currently closed-source,' while master holds the actual open-sourced Rust workspace (Cargo.toml, LICENSE-AGPL, LICENSE-MIT, full source tree). The April 2026 announcement is real. If you only check main, you will conclude Warp is still closed-source - check master.
What does 'AGPL-3.0 client + MIT UI framework' mean for embedding?
Warp's repo splits the license at the crate boundary: the warpui_core and warpui crates are MIT, the rest of the codebase (the terminal core, the AI surface, the orchestration code) is AGPL-3.0-only per the workspace Cargo.toml. You can pull warpui into a closed-source product; you cannot pull the rest. Paneflow's MIT covers everything - the terminal core, GPUI integration, and IPC server are all MIT - so embedders do not have to track a license boundary inside the codebase.
Why does Warp's Free tier require telemetry but Paneflow does not?
Different business models. Warp's Free tier is the funnel: telemetry feeds the AI product, the AI product generates conversion to paid tiers. Per Warp's own docs at docs.warp.dev: 'Telemetry must be enabled to use AI features on the Free plan, while paid plans can opt out at any time and continue using Warp, including AI.' Paneflow has no paid tier, no AI service to feed, and no business reason to collect telemetry. Login was also lifted from Warp in November 2024, but the telemetry gate on Free-tier AI remains in 2026.
What about Oz? Is that the same as the in-terminal Warp AI agent?
No. Oz is a separate cloud-orchestration layer from the Build plan ($20/user/month): it spawns parallel coding agents server-side, with a 'handoff' that moves a session from the local terminal to Oz for more compute. The in-terminal Warp AI agent is the local interactive feature. Paneflow has neither - it launches local CLI agents in panes, no cloud layer, no orchestration service.
Does Paneflow have team pricing or SSO like Warp's Business tier?
No. Paneflow is a single MIT binary with no team tier, no SSO, no SCIM, no team admin console, no per-seat billing. If you need any of those, Warp Business at $50/user/month is the right tool - it ships SAML SSO, enforced team-wide Zero Data Retention, shared credit pools, and central billing up to 50 seats. Paneflow is built for individual developers; if your org needs centralized terminal management with auth controls, look at Warp.
Can I migrate my Warp settings to Paneflow?
There is no automatic path. Warp uses a YAML config plus cloud-synced settings; Paneflow uses a static JSON file at ~/.config/paneflow/paneflow.json on Linux. Plan ten minutes for a fresh setup: default shell, theme, keybindings, agent buttons. Workflows that depend on Warp Drive (the shared command-and-snippet library) do not have a Paneflow equivalent - if Warp Drive is core to your team workflow, stay on Warp.
Next steps
Ready to try Paneflow? Download the latest release or read the getting-started guide. Curious about Warp instead? Warp’s open-source code is on GitHub (master branch, not main) - the open-source pivot was the headline change of 2026 and worth respecting on principle, even if Paneflow lands on the other side of the local-vs-cloud tradeoff.