Contribution model
A contribution is a feature declared by an extension. One package can contain several contributions and is installed and updated as a whole. Each contribution declares the permissions it needs.
| What you want to add | Contribution | Example |
|---|---|---|
| Connect a model | LLM provider | Ollama provider |
| Give an agent a capability | Tool, action, skill or MCP tool | Issue Lookup |
| Add a workflow step | Tool used by Workflow Designer | Workflow Text Stats |
| React to activity | Event subscription or event publisher | Mail Watch emits mail.received |
| Run scheduled work | Background service | Mail Watch checks for new messages |
| Read or change conversation data | Message observer or middleware | Conversation Insights and Prompt Redactor |
| Add a settings panel | Sandboxed web UI | Accessible Theme, shown as Custom Settings Panel |
| Open an extension panel | code.main-panel placement |
A panel inside Glixo Code |
| Reuse Glixo controls and colors | @glixo/extension-ui helper |
Controls for your own panel |
| Store or inspect workspace data | Data source or storage | Workspace Health, Document Index and Workspace Storage |
| Change the app's appearance | Theme contribution | Planned; Glixo has no installed-theme selector |
Describe the feature in a manifest
The CLI creates glixo.extension.json in your project. This JSON file connects each contribution to its code and lists the permissions the user will review. For example, an action named save-preferences points to a component that implements the Save button's behavior.
Start with the complete manifest walkthrough, including a working tool manifest, field descriptions, a panel example and validation commands. glxdev pack generates glixo.module.json, which describes the ZIP offered through the catalog. The distribution reference explains that generated file and its signatures.
An LLM provider may also implement the optional account-status/1.0.0 interface to report plans, quotas or billing. It remains part of that provider contribution; inference-only providers do not need a status implementation. See account-status reporting for its declaration and snapshot meanings.
Installation and permissions
Installing a package stores it in Glixo. Activation starts its enabled features after the user approves the requested permissions. External services also need an approved account connection; approving the package alone does not connect a mailbox or model endpoint.
Glixo checks the active package, account and permissions each time a contribution runs. Removing a permission can disable the feature that needs it. The example's compatibility notes describe whether installation and use in the app have been tested, or whether only its development source is available.