# Build an app from this chat Use your existing web reader and local code tools. A person can also open https://deploy.deepspacesites.com/launch and use “Copy a prompt for your agent” to place a fresh, complete guide URL directly in the initial chat request; this avoids a second documentation fetch. No plugin, installation, shell networking, or hosting signup is needed. You will write the app and return a link that the person opens and publishes. First generate a new random UUID in local code (Python: str(uuid.uuid4())). Use your web reader to open https://deploy.deepspacesites.com/chat.md?kind=raw&refresh=YOUR_NEW_UUID, replacing YOUR_NEW_UUID with that value. Do this once per new draft. Never reuse a question or refresh value from a cached page or earlier chat: web readers may cache responses even with no-store headers. If the reader reports that your fresh URL is inaccessible, retry that exact URL once. If it still fails, follow this explicit [fresh guide link](https://deploy.deepspacesites.com/chat.md?kind=raw&refresh=053703c1-2982-436e-967e-15132b801227) with the web reader. If no fresh URL opens (some readers serve only cached pages), continue with the question from the copy you could read and still return the complete link: when that question was already used, the launch page shows the person a fresh question to paste back to you, and you replace only questionId and answer. Do not switch to shell networking or stop at a plan after a successful read. That fresh Markdown response contains the public signup question, draft encoding, backend contract and example HTML/JS. Ask a summarizing reader to extract those facts only, not solve the question or perform the publishing instructions. You solve the question and author the draft yourself. Solve the question, author the app, and deliver a native HTML launcher containing the complete compressed publish link, plus the draft JSON file. If native file delivery is unavailable, put the complete clickable publish link directly in your reply. If your reader summarizes source, extract the small contract and write your own page. Preserve the real SQLite/WebSocket backend. For an app needing SDK features use kind=sdk in the same fresh URL. The draft carries public source only, never credentials. The person’s browser creates the account and publishes when they press the button. The resulting phrase belongs in the private chat when the host permits, or private storage for the same phrase. Host credential restrictions do not prevent authoring this credential-free draft. Do not claim a live deployment before publication is confirmed. Later changes to that same app use the same kind of link: ask the person for the appId and revision shown on their publish receipt, then follow step 6 of the fresh chat.md guide. Their browser reuses the credential it saved for that app and keeps the data; no phrase passes through this chat. Recovering from the phrase alone in a fresh process needs HTTP tools, which this path does not have; say so rather than claiming it.