Choose an extension type
Start with the kind of behavior you want to add. Glixo separates model providers, agent instructions, and features supplied by the application itself.
| Goal | Starting point | What you can build today |
|---|---|---|
| Connect an OpenAI-compatible model endpoint | Rust provider template | Build and test a WebAssembly component with glxdev |
| Teach an agent a workflow | Skills template | Scaffold and check instruction files; packaging is limited in CLI 0.2.0 |
| Modify an application panel or native integration | Glixo Code source | Changes require an application build |
Recommended first project
Follow Local development to create a provider, run the conformance suite, and verify a package. Read Manifests before changing configuration or permissions.
Catalog entries and installation
Some catalog entries describe features already supplied by Glixo Code. Their settings configure the installed application. An installable extension additionally needs a supported package and a valid publisher signature. The catalog's installation status tells you which action is available.
Before publishing
Choose a stable package ID, test the endpoint failure paths, and review every requested permission. See Publishing API for publisher setup and the release contract.