Create & connect
Build: create, revise, and publish a web app
Build browser-based HTML, CSS, and JavaScript apps, manage versions, preview changes, and publish or export your project.
Before you start
Section titled “Before you start”Build creates interactive apps that run in a web browser using HTML, CSS, and JavaScript. It is for web pages and browser experiences—not arbitrary backend services, full-stack applications with server infrastructure, or native mobile apps. Start a Build thread from the initial workspace panel by choosing Build, or switch to Build when starting in Chat.
Build answers create project versions on the conversation tree. The Your app panel shows a preview and project code for a selected version. A version can be generated, manually edited, or published; these are separate actions.
When to use this
Section titled “When to use this”Use Build for a landing page, interactive calculator, simple browser game, dashboard mockup, or prototype you can share as a website. Use Ask to discuss the project without changing its code. Use Build when you want the model to implement a requested change.
- Start a workspace and choose Build. Describe the app, its audience, main task, and visual direction. Turn on Ask me a few questions first to define the app if you want to clarify requirements before building.
- Answer the model’s questions. Review the resulting Spec. Choose Adjust to refine it, Decide for me to fill gaps with sensible choices, or Build to create the app. If you do not need a discovery exchange, use Build now when offered.
- Open Your app and use Preview. Test Mobile, Tablet, and Desktop, and use Reload to refresh the preview. The preview runs in an isolated browser frame; it does not provide your project with a server backend.
- Ask for changes in a Build node, such as “Add a clear reset button and show a confirmation before clearing the form.” Each successful Build answer creates another version. Branch from a version to try a different direction without losing the earlier one.
- Use Ask to discuss the project without changing code. Use Build for implementation. In the preview, Edit text and images allows direct text or image edits without model credits; Edit with AI lets you select an element and describe a change.
- Open Code to inspect or edit project files. Manual edits appear in the preview; choose Save version to record them as a new version, or Discard to drop unsaved changes. Use Console and Fix if the preview reports errors.
- To publish, click Publish, verify your email if asked, choose an available address and review the title and sharing options. Publish only when you are ready for the site to be reachable at that address.
- To update the public code, select the desired version and choose Publish this version. Save changes saves site details such as its title, address, description, and sharing options; it does not publish a different project version. A newly generated or manually saved version does not automatically update the public site. Use Unpublish to take the site offline.
Worked example
Section titled “Worked example”Build a “Workshop budget planner” with fields for attendees, venue cost, and materials per person. Ask for a total estimate and a per-person amount, with a reset button. Start by asking questions to settle currency, audience, and validation rules; review the spec; then build. Test the layout in Mobile and Desktop, try a second branch with a simpler layout, and publish the version you have checked.
What happens next
Section titled “What happens next”Share the published site address. The published page and the working project are distinct: later Build answers and manual edits create or save versions, but publishing is what changes the live site. On paid plans, Download offers a single HTML file or project ZIP, and GitHub can export the project when a GitHub connection with the needed tools is available. A permitted published project can be remixed by another user into their own workspace.
Cost and limitations
Section titled “Cost and limitations”Model generations can spend credits; inspect the selected model and length before sending. Direct text/image edits in the preview use no credits. Stopping a generation keeps the partial text, but a stopped Build answer does not save a new project version. Publishing requires a verified email. Free sites show the Neurothread bar, allow remixing, and stay out of search engines. Paid plans provide options to hide the bar, disable remixing, and allow indexing; downloading and GitHub export are paid features. Plan limits, site counts, and current availability can change; see neurothread.ai/pricing. A preview or saved version is not automatically public, and a published site may be reviewed before display.
Troubleshooting
Section titled “Troubleshooting”- The preview is blank: wait for the first project files, check that the project has an
index.html, and use Reload. - A request discusses the app but does not change it: select Build, not Ask.
- A manual edit is not included in the conversation: choose Save version; unsaved edits are only a preview draft.
- The live site shows an older version: open the intended version and select Publish this version. Save changes updates site details, not the code being served. Saving or generating a version alone does not publish it.
- Publishing is blocked: verify your email, choose an available address, and check your plan’s publication limit.
- GitHub export fails: connect GitHub in Settings → Connected apps and ensure the connection offers the required repository and file tools.
- The project needs a backend or native feature: Build is a browser-only HTML/CSS/JavaScript environment. Use a separate service or development platform for server-side and native functionality.