After the first launch, finish account setup so future work uses your normal Answer Cloud account. The temporary build credential used for launch is limited to that one reservation and is not a permanent account connection.
If you accepted an invitation to someone else's workspace, use Start developing after accepting an invitation instead. You can work on the invited site without claiming a new one.
Accept ownership of the launched site#
- Open the Finish account setup link your agent returned, or use the account-setup email sent after successful production publication.
- Complete sign-in or email verification in your browser. Use the account email supplied during launch.
- Return to your website's setup page and complete the ownership handoff for that existing site.
- Sign in at app.answer.cloud and confirm that you can find the site and its public address.
Do not send passwords, verification codes, or the private emailed claim link to your agent. The conversation-safe setup link leads into the ownership check; possession of that link alone does not grant ownership.
Email sending is asynchronous and may retry. If the site is live but the email is missing, check the mailbox and spam folder and use the saved continuation link. If ownership cannot be completed, contact support with the public URL and account email through a private channel. Creating another site does not recover the original one.
Connect Answer Cloud to your AI assistant#
Open MCP setup and follow the instructions for your AI assistant. Installing the Answer Cloud plugin or adding its MCP connection lets your assistant work with your website. Complete browser sign-in with the account you used for setup. The assistant setup guides explain the available options.
An existing connection can be reused when it has access to the correct organization. Completing account setup revokes temporary build access, so you may need to reconnect even if the first website was published successfully.
Ask for your next change#
Tell AI what you want changed and include the website's public address. For example:
Help me update my existing website at [website URL]. Confirm the right site in Answer Cloud, update the homepage opening sentence to the wording below, and show me a preview before publishing.
Your assistant should find the existing website, prepare the change, and handle the technical work. If it needs project files or another permission, it should explain what is missing. Do not start another site to continue this one.
Review the result, then tell the assistant when and where to publish. After publication, open the public page and check the exact change. The hosted agent workflow provides more detail for ongoing work.
Keep the project for future edits#
For design, layout, or code changes, your coding agent needs the editable project that produced the website. MCP provides account access; it does not automatically provide those files. Keep the project or repository from your first session, and ask the agent to help preserve a clean source archive if the environment is temporary.
For developers, retain src/, public assets, package.json, the lockfile, Astro configuration, and project instructions. A deployment ZIP containing only built files is not the full editable project. Record the site identity and build instructions without recording credentials.