Build, test, and publish an extension

Install the published @glixo/glxdev CLI with Node.js 22 or newer:

npm install --global @glixo/glxdev@0.3.3
glxdev --version
glxdev doctor

Version 0.3.3 includes C#, Go, Rust, and TypeScript project templates and build recipes, including workflow-text-stats.

Create, build, and check a project

Create an Ollama provider project, then check, build, and test it. Testing requires the Glixo extension host:

glxdev new --kind llm-provider --language typescript --package-id org.example.ollama --name "Ollama Provider" --publisher org.example --output ./ollama-provider
cd ollama-provider
glxdev check
glxdev build
glxdev test --development --host-path <path-to-glixo-extension-host>
glxdev pack
glxdev verify

Use --language csharp, go, rust, or typescript. To start from another example, choose it from the reference list and run glxdev new --kind reference --reference <reference-id> --language <language>. The CLI selects its template and build recipe. check validates project files, build creates the component, and test runs provider examples against the test host with sample responses. pack creates a package, and verify checks it. These tests do not install or activate the package or contact a live provider.

For example, scaffold the workflow text statistics tool with glxdev new --kind reference --reference workflow-text-stats --language typescript --output ./workflow-text-stats. Select csharp, go, or rust for the other language templates. The example package passed tests in all four languages. You need a newer app release to use it in Glixo.

Use the source tabs and SDK matrix for compiler versions and exact build commands. Each language README explains how to build that example directly. The published CLI version is 0.3.3.

Check the feature in the released app

Before releasing a feature that uses an extension panel, settings, or actions, test the signed app on each desktop system where the feature is available (Windows, macOS, or Linux). Reopen the app and check that settings were saved, try the actions, check any promised theme behavior, confirm the panel loads only allowed resources, and revoke its grant to confirm the app disables it. Test on Android only if the same feature is available in the Android app.

Install for development

glxdev auth login
glxdev install --development --cell-url <app-url>

The signed-in account needs integrations.manage. Development install checks and stores the package but leaves it inactive. Review its requested permissions and approve them in Glixo before activation.

For external services, the user separately approves the account connection's endpoint, methods, and paths. The package grant and approved connection are distinct; the host issues a scoped handle for each invocation. Do not put credentials in the manifest, guest configuration, or browser assets.

Publish

Catalog publishing is not available yet because its endpoint is still being configured. Auth0 sign-in works. When publishing is enabled, run glxdev publisher to create and register your key, import its Glixo-root certificate, and check readiness. Run glxdev publish --dry-run to review issues, then glxdev publish. A local test or package check does not publish your extension; confirm publication in the catalog response.

Current limits

The Ollama example passed offline tests in C#, Go, Rust, and TypeScript. All four languages also completed local Gemma tool calls and follow-up responses. These tests used a newer extension runner that Glixo 0.7.8 does not include, so you need a newer app release to try them. See the Ollama walkthrough.

The Workflow Text Stats example passed tests in all four languages, including configuration, grant revocation, and package-change checks. Glixo 0.7.8 cannot run it; a newer app release is required. See Workflow Text Stats.