Clone Code: give your clone a software engineer
Ask your clone to build a website, app, script or tool. Clone Code writes, runs and tests real code, then sends you a live preview and the files.

Clone Code gives every clone a software engineer. Ask for a landing page, a calculator, a dashboard, a data clean-up script or a small internal tool, in plain English, right in chat. A coding agent plans the work, writes the code, runs it and tests it in its own private sandbox, and your clone sends you back a summary, a live preview link and a download of every file.
No code editor, no hosting account, no setup.
What you can build
Clone Code is a good fit for anything that is, in the end, code:
| Kind of thing | Examples |
|---|---|
| Websites and landing pages | A bakery's one-page site, an event landing page, a product launch page |
| Web apps and tools | A tip calculator, an ROI calculator, a lead quiz, an invoice generator |
| Dashboards | A sales dashboard from a CSV, a KPI tracker |
| Scripts and data work | Clean up a messy spreadsheet, merge two exports, convert file formats |
| Automations and prototypes | A blueprint and working script for lead enrichment, an API prototype |
| Small games and demos | A browser game for an event, an interactive product demo |
| Email and content kits | An HTML email template set, a reusable signature block |
It's not for explaining code or short snippets. Your clone answers those directly without starting a job.
How it works
- You ask. Describe what you want, with as much detail as you have: content, style, colors, features, who it's for.
- Your clone hands the job to Clone Code, including everything relevant from your conversation, and tells you it's started.
- Clone Code builds it in a fresh, private sandbox: it plans the project, writes the code, runs it, tests it and fixes what breaks.
- Your clone sends the result as a new message:
- a summary of what was built and how to use it
- a live preview link for websites and web apps
- a download link with all the project files as a zip
Then you keep going. "Make the header navy." "Add a contact form." "Turn the table into a chart." Each follow-up continues the same project.
Asking well
Clone Code does its best work with a clear brief. You don't need technical language; you need specifics.
A strong first request
"Build a one-page website for Driftwood Coffee, a small coffee shop by the beach. Warm, sandy colors and a relaxed feel. Sections: hero with our tagline 'Slow mornings, good coffee', a menu with prices, opening hours, a photo gallery placeholder, and a map link. Mobile-friendly."
What makes it work:
- Who it's for and what it's for (a beach coffee shop's website)
- Look and feel (warm, sandy, relaxed)
- Exact content in quotes (the tagline)
- The parts you want (sections listed)
- Constraints (mobile-friendly)
Attaching files
Share links to the files you want used: a logo, product photos, a spreadsheet, a brand guide. Say what each one is for: "use this as the logo", "build the dashboard from this CSV".
Follow-ups
Describe only the change: "make the buttons rounder and add a dark mode toggle." Clone Code already has the project.
Starting fresh
Clone Code continues your chat's project by default. To start over on something new in the same chat, say so: "start a new project: …"
Example prompts to try
- "Build a mortgage calculator web app with a payment breakdown chart. Clean, modern, blue accents."
- "Make an ROI calculator for our sales team: inputs for team size, hours saved per week and hourly cost; show annual savings in big numbers."
- "Here's a CSV of last quarter's deals. Build a dashboard with revenue by month, win rate by rep and the top 10 accounts."
- "Write a script that takes this messy contact export, fixes capitalization, removes duplicates by email and outputs a clean CSV."
- "Create a five-question quiz for our website that recommends one of our three plans at the end."
- "Build a landing page for our Spring Summit on April 12: agenda, speakers, a registration button and a countdown timer."
- "Make an invoice generator: I fill in client, items and rates, it produces a printable invoice with our logo."
More ideas are in the sample prompts library and the use case library.
What you get back
The summary
A plain-English explanation of what was built, how it's organized, and how to use or change it. If Clone Code made assumptions (a placeholder image, sample data), it tells you.
The live preview
Websites and web apps get a link you can open on any device and share with your team for feedback. Previews are for reviewing. When you're ready to publish, use the files.
The files
Every job includes a zip of the whole project. Open it, hand it to a developer, upload it to your web host, or keep iterating with Clone Code.
How long things last
- Projects stay available for follow-ups for 7 days in the same chat.
- Preview and download links last 30 days. Download anything you want to keep.
A worked example: from idea to live page in one chat
Here's how a typical Clone Code conversation goes.
1. The first ask
"Build a landing page for our Spring Summit on April 12 in Austin. Sections: hero with the date and a Register button, agenda (morning keynotes, afternoon workshops, evening reception), three speaker cards with placeholder photos, a FAQ, and a footer with our logo. Navy and coral, modern, mobile-friendly. Logo: [link]."
Your clone replies that the job has started. About eight minutes later, a new message arrives with a summary ("a single-page site with five sections; the speaker photos are placeholders; the Register button links to # until you give me a URL"), a live preview link, and a zip.
2. Review on your phone and share it
You open the preview, scroll through on your phone, and forward the link to your events lead.
3. Follow-ups, in the same chat
"Make the hero full-height with a subtle gradient. Add a countdown to April 12. Register should go to https://example.com/register. Swap the FAQ for an accordion."
A few minutes later: an updated preview and a new zip. Clone Code changed only what you asked for and kept everything else.
4. Hand-off
You download the final zip and upload it to your web host, or hand it to whoever manages your site. Done in a lunch break, without opening a code editor.
Getting better results
- Give real content when you have it. Real headlines, prices and copy beat placeholders and make the first version much closer to final.
- Name a reference. "Layout like a modern SaaS pricing page" or "feels like a printed menu" gives Clone Code a clear target.
- Say who will use it. "For our sales reps on their phones" and "for executives on a big screen" lead to different designs.
- Ask for explanations. "Explain how to change the prices myself" gets you a short guide in the summary.
- Ask for tests on logic-heavy tools. For calculators and scripts, ask Clone Code to show a few example inputs and outputs so you can check the math.
- Keep your data clean. For dashboards and scripts, share a sample file that looks like the real thing, including the messy bits.
How a job runs, behind the scenes
You don't need to know any of this to use Clone Code, but it explains why it behaves the way it does:
- A fresh, private workspace is created for your chat's project. Nothing from other users' projects is in it, and nothing from yours leaks out.
- The coding agent plans the work, writes the files, installs what it needs, runs the code and checks the result, fixing errors as it goes.
- The project is saved so your follow-ups continue from exactly where it left off, for 7 days.
- The preview and the zip are published to private links, and your clone sends them to you.
Because the agent actually runs what it writes, you get working software, not just code that looks right.
Good to know
- One task at a time per chat. If a job is still running, wait for its result before asking for the next change. Your clone will tell you if one is in progress.
- The sandbox is private and separate. Clone Code can't reach your computer or your accounts. It can use public information and public code repositories as a starting point.
- Usage is billed to your plan like other skills, based on how much work the job takes. Bigger builds use more.
- Each job has a time and spending safety limit, so a runaway job can't run forever.
Turning it on
Clone Code is a skill. If your clone doesn't have it yet:
- Ask your clone: "Turn on the Clone Code skill."
- Or go to Skills → + Add, search for Clone Code and enable it for the clone you want.
See Connect your accounts and turn on skills for how skills work.
Clone Code and the rest of your team
Clone Code is most useful when it's part of a bigger job your clone is doing:
- Your marketing clone researches a launch with Research Operator, makes the hero images with Image Operator, and builds the landing page with Clone Code.
- Your ops clone notices the same spreadsheet chore every week and builds a script to do it.
- Your sales clone builds a custom ROI calculator for a big prospect before the call.
Common questions
Do I need to know how to code? No. Describe what you want in plain language. If you do know how to code, you can be as technical as you like.
Can it change something it built yesterday? Yes, in the same chat, for 7 days. Just describe the change.
Can it work on my existing website or code? Share the files (or a link to a public repository) and describe the change. Clone Code works on a copy in its sandbox and sends back the updated files.
Can it connect to my accounts or databases? Not today. Clone Code works in a private sandbox with what you give it. Share exports or files instead.
It's been a while and nothing came back. Big builds can take longer than 15 minutes. If you've heard nothing after an hour, ask your clone for the status, or open a support case.
Where's the preview link? It stopped working. Links last 30 days. Ask your clone to rebuild it from the project if it's still within 7 days, or start from the zip you downloaded.
Was this helpful?
Thanks. That helps us make this better.