App Maker (App Creator)

App Maker is the Agxos App Creator workflow: you describe a small desktop app, the agent scaffolds a real module under your workspace, you iterate until it looks right, then optionally generate marketplace assets and publish.

When to use App Maker

• From scratch — plain-language request + feature list → new app module.
• Fork — copy an existing catalog or built-in app, then dictate the diff you want. See Extend an existing app.

Both paths produce a module directory (typically under .agxos/extensions/<slug>/) with glixo.module.json and app source.

How to start

1. Open Glixo Code and switch to Agxos mode.
2. Launch App Creator from the desktop or Start menu.
3. Enter your request (e.g. “image viewer for PNG and JPEG with zoom”) and a feature list.
4. Preview the app on the Agxos desktop — send feedback until you approve the iteration.

Workflow phases

The creator runs a checkpointable workflow:

1. Spec — capture an AgxosAppSpec at .agxos/spec.json (id, name, app template, capabilities).
2. Scaffold — generate files and glixo.module.json from the spec.
3. Iterate — agent edits; you approve or request changes (gate loop).
4. Describe (optional) — marketplace description text.
5. Icon (optional) — generate assets/icon.svg.
6. Demo (optional) — record an Agxos replay for glixo.io embeds.
7. Publish (optional, gated) — push to the catalog via glixo.dev.

Progress is saved in .agxos/workflow/checkpoint.json so you can resume after closing the session.

Authoring docs the creator must read

Before each implementation pass, App Creator is expected to ground its changes in the versioned App Creator docs bundle and the current module files. The bundle index is https://extend.glixo.io/artifacts/docs/v0/index.json; read every file it lists.

• app-creator-system.md — compact provider/system-prompt contract for app generation.
• app-author-guide.md — workflow phases, checkpoints, and publish gates.
• agxos-template-guide.md — no-code app templates and intent actions.
• agxos-coded-guide.md — sandboxed app.js, window.agxos, file associations, display surfaces, and capability-gated requests.
• manifest-reference.md and module.schema.json — manifest fields and validation contract.

The human Builder Docs pages here mirror and explain that material, but the agent/provider should start from the versioned bundle. If the deployed bundle is unavailable, the agent should fall back to the checked-in markdown/source and manifest schema. It should not invent request names, capability names, SDK packages, manifest fields, or build steps from memory.

AgxosAppSpec (simplified)

{
  "id": "glixo.my-notes",
  "name": "My Notes",
  "description": "Quick scratch pad",
  "version": "0.1.0",
  "app": {
    "id": "my.notes",
    "name": "My Notes",
    "template": "note",
    "width": 560,
    "height": 420,
    "actions": [{ "id": "write", "description": "Set note text" }]
  },
  "capabilities": ["filesystem.workspace.read"]
}

The host converts the spec to a full manifest via specToManifest. Template apps publish end-to-end today; custom coded apps need a built bundle artifact.

Publishing from App Maker

1. Finish the iterate gate (approved = true).
2. Run optional describe / icon / demo steps.
3. Confirm publish — requires sign-in on glixo.dev and a public source repository URL for marketplace-listed Agxos apps.

Or publish manually: validate on the dashboard, then use the authenticated catalog API (see Publish flow).

Tips

• Start with a template (note, list) before a full coded app.
• Start from a working sample under glixo-extensions-docs/samples, not from an arbitrary marketplace product.
• Keep module ids stable — use reverse-DNS (com.you.app or glixo.you.app).