Add the Website Generator module to this existing Agent OS app using the supplied website-generator-source.zip. Read the app instructions first. Preserve existing user changes. Inspect the supplied source before merging.

Copy the new src/app/website-generator, src/app/api/website-generator, src/components/WebsiteGenerator.tsx and .css, src/lib/websiteGenerator.ts, scripts/website-generator and scripts/website-generator-check.cjs into matching paths. Add src/lib/designOrigin.ts only if absent; otherwise verify and reuse the existing helper. Reuse the app's existing config.codex and installed dependencies. If config.codex is missing, implement equivalent executable discovery and configuration; do not hardcode the original author's paths.

Add Website Generator to Sidebar.tsx pointing to /website-generator and add its title to TopBar.tsx. Do not replace either whole file. Use the navigation snippets in INSTALL.md. Keep the app bound to localhost. The Python worker needs Python 3.9+ and the configured, signed-in Codex CLI for fresh copy. No new package dependencies are required for the supplied app version.

Run the Python worker tests and TypeScript check. Start the app, open /website-generator, and use Open patio example. Then run the endpoint check against the actual local port. Generate one fresh fictional brief and verify linked service pages, mobile layout, notes and ZIP contents. Confirm saved drafts survive a page reload. Keep previews noindex and forms in demonstration mode. Report failures and untested items accurately. Do not publish a site or connect live enquiries as part of installation.

Add a Website Generator tab inside Design OS by reusing the WebsiteGenerator component. Preserve existing tabs and support /design-os?view=website-generator on reload. See INSTALL.md for integration details.


Original image generation now defaults on. Include scripts/website-generator/images.py. The image stage uses the configured Codex CLI and connected Higgsfield MCP tools with existing credits. It generates one hero plus one image per service, saves PNGs into the job, validates output, and packages them with IMAGES.json. Missing provider access or incomplete images must fail visibly; never fall back silently to the patio assets. Keep example and text-only modes available.