What extensions can I build?

Every installable extension ships a glixo.module.json manifest and declares one or more contributions under contributes.*. Required top-level manifest fields: id, name, version, protocolVersion, runtime.kind, entry.command, and at least one capabilities entry (see the Manifest reference).

Pick the type you want to build — each page has a real, copy-pasteable example.

Providers & adapters

Declarative — register a model or storage backend, no server code.

Agent extensions

Give the agent new tools, skills, MCP servers, or run-time context.

IDE UI surfaces

Contribute UI into Glixo Code.

Agxos apps

Windowed desktop apps that run in Agxos (and, increasingly, in IDE surfaces).

Entry fields without surprises

Glixo uses two different "entry" ideas. Keep them separate so your package works in clean installs and older hosts:

• components[].entry is launch metadata for a component process. Prefer explicit sibling command and args fields when you need to start Node or another runtime.
• contributes.agxos.apps[].entry is a coded iframe app bundle path such as dist/app.js.
• Do not import private Glixo Code files through @tmedanovic/glixo-code/sources/.... Use documented package exports only; private source paths may fail in CI or hosted installs.

{
  "components": [{
    "id": "worker",
    "cell": "server",
    "scope": "workspace",
    "command": "node",
    "args": ["server/index.js"],
    "placement": { "kind": "workspace", "required": false }
  }],
  "contributes": {
    "agxos": {
      "apps": [{
        "id": "recorder",
        "name": "Recorder",
        "template": "app",
        "entry": "dist/app.js"
      }]
    }
  }
}

Themes & services

Once you've built one, see Local development to test it and Publish to ship it to the catalog.