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
- Open Glixo Code and switch to Agxos mode.
- Launch App Creator from the desktop or Start menu.
- Enter your request (e.g. “image viewer for PNG and JPEG with zoom”) and a feature list.
- Preview the app on the Agxos desktop — send feedback until you approve the iteration.
Workflow phases
The creator runs a checkpointable workflow:
- Spec — capture an
AgxosAppSpecat.agxos/spec.json(id, name, app template, capabilities). - Scaffold — generate files and
glixo.module.jsonfrom the spec. - Iterate — agent edits; you approve or request changes (gate loop).
- Describe (optional) — marketplace description text.
- Icon (optional) — generate
assets/icon.svg. - Demo (optional) — record an Agxos replay for glixo.io embeds.
- 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.
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
- Finish the iterate gate (approved = true).
- Run optional describe / icon / demo steps.
- 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. - Fork
incident-notesoros-control-demofrom the marketplace if you need a working baseline. - Keep module ids stable — use reverse-DNS (
com.you.apporglixo.you.app).