# Clone a Website

> Fire ultron-capture: spider the site, deploy a branded clone, surface the URL when ready.

- **Kind**: Shell tool
- **Category**: engineering
- **Owner**: Sentinel (/sentinel)
- **Default model**: sonnet
- **Cost class**: standard (Sonnet-class model. Default for most skills.)
- **Turn budget**: 2
- **Execution**: background (returns immediately, surfaces result via bg_trigger)
- **Canonical URL**: https://app.51ultron.com/docs/skills/clone-website

## What it does

Long-running async clone via the ultron-capture pipeline. Call the start_site_capture chat tool with the URL. It returns IMMEDIATELY with a job_id — the user sees the job in the Background Jobs panel. Simple sites finish in ~30s, full SPAs (Apple-scale) take up to 40 min. When done, bg_trigger fires and you'll resume the conversation with the branded deploy URL (<slug>.clones.51ultron.com) and the slug. From there: if the user wants to edit, shell_exec wget the deployed site into /work/<slug>/ and use the edit-html-clone skill for surgical edits, then ultron-deploy to ship the modified version. END THE TURN immediately after calling start_site_capture — do NOT poll, do NOT loop, do NOT use the in-container ultron-clone (that's the broken v1 that misses SPA content).

## When to use this

- user wants to clone an existing website
- user says 'rebrand <url>' / 'make a copy of stripe.com' / 'mirror linear.app'
- user wants to swap copy on a competitor's landing and ship a variant
- user wants the site as a starting point for edits + deploy to Pages

## When NOT to use this

- user wants to scaffold a NEW web app from scratch → use spin-up-web-app
- user wants to scrape data only (no rebuild/deploy) → use scrape_website
- user wants only a screenshot of a page → run ultron-screenshot via shell_exec

## Example prompts

- `clone https://linear.app and rebrand it for our launch`
- `make a copy of stripe.com landing page`
- `mirror flora.ai so I can edit the copy`
- `rebrand vercel.com with our colors and ship to Pages`

## Inputs

- **url**: the URL to capture
- **branch**: optional kebab-case branch name for the Pages deploy

## Output

job_id (visible in Background Jobs panel). Branded URL surfaces via bg_trigger when capture completes (30s–40min depending on site size).

## Tools used

`start_site_capture`

## Execution template

Shell tools dispatch through `start_site_capture` with the following command template:

```bash
call start_site_capture({{url}}, {{branch}}) and END THE TURN. bg_trigger will resume when the capture is done.
```

## Tags

`engineering`, `clone`, `deploy`, `async`, `background`

## Keywords

clone, rebrand, mirror, copy site, landing page, site capture, ultron-capture