Extension SDK
The SDK connects your extension code to Glixo's approved host operations. Use it to store extension settings, read selected workspace files, call an approved HTTP endpoint, or translate a model's stream into Glixo events. You build your own project into a WebAssembly component; Glixo loads that component after installation and permission approval.
The SDK consists of small language libraries and WIT interfaces. WIT describes the functions imported from Glixo and exported by your component. Generated bindings translate those functions into your language. The libraries provide convenient types and streaming helpers; the bindings provide the actual connection to Glixo.
Choose a language
| Language | Get the SDK | Start building |
|---|---|---|
| TypeScript | Published npm package @glixo/extension-sdk@0.1.0, or the scaffold's vendored source |
TypeScript SDK |
| C# | Vendored Glixo.ExtensionSdk project; NuGet package not published |
C# SDK |
| Go | Published module github.com/tmedanovic/glixo-community-modules/packages/extension-sdk/go@v0.1.0, or vendored source |
Go SDK |
| Rust | Vendored glixo-extension-sdk crate; Cargo package not published |
Rust SDK |
Download SDK source, WIT and UI helpers. The archive contains the public files used by these guides, a source identity file and setup README. You can inspect them without access to Glixo's application source. Start with a CLI project for the component build settings; importing the SDK by itself does not create an extension.
npm install --global @glixo/glxdev@0.3.5
glxdev new --kind reference --reference workflow-text-stats --language typescript --package-id org.example.text-stats --name "Text statistics" --publisher org.example --output ./text-stats
cd text-stats
glxdev doctor
glxdev check
Replace the language with csharp, go or rust. The language guides contain their build commands. The development guide takes the resulting component through signing, installation, activation and publication. SDK and CLI versions are separate; all SDK languages remain Preview.
API guide
| Task | Documentation and working source |
|---|---|
| Receive a call, validate input and return a result | Invocation and host APIs, Text Stats guest |
| Save settings or checkpoints | Scoped state, Workspace Storage handler |
| Read or search workspace files | Workspace APIs, Document Index handler |
| Call HTTP, use a credential slot and release a response | HTTP SDK, Mail Watch handler |
| Discover models and implement streaming | Provider SDK, Ollama provider |
| Build a panel, apply themes and invoke an action | UI SDK, complete panel tutorial |
| Schedule work or process messages | Services and events, message processing |
What belongs in your project
Keep the generated wit/ directory, compiler locks and glixo.project.json aligned. Tools, actions, data sources, services and message handlers use the contribution world. Model providers use the provider world. Preserve the world's literal identifier in both the component and manifest; it selects the component's function contract.
Implement adapters once near the guest entry point. Keep your handler independent of generated bindings, so a test can supply an in-memory state store or a fake HTTP broker. A fake broker verifies handler logic; check permission approval, real connections and persistence separately in the installed app.
@glixo/sdk and Glixo.Sdk are internal platform service packages. They are not the guest SDK and are not public prerequisites for these examples. A web panel uses the injected bridge and bundled UI assets. It does not import a server SDK or receive raw credentials.
Source and compatibility
Read the public SDK source overview, pinned toolchain and recipe matrix, and runtime interfaces. The source READMEs describe packaging at that revision; the install instructions above reflect the published npm and Go packages. Use the support reference for app and platform limits.