Local development and testing

Test extensions and Agxos apps against a local marketplace before publishing to production.

Prerequisites

• Glixo Code dev stack (dev.cmd from moron-cursor) for IDE + Agxos iframe
• Portal stack (portals.cmd) for local marketplace (:8184) and glixo.dev (:8185)
• Clone glixo-community-modules and add your module under catalog/

Sync catalog to the dev portal

cd glixo-portals/dev
npm run catalog:sync
npm run catalog:pack

By default the portal refreshes a managed clone of the canonical GitHub repository. Point GLIXO_COMMUNITY_MODULES_REPO at your own working clone when testing unpublished changes; explicit developer clones are never fetched, reset, or cleaned by portal tooling.

Validate a manifest

Use the Validator on glixo.dev → Dashboard → Validator, or:

curl -X POST https://api.glixo.dev/v1/extensions/validate \
  -H "content-type: application/json" \
  --data-binary @glixo.module.json

Install in Glixo Code

With the local marketplace running, open the Marketplace app in Agxos or use a deep link:

glixocode:///extensions/install?id=your.extension.id

Enable contributed UI when prompted (sidebar, settings, etc.).

Pack artifacts

From the community repo, zip your module (excluding dev-only files) and update artifacts[] with the SHA-256 hash:

cd glixo-community-modules
node scripts/pack-catalog-artifacts.mjs

App Maker local loop

1. Start App Creator in Agxos — module lands under the workspace .agxos/ tree.
2. Iterate until approved; manifest and bundle update in place.
3. Copy or symlink into catalog/agxos/apps/ for catalog sync, or publish via API.