Remix, rename & delete

There are two different things you can do with an existing prototype, and they’re easy to mix up: keep working on the same project (ship its next version), or fork it into a brand-new project that’s yours.

Pulling and remixing need a publisher seat, access to the source prototype, and the CLI installed.

Remix: fork into a new project

artor remix acme-dashboard                  # prompts for a name
artor remix acme-dashboard my-variant       # name it directly
artor remix acme-dashboard --ref 2          # fork from version 2

Remix creates the folder for you, downloads the source, and creates a new project with you as the owner. The target folder must be empty or not exist yet. The fork is fully independent; publishing in the new folder never touches the original.

On the dashboard you’ll see a “Forked from acme-dashboard v3” line linking back to the exact version you started from. If that version or its prototype is later deleted, the line disappears; your remix keeps working.

Remix from the dashboard

The dashboard gives you the exact command to run, ready to copy:

• Remix latest… in a prototype’s ··· menu (on its card, its list row, or the prototype page) forks whatever the newest version is when the command runs.
• Remix this version… in a version’s ··· menu in the version list forks exactly that version.

Both open the same dialog with two tabs:

• AI agent (the default): a prompt to paste into your coding agent. It names the prototype and version, asks the agent to pick a short name for the new prototype (checking with you if unsure), run the remix, and carry on in the new folder. The agent needs the Artor CLI and skill.
• CLI: the artor remix command to run yourself. It creates the new prototype and a folder with its source; run artor publish in that folder to ship its first version.

Nothing installed yet? Both tabs also offer Copy setup prompt, a prompt for your AI agent that checks for Node 22 or newer (and installs it if needed), installs the CLI and the skill, and signs you in, plus Install guide, which opens Installing the CLI.

The copied command names the prototype by its ID and includes your organization, so it works from any folder, even if you belong to several organizations or the prototype gets renamed. It identifies your organization by its slug when the slug fits the current naming rule (lowercase letters, digits and hyphens only), and by its ID otherwise, so an older organization with an unusual slug still gets a command that’s safe to paste and run.

Remix isn’t offered on a prototype in the trash. People with a reviewer seat see “Remixing needs a publisher seat. Ask an organization admin.” instead of the dialog.

Rename: change the display name

artor rename "New Name"               # owner or org admin only
artor rename acme-dashboard "Acme V2" # owner or org admin only

Rename changes only the display name. The URL and your local folder don’t move. Only the owner or an admin can rename.

Delete & recover

You can delete a prototype in two ways, or delete just one of its versions:

In the dashboard

• Delete… in a prototype’s ··· menu (shown to the people who can delete) opens a dialog that moves it to the trash. Turn on Delete permanently now to delete it for good instead: the dialog lists what goes, and you retype the prototype’s exact name to confirm.
• Deleted prototypes (in the projects toolbar’s ··· menu, also on a right-click on an empty area of the page) opens the trash, which lists deleted prototypes from every Space you can see. Each row has Restore and Delete permanently….
• Delete version… at the bottom of a version’s ··· menu deletes that version after a confirmation that lists what goes with it.

Right-clicking a prototype card or row, a version row, or a trash row opens the same menu as its ··· button. Right-clicking an empty area of a Space or a folder opens the toolbar’s ··· menu, led by New folder at the top of a Space or by the folder’s own actions inside a folder.

From the CLI

artor rm                          # move the linked prototype to the trash (asks to confirm)
artor rm acme-dashboard           # by ID, slug, name, or a unique partial
artor rm acme-dashboard --yes     # skip the question (required without a terminal)
 
artor rm acme-dashboard --permanent                             # retype the name to confirm
artor rm acme-dashboard --permanent --confirm "Acme Dashboard"  # unattended form
 
artor rm acme-dashboard --version 3        # delete only version 3 (asks to confirm)
artor rm acme-dashboard --version 3 --yes  # unattended form
 
artor trash                       # list what's in the trash and how long each has left
artor restore acme-dashboard      # bring it and all its versions back

• --permanent works on a live prototype or one already in the trash. It is confirmed by the prototype’s exact name, never by --yes alone.
• --version takes a version number and can’t be combined with --permanent: a version is always deleted permanently.
• Run artor rm --version <n> from a linked folder with no name given, and the CLI looks up the prototype’s current name first, so the confirmation always names it correctly even if it was renamed since you linked the folder.
• Permanent delete and --version need CLI 0.29.0 or later. Run artor update if your CLI doesn’t recognize them.

Deleting never touches your local folder, only the prototype on Artor. If you publish from a folder still linked to a permanently deleted prototype, the CLI says: “This prototype no longer exists (it may have been permanently deleted). Run artor init to start a new one.”

You cannot publish to a prototype in the trash. Restore it first, so you never pile up versions that can’t serve. After a restore, version numbers continue from the highest one left.

Deleting a version

• Public links pinned to that version stop working right away. Links set to follow the latest version keep working.
• Named links on that version are removed, whether or not it was the latest. The confirmation lists them.
• If latest pointed at it, latest moves to the highest-numbered remaining live version.
• Its comments are deleted with it. The confirmation shows how many threads it has.
• The last live version can’t be deleted. Delete the prototype instead.
• A version that is still publishing can’t be deleted. Wait for it to finish and try again.
• A prototype in the trash has to be restored before you can delete one of its versions.

Who can delete

The same people can move to trash, restore, delete permanently, and delete a version:

• the prototype’s owner, in a Space where they can publish;
• a Space admin, in their Space;
• an org admin, in the Organization Space or any Shared Space, even one they haven’t joined.

In a Personal Space, only its owner can delete, and they can do it even with a reviewer seat. Anyone else sees “Only the prototype’s owner, a space admin, or an org admin can delete it.” Every delete and restore appears in the audit log.

A permanent delete frees storage (files no other version still uses) at the next daily cleanup. A trashed prototype keeps its files until the 30-day window ends.

See also

• CLI reference
• Access control
• Public sharing
• Spaces