Direct answer
Clone website is a human UI workflow that creates a new HTML app artifact from one webpage URL. The result is editable and versioned but is not synchronized with the source website.
Preconditions
Confirm the destination workspace, create permission, accepted source URL, room under the team's artifact limit, and a plan that includes the import. A workspace is an access-controlled area inside a team. Do not infer that possession of a URL grants access to protected source content.
Human action required
Instruct the human to open New → Clone website, enter the URL, select the destination workspace when prompted, start the import, and inspect the generated app. Verify success by opening the new artifact and checking its rendered page and files.
Quota invariant
Free teams receive five successful imports total across both methods. It is one combined allowance, not five of each. Artifact capacity and import allowance are separate. A quota refusal should open or relay the upgrade path, not trigger retries. Deleting an imported artifact does not restore an already consumed import.
Canonical plan references: Plans and usage and Limits and quotas.
Result and boundaries
- Output: a new app artifact backed by generated HTML, with its own URL and History.
- No synchronization: later source-site changes do not update the artifact.
- Protected, blocked, unsupported, or runtime-dependent content may be incomplete.
- Re-importing creates another artifact rather than updating the first.
- No separate public CLI import-from-URL syntax is established here; do not invent one.
Failure handling
Retry after correcting an invalid URL or a transient generation failure. Do not retry access or quota refusals; relay the required human action. For blocked resources, ask the human for an authorized source or use folder/ZIP import. Escalate repeated generation failures through Troubleshooting.
Related: Artifact types · Publish