When a first launch stops, preserve the existing Astro project and reservation. Identify the failed step before trying again. The canonical first-launch guide remains the authority for the full sequence and current recovery details.
Before a site was reserved#
The agent should assess the current session's actual tools and permissions, compile the reusable Astro template, package it, and check source handoff. A product name or successful webpage read does not demonstrate build execution or binary-upload capability.
The guide also includes an anonymous network readiness assessment. It tests JSON POST, authenticated MCP requests, and a bounded binary upload without creating a customer, organization, site, or deployment. Its credential lasts 30 minutes and exposes only assessment tools. The signed receipt covers network operations; it does not prove local builds or source downloads work.
| Failure | Next step |
|---|---|
| Template/dependency download or compiler fails | Resolve that specific build failure before collecting email/reserving a site. |
| Client lacks execution or ZIP/source handoff | Preserve the brief/project and continue in a session with those capabilities. |
| POST or binary upload is blocked | Identify the blocked operation and use the client's supported permission/network path. |
| Assessment expires or receipt is invalid | Repeat the assessment using the same private request key and existing source. |
Installing an MCP plugin does not fix a missing runtime or an unsupported file upload. Do not describe a reader-cache problem as a confirmed platform outage.
After a reservation exists#
Keep the returned organization, site slug, URL, deployment ID, source location, and private resume values. A lost bootstrap response should be retried with the same request key and original normalized email/organization name; do not create another identity.
If upload or finalization failed, follow deployment recovery on the same site. Guest build access permits six deployment starts total and lasts up to 24 hours. Use the returned remaining count. Processing delays alone do not justify consuming another attempt.
If the credential expired, quota is exhausted, or ownership was claimed, preserve the source and finish account setup. Continue with normal authenticated access to the existing site rather than reserving a replacement.
Finish ownership and verification#
Open the agent's Finish account setup link and complete sign-in or email verification. Successful production publication queues setup email asynchronously; bootstrap alone sends no customer setup email. If no message arrives, use the supported setup page or ask support about ownership recovery.
After connecting the agent, verify access with list_organizations and list_sites. Confirm the same reserved site and source project. Then verify important live pages and a substantive chat answer. An API-only answer check does not establish widget layout or controls.
If any step remains unresolved, email jared@answer.cloud with the public site URL, failed step, safe error details, and source availability. Keep tokens, request keys, signed URLs, and private claim links out of the report. See account access.