CLI reference

Use the artor CLI to publish prototypes, read feedback, and manage your team’s shared setup. Run commands from your prototype’s folder. If you haven’t installed it yet, follow Installing the CLI.

If you belong to more than one organization or sign in with more than one account, see Organization context and Multiple accounts. Running artor from a coding agent or a script? See Scripting & agents.

Basics

• Help: artor <command> --help (or -h) shows usage without running anything, even offline.
• Names: most commands accept an exact name, an ID, or a unique part of a name. If several things match, Artor asks you to be more specific. link needs an exact ID or slug.
• Confirmations: destructive commands ask first; --yes (-y) skips the question. artor rm --permanent is the exception: you confirm it by retyping the prototype’s name.
• Before it acts, a command prints which organization and account it’s using, for example -> acme · you@x.com · Client work / Checkout redesign.
• Threads and links: refer to a comment thread by its ID or a quoted row number such as "#3", and to a public link by its ID from artor share list (the first four characters are enough if they’re unique).

Version & update checks

A global install updates itself after an interactive command. If an update is required to continue, the CLI updates and retries once; otherwise it asks you to run artor update. See Keeping the skill up to date.

Auth & project

If you name a folder in init that doesn’t exist, Artor suggests close matches and offers to create it. It never creates one silently or files the prototype somewhere you didn’t choose.

Publish & view

Who can delete, restore or rename a prototype is explained in Spaces.

Changelog

Add a short note to each version saying what changed:

artor publish -m "Fixed navigation on mobile"

The note appears beside the version in the dashboard, where owners and admins can edit it later. It can hold text and links, up to 2,000 characters. The Artor skill can draft it from your changes; a note you write yourself always wins.

Review-anchor notes for coding agents

Comment pins stay on the right element when the element has a unique data-testid (why). So your coding agent adds them without being asked, artor init and artor publish keep a short Review anchors (Artor) section in your project’s AGENTS.md (or CLAUDE.md). Artor only ever changes that section, never the rest of the file. It’s written only after a version goes live, so a failed or cancelled publish leaves your files alone, and a problem writing it never blocks a publish.

To skip it once, use --no-agent-notes. To turn it off for the folder, add "agentNotes": false to .artor/project.json; an existing section stays until you delete it.

Reading a crashed version’s logs

artor logs latest
artor logs v3

Shows a running version’s recent output, or the error a version hit while starting. The same logs are under Details > Logs in the dashboard. Crashes after startup aren’t captured. Saved environment values are hidden from logs, but a value your prototype changed before printing may not be, so check logs before sharing them. See Runtime errors.

Public sharing

Create a link that people without an Artor account can open. See Public sharing.

Pointing a link at another version is changed from the dashboard.

Link passwords

artor share add --password                # asks for it, hidden, twice
artor share set <share> --password        # change it
artor share set <share> --remove-password # remove it

Passwords are 8 to 128 characters and are always typed at the prompt (or piped in with --password-stdin), never written on the command line. If your organization requires a password on every public link, you can’t remove one. See Password protection.

Spaces

A Space decides which organization members can open and work on a group of prototypes. See Spaces for who can do what.

Put a Space name with spaces in quotes. Run artor org members to find people’s email addresses.

Folders

Group prototypes into colored folders within a Space. Folders organize; Spaces control access. See Organizing with folders.

Without --space, folder commands use the Organization Space.

Env vars

Set configuration for the organization, a project, or one version. In a linked folder the default is the project. See Environment variables for who can change what.

Mock datasets

Add sample data for the organization, a project, or one version. See Mock datasets for who can change what.

Org skills

Share instructions with your team’s AI tools. See Org skills.

Starter templates

Start from a template with artor init --template <slug>. See Starter templates.

Usage

The same figures are in Settings > Usage. See Usage.

Private registry

Install your organization’s private packages through Artor. See Private registry.

Unlinking a folder

artor unlink removes Artor’s local setup from a folder. It never deletes your code or the prototype on Artor (use artor rm for that).

Every run with a flag, and every run outside an interactive terminal, also removes the link. To remove only the skills or the registry setup and stay linked, run artor unlink with no flags in a terminal and uncheck the link in the list.

Multiple accounts

You can be signed in with several Artor accounts at once, for example a work and a client account. Run artor login once per account.

There’s no account to switch: each folder uses the account that belongs to its organization. If more than one of your accounts could be used, Artor asks once and remembers the answer for that folder, on your machine only. To choose for a single command, add --account <email>.

artor account list                  # which accounts are signed in, and which this folder uses
artor logout --account you@acme.com # sign out one account
artor logout --all                  # sign out all of them

Organization context

When you belong to more than one organization, a command picks one in this order:

1. --org <ref>, if you pass it.
2. The organization the folder is linked to.
3. Otherwise Artor asks, with your default (artor org use) pre-selected. If you only have one organization, it just uses that.

A folder stays with its organization: --org naming a different one is refused. To move a folder, run artor unlink --link-only, then artor link <prototype> --org <ref>.

artor status and artor whoami show which account and organization this folder will use.

Your token

Signing in stores a token on your computer. Treat it like a password. artor logout makes it stop working and removes it; if Artor can’t be reached at that moment, revoke it yourself under Settings > CLI tokens. Signing out also ends any artor open --signed-in sessions it started.

When a command says your token no longer works

• “This account is suspended.” Signing in again won’t help. Contact your organization admin or Artor support. Your login works again once the suspension ends.
• “This account is scheduled for deletion…” Run artor login and sign in with your password, then choose Cancel deletion & sign in. See Changed your mind?.
• “Token invalid or revoked.” Run artor login again.