Template changes
Read the starter's release notes for workflows, presets, launch tooling and integrations.
October 12, 2026 — 1.5.0: more paths from an idea to a product
An eight-group creation wizard, four runnable presets, three theme presets and a component gallery now help you choose and generate an independent product. The shared CLI adds sandbox payment catalog and webhook setup for Waffo, Creem and Stripe, plus controlled three-way upgrades that preserve customer changes.
New AI workflows include persistent chat, private image editing and captioning, and web answers with linked sources. OpenAI-compatible, Workers AI and fal adapters share task recovery, private files and the credit ledger. API, TypeScript SDK, product Skill and builder Skill guidance are updated together.
Optional growth modules add waitlists, double opt-in newsletters, unsubscribe controls and reviewed broadcasts. Durable operational notifications support email, Discord and Feishu. Optional Umami, Plausible, Clarity and Crisp integrations are disabled until configured. A separately paired MV3 browser extension uses the same scoped API and credits. New products receive editable logo and favicon placeholders marked for personalization.
Local simulations and isolated contract checks do not connect or verify external services. Each product needs its own credentials, domains, model rates and payment catalog, followed by sandbox and production acceptance before those services are enabled.
October 12, 2026 — 1.4.0: first-launch guidance
New anonymous read-only demos, Standard and One-page template selection, three-step access guidance, and shared create/doctor/launch/resume/status commands. Launch receipts distinguish configuration from sandbox and production verification.
October 2, 2026 — Template onboarding
The initial site explains the mother template with five ordered launch guides, template capability pages, builder articles and use cases. The independent generator starts products with separate end-user content.
Local simulations, external setup and deployment evidence remain separate. Check the repository delivery report for implementation and verification records.