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.
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 the agent you use#
Follow Connect Claude Code or Connect Codex. Existing authenticated connections can be reused when they have access to the correct organization.
Ask the agent to list your organizations and the selected organization's sites. It should confirm the original reserved slug and live URL before editing. Completing account setup revokes temporary build access, so a new OAuth connection may be necessary even if the first website was published successfully.
Keep the editable project#
Retain src/, public assets, package.json, the lockfile, Astro configuration, and project instructions. Your agent should record the public URL, site slug, organization ID, and build commands without recording credentials.
If the original environment was temporary, download the clean source archive before it disappears. A deployment ZIP containing only built files is not the full editable project.
Make a small first edit#
Use a concrete request such as:
Continue the existing website using this Astro project. Confirm its Answer Cloud organization and site, update the homepage opening sentence to the wording below, and show me the local result before publishing.
After review, specify whether to publish to staging or production if that choice is still unresolved. Have the agent inspect the completed deployment and open the public page to verify the exact change. The hosted agent workflow covers subsequent updates.