GPUI keeps application state and declarative UI policy in Elixir while native displays interpret immutable snapshots. Choose a path below based on what you are trying to do.
Build an application
- Start with Your first application.
- Learn the runtime model in Sessions, snapshots, and displays.
- Browse UI components, Commands and keyboard shortcuts, and Overlays and menus.
- Choose the appropriate test tier in Testing GPUI applications.
Use framework capabilities
- Remote displays connects an application session to a display in another process or machine.
- Native builds and deployment covers source builds, feature sets, and release validation.
- Editable text surfaces explains persistent buffers, revisioned edits, submission, geometry, and annotations.
- Presentation primitives explains bounded edge fades, frost fallbacks, and custom paint for application authors.
- Test coverage ownership identifies which test tier owns each kind of behavior.
Contribute to GPUI
These documents describe implementation boundaries rather than the normal application-authoring workflow:
- Platform support and development status
- Editable text internals
- Native text projections
- Accessibility
- Transfer payloads
- Presentation extension contracts
- Declarative motion decision
- Window chrome decision
The project is private and unreleased. Internal payloads may change directly; version fields detect mismatched running components rather than promise support for historical revisions.