Local development and testing

Test extensions and Agxos apps against a local marketplace. Public VNext publishing is currently unavailable.

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

Use glxdev for the supported Rust local test path. Test-fixture activation is local evidence only; catalog installation and production publisher admission are not established by a protocol-v0 record.

glxdev check --project ./my-provider
glxdev build --project ./my-provider
glxdev test --project ./my-provider
glxdev pack --project ./my-provider
glxdev verify --project ./my-provider

Legacy catalog preview

Catalog sync is for local browse/projection checks. The old ZIP packer does not produce a VNext package and must not be used to re-sign or publish protocol-v0 material.

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. Keep the output local for review; public VNext publishing is unavailable.