Extension user interface
An extension can add a panel at a named location in Glixo, called a placement. Glixo supplies the surrounding navigation, title, close button, keyboard behavior and permission screens. The extension supplies its panel's content.
Build a complete example
- Settings panel: generated files, complete manifest, HTML bridge, Save handler, asset hashes and run steps.
- Context menu action: declaration, guest implementation and permission tests.
Shared controls and custom surfaces
The Accessible Theme example is a settings panel called Custom Settings Panel, with action code in C#, Go, Rust and TypeScript. It saves preferences for its own UI; it does not change Glixo Code's appearance. Glixo has no installed-theme selector.
The separate @glixo/extension-ui helper provides controls, colors and typography for extension authors. It is experimental source code, not an installable theme.
Configuration forms
Configuration forms are Preview and support a subset of JSON Schema:
- A schema and its submitted value can each use up to 64 KiB and 16 nesting levels.
- Objects support
properties,requiredand booleanadditionalProperties. - Arrays need an
itemsobject schema andmaxItemsbetween 0 and 64.minItemsis optional. - Nested values are checked against these limits. Nested secret fields are rejected.
Use Glixo's connection setup for credentials. The configuration editor does not implement every JSON Schema feature.
Panels and theme values
Custom web panels run in isolation and communicate with Glixo through a versioned bridge. That bridge can provide theme mode, fonts, colors, spacing, contrast, reduced-motion settings, locale and text direction. Use those values in your UI; Glixo cannot automatically restyle arbitrary canvas drawings or custom CSS.
Bridge access belongs to the current extension, account and approved permissions. Updates, uninstall, permission changes, account switches and frame reloads invalidate that access. Mobile WebView support is not available for this sample.
Placements and responsive behavior
Use the placement IDs supported by the app version you target, such as settings.extensions for the sample settings panel or code.main-panel for an extension panel in Glixo Code. Declare commands and actions through the public descriptors instead of accessing Glixo's DOM or private React components.
Make your content work at narrow widths, with keyboard navigation and screen-reader labels. Glixo manages the surrounding panel's focus and close behavior. See UI examples and compatibility for the current limitations.