| Origin and purpose | Zed Industries develops GPUI for the Zed code editor as a hybrid immediate and retained mode, GPU accelerated framework. gpui.rs credits the creators of Zed and Delta and says GPUI implements the features those two apps need first, plus community requests. | Built by Anomaly as a native GPU-rendered Rust UI framework with its own renderer, text, layout and springs. Its public page calls OpenCode's desktop app the test Rune is built against, and every app can run headless so coding agents can check their work. |
|---|
| Rendering backends | Metal on macOS, DirectX 11 on Windows and wgpu on Linux, where X11 or Wayland handles windowing. Text on Windows uses DirectWrite, and glyph rasterization on macOS needs the font-kit feature. | Rune's own Metal backend on macOS, wgpu on Windows and on Linux, and WebGPU on a single canvas in the browser, with an optional WebGL2 fallback. Each frame is drawn by one instanced uber-quad pipeline in one draw call. |
|---|
| Platforms: desktop, web, iOS | The README covers macOS, Windows, and Linux or FreeBSD with Wayland or X11. The Zed repository also holds a gpui_web crate whose hello_web example builds for wasm32 on nightly Rust with Trunk. Neither the README nor gpui.rs documents iOS. | One codebase targets macOS, Windows, Linux with X11 and Wayland, iOS and the web. On iOS, Rune is embedded in UIKit or SwiftUI views; the web target is experimental and builds for wasm32-unknown-unknown. |
|---|
| API style and state model | State lives in entities owned by GPUI and reached through Rc-like smart pointers. A view is an entity implementing Render, styled with a Tailwind-style API, and a handler calls cx.notify() to request a new render. Low-level elements give imperative control. | A view is a plain Rust function of your state that returns elements, with no markup and no macro language. Press handlers are queued and run between frames with mutable state, then the view runs again and elements given motion move on springs. |
|---|
| Distribution and versioning | Published on crates.io as gpui, newest release 0.2.2 from October 22, 2025, with API docs on docs.rs. That release's README asks for macOS or Linux and starts apps with Application::new(), while the main-branch README adds an optional gpui_platform crate and Windows setup notes. | Not on crates.io: you add it as a Git dependency pinned to a revision of the dev branch, which is never rewritten. The core crate declares version 0.0.1, and apps must repeat Rune's crates.io patch entries in their own workspace. |
|---|
| Licence | Apache-2.0, declared in the gpui crate manifest, with copyright held by Zed Industries. The Zed editor crate in the same repository is GPL-3.0-or-later, so check the licence of any other Zed crate you copy. | MIT License, copyright 2026 Anomaly, set for the whole workspace in Cargo.toml. The project does not take pull requests; bugs and ideas go to GitHub issues instead. |
|---|
| Maturity | Pre-1.0 and in active development alongside Zed, with frequent breaking changes between versions. Contributions go through the Zed repository and stay in sync with the editor, and the README points to the Zed source code as the best way to learn the APIs. | Pre-release with no releases yet. The changelog lists changes that can move an app's output without a code change, so upgrading means reading it before you move your pinned revision. |
|---|
| Testing and accessibility | The gpui::test macro and TestAppContext let tests simulate common platform input. GPUI exposes an accessibility tree through AccessKit, and developers are responsible for making custom controls accessible. | Any app renders headless to a PNG with --snap, to a strip of frames with --frames, and prints its element tree with --tree. Tests drive the real runtime by key and clock. Accessibility is a default feature, built on patched AccessKit adapters. |
|---|