Open a pull request, never push to main.
Used by 6 jobs
Clone Code can build, deploy and operate real systems, so it runs every job through the same secure process: verified as you, your connections only, a private sandbox for each job, keys that are never shown again, and controls that stay in your hands.
Loaded only into your own jobs. Each job runs in its own sandbox, torn down afterwards.
Keys are encrypted when you save them and never shown again, not even to you.
Keys go in your Connect page, never into chat. If you try, your clone tells you not to.
Connections belong to you, follow you across your clones and load only into your own jobs.
Each job runs in its own sandbox, separate from every other job, and is torn down when it ends.
Clone's own AI key never enters the sandbox. The sandbox only gets a short-lived token for that job.
Secrets are scrubbed from preview links. Previews and zips are served from a separate domain, not the brand site.
You choose what each connection may do, and you can see what used it. Combine the controls to keep a connection as low-risk as you like.
Open a pull request, never push to main.
Used by 6 jobs
Reports only. Never touch billing.
Used by 2 jobs
Used by 4 jobs
When a website needs a sign-in, you take over and sign in yourself, including any 2-step code or captcha. Clone Code never sees your password. Saved logins are encrypted, and you can forget all of them with one click.
How the browser worksWhere a service offers restricted or scoped keys, give Clone Code only what the job needs.
Let it look first. Switch a connection to Read & write when you're ready for it to make changes.
Add notes like “open a pull request, never push to main” to set the ground rules for a connection.
Clone Code connects from a fixed outbound IP, shown on the connection form, so you can keep allowlists tight.
Only your own jobs. Every request is verified with the Clone platform as you before your connections are used, and connections are tied to your verified email.
Encrypted with Google Cloud KMS. They're never shown again after you save them, and they're loaded only into your own jobs.
No, never. Use the Connect page instead. If you try, your clone will tell you not to.
Each job runs in its own isolated sandbox that is torn down afterwards. Clone's own AI key never enters the sandbox; it only gets a short-lived job token.
Secrets are scrubbed from preview links, and previews and zips are served from a separate domain, not the Clone brand site.
No. When a site needs a sign-in, you take over and sign in yourself. Saved logins are encrypted, and you can forget all of them with one click.
Make it Read-only, keep payments in Test mode, add notes like “never touch billing”, and use restricted or least-privilege keys where the service offers them. Each job also has a spending cap.
Yes. Each connection shows which jobs used it, and you can remove any connection at any time.
Start a free trial and connect your first system read-only, or book a demo and we'll walk through the secure process with you.
Tell us a little about yourself and we'll set up a time to walk you through Clone.