How App Composer works
App Composer prepares a real environment and joins independently maintained apps. It uses external Codex for execution and EmDash for its managed catalogue; it does not host a competing agent.
Read the original visual architecture explainers
From no idea to a live app
- Get Ready. The agent checks its actual workspace, GitHub and Cloudflare tools. It verifies the target and deploys the configurable Hello World reference over HTTPS.
- Init. Choose a useful preset and customise real fields. Export a versioned spec and a matching prompt, without credentials.
- Compose. Pin independent source commits, validate their declared routes, data versions and capabilities, and connect their real item/action interface.
- Verify. Check source identity and live interaction, not just HTTP 200 or a green build.
The first composition
Photo Guestbook owns submitted media, moderation and eligibility. Curated Showcase owns its card collection. An approved item can be selected and featured; opening its card opens the source contribution. Unavailable, hidden or deleted sources fail closed. Composer joins the routes through Worker service bindings; there are no iframes or private media copies.
Updates preserve your work.
App configuration and owner data live separately from upstream source. A candidate must keep the supported contract and data version, pass capability checks and use exact commits. Incompatible versions or new permissions are rejected before activation. Your working release stays live.
The first path uses explicit, validated promotion through repository commands. Automatic branch following and webhook-driven updates remain unshipped until their concurrency and conflict gates are proven.
Code rollback restores an executable only. It never restores an old database, republishes a hidden image or discards later submissions. Storage exports and backups have their own authorised recovery path.
The supported boundary
This first release is operated by an authorised agent using its own GitHub/Cloudflare runtime. Public users can browse examples, explore decisions and export a spec. They cannot launch arbitrary builds, access production credentials or moderate another owner’s collection.
Owner uploads are capped and invited. No current feature implies a public multi-tenant security guarantee, provider partnership or commercial agreement.
Try fictional encrypted assistant state · Optional Cloudflare dashboard extension · Verified release evidence