changelog

every release, in one place.

October 4, 2026
fix
A retried publish never makes a second version
When the connection dropped while Artor was finishing a publish, the version could go live while the CLI reported a failure, and publishing again created a second copy of the same build. With artor-cli 0.35.0 or later, a retried publish never creates a second version (check with artor --version).
- One run, one publish: each artor publish run tags its final step with its own key. When the version already went live for that key, Artor answers with that version instead of publishing another one, and the CLI prints its link as usual. If a newer version was published after the lost attempt, the link printed is the replayed version's own numbered link, not the newer one.
- A lost reply is retried, not reported as a failure: when the connection drops, the reply is cut short, or a proxy answers with an error page, the CLI asks again with the same key, up to 2 more times. An error Artor answered directly is final and isn't retried.
- It waits when Artor asks it to: while the first attempt is still being processed, or while your organization's publish slot is busy or a short rate limit applies, the CLI waits and asks again, for up to about 5 minutes in total. A rate limit that would take longer (for example, your organization has used up its publishes for now) stops the publish at once with Artor's message.
- Honest messages when the outcome is unclear: after a lost attempt, any failure says the version may already be live and asks you to check the prototype's versions in the dashboard before publishing again. When the earlier version was changed or deleted in the meantime, the CLI says so and republishes nothing.
- No automatic update after a lost attempt: if Artor asks for a newer CLI at that point, the CLI no longer updates itself and re-runs the publish, which could create a second version. It prints the warning and asks you to run artor update.
- Ctrl-C warns when it matters: stopping the CLI while Artor is finishing the publish, or after an attempt lost its reply, prints the same warning before exiting.
- --json adds replayed: true when the version came from an earlier attempt of the same run.
- Retries only happen against an Artor server that supports them, so an older server never gets a retry that could publish twice.
If the server crashes in the middle of a publish, just publish again: the new publish works. The crashed attempt can be left behind as a version stuck in progress (never served) until automatic cleanup lands.

See If the connection drops during a publish.
October 3, 2026
improvement
Registry list tells scripts whether the proxy is available
artor registry list --json now tells a script whether artor registry login will write anything, which until now only the human output said. This requires artor-cli 0.34.2 or later (check with artor --version).
- Each row carries proxyAvailable: true when Artor can serve that package scope, false when the organization's registry proxy is off or its plan doesn't include it (so registry login writes nothing), and null from an older Artor server that doesn't report it. The result is still a bare array, so existing scripts keep working.
- The "proxy is not available" note goes to the error output under --json, so the JSON stays one clean result.
- An empty list warns too: with no sources connected, registry list still says when the proxy isn't available, instead of only saying there are no sources. With --json, an empty list is [].
See Private registry and Scripting & agents.
October 2, 2026
improvement
Comments inside dialogs and tabs
A comment left inside a dialog, popover, collapsible section, tab or menu now says where it lives once that container is closed: "Inside the 'Confirm plan' dialog". When the prototype ties the opening control to it, an Open it button presses that control for you, scrolls the page to the comment and shows its pin. It's offered on your team's comments, and on a guest's own comments when that guest is the one looking.

Comment mode now leaves the prototype alone: with the comment tool on, a click places a comment and never fires the button or link underneath, and the cursor stays the comment pin over buttons and links. Hold Option on a Mac, or Ctrl on Windows and Linux, to use the page without leaving comment mode.

artor publish now keeps the review widget up to date by itself. When your project declares @artorapp/web-sdk as "latest" (what artor init writes), every publish that builds installs the newest widget first, with no prompt, in CI too. artor publish --json reports what it did as webSdk.

Fixes and improvements:
- Quoted-text highlights no longer cover the page, so you can still click what's underneath.
- A teammate opening a shared link while signed in sees a plain page, then a Continue button, instead of a blank screen while Artor checks who they are.
- Dragging the review toolbar no longer swallows your next click on it.
Run artor update to get CLI 0.32.0; your next publish then updates the widget. Static HTML prototypes get it automatically. See Comments.
October 2, 2026
improvement
One setting for who can comment on a shared link
Public links now have one commenting setting, Comments on this link, instead of separate switches for your team and for visitors. New links start from your organization's default.
- Five choices: Off (nobody), Members (signed-in members of your organization), Anyone (visitors too, no name needed), Name (visitors after typing a name) and Name and email.
- Off now stops everyone. Before, turning team comments off left guest comments open on a link that allowed them. Links already set that way now stop visitors too; none were live when this shipped.
- From the CLI: artor share add --comments and artor share set --comments take off, members, anyone, name or name-email. Run artor update to get CLI 0.33.0 or newer.
See Comments on a shared link.
October 2, 2026
feature
Profile pictures in the review widget
The review widget now shows your teammates' profile pictures instead of initials.
- Everywhere in the widget: on comment pins, in the thread list, next to each message and in the @mention list.
- Through shared links too: signed-in teammates who open a public link see pictures, including teammates who can't open that prototype's space.
- Guests see initials: visitors without an account, public viewers and anyone viewing a link as a guest see initials only, and no picture is ever sent to them.
- Fast and private: pictures come from the prototype's own preview address, so no dashboard link or account detail reaches the prototype's code. Your browser keeps each picture after the first load.
- No setup: upload a picture in Settings > Account and it appears in the widget within seconds. A picture that can't load is tried once more, then shows initials.
See Comments.
October 2, 2026
improvement
Publish a Next.js app from a monorepo
A Next.js app inside a pnpm, npm, Yarn or Bun workspace now publishes with plain artor publish from its own folder, with or without Turborepo. This requires artor-cli 0.34.0 or later (check with artor --version).
- No extra flags for the usual layouts: cd apps/web && artor publish builds and ships the app. The manual recipe (copying assets by hand, then --no-build --no-install --node --dir .next/standalone --entry apps/web/server.js) still works but is no longer needed.
- Finds the server where Next puts it: in a monorepo the standalone server sits under .next/standalone/<app path>/. Artor checks the usual spots, reads outputFileTracingRoot from next.config when it's written plainly, tries the path implied by your workspace, and otherwise searches the standalone folder for exactly one server.
- CSS, JS and public files land next to the server, so the published page loads with its styles and scripts.
- Installs at the workspace root: when your app's folder has no lockfile of its own and the workspace lists it, missing dependencies install at the workspace root with the workspace's package manager (its lockfile, then its packageManager field, then pnpm for a pnpm-workspace.yaml), and the app builds with that same manager. Otherwise the install runs in the app's own folder. Before, publish ran npm install in the app folder, which failed on workspace:* dependencies.
- Workspace membership: Artor reads pnpm's pnpm-workspace.yaml globs and npm-style workspaces (used for Yarn and Bun too), excludes included. A workspace file it can't read counts your app as listed, and a few pnpm edge cases differ between pnpm versions.
- Fewer needless reinstalls: an npm, Yarn or Bun workspace app whose dependencies are already installed (hoisted ones included) no longer reinstalls on every publish (Yarn Plug'n'Play excepted).
- --no-install names the folder: when dependencies are missing, the message tells you which folder to run the install in: the workspace root for a listed app with no lockfile of its own, otherwise the app folder.
- Clearer errors: when no server is found, the message lists every path Artor checked; two possible servers are both named; a search that had to stop early says so. These messages suggest setting outputFileTracingRoot or publishing the server yourself with --node. A symlinked server, .next, .next/static or public folder is refused with the reason: replace the symlink with a real file or folder.
- --entry is checked before packaging or building where supported: with --node and other node-server framework overrides, it must be a relative .js, .mjs or .cjs path, start with a letter or digit, use only letters, digits, ., _, - and /, and contain no .. path segment. Next's automatic publishing path ignores --entry.
- No home-folder surprises: without a Git repository above your app, a stray package.json or lockfile in your home folder no longer turns every project under it into a workspace member. This applies to the review widget's auto-update too, whose message now says whether to update from the workspace root or from the app's own folder.
- Native modules: native modules such as sharp are not swapped for their Linux builds in a monorepo app; publish prints a warning when the bundle carries sharp. Publish from a Linux machine or CI if sharp must work in the published app.
See Monorepos.
October 1, 2026
feature
Members open shared links as themselves
When you're signed in to Artor and open a public link from your organization, Artor now recognizes you automatically. If you can open the prototype's Space, you get the team view: every thread, and you comment as yourself instead of as a guest.

Members who can't open the Space still see the prototype as a visitor does, but the review widget now shows them every thread on that version and they comment as themselves. This doesn't apply to a prototype in a Personal Space, where everyone but its owner keeps the visitor's view. Admins can turn this off under Settings > Sharing.

Want to see what an outside visitor sees? Add ?artor-as=guest to the link, and ?artor-as=member to switch back.

See Teammates on a shared link.
October 1, 2026
improvement
The review widget stays with the page
Comment pins now stay on their element when you scroll a panel inside the page, and when the layout moves under them, like an accordion opening above. You can scroll while you write a comment without losing what you've typed, and the Comment button on selected text follows the selection, on a paused page too. Menus, the mention picker and the toolbar stay on screen when you pinch-zoom or the keyboard opens.

Fixes and improvements:
- Version labels read V4 everywhere, including the review widget and the CLI (artor update).
- Space icons are easier to read on their color.
- Comments beside a Home prototype render at normal weight.
- An empty Space filter on Home no longer repeats the Space's name.
To get the new widget, update it with npm i @artorapp/web-sdk@latest and publish again. Static HTML prototypes get it automatically. See Comments.
September 28, 2026
improvement
A welcome for everyone who joins
Everyone who joins an organization now gets a short welcome, including people invited as admins. Publishers also get a setup prompt to copy into their AI agent, which checks for Node, installs the CLI and the skill, and signs them in.

See Your first sign-in.
September 28, 2026
improvement
Comments update on their own
New comments, replies, resolves and deletes now show up without a reload, both in the prototype and on its dashboard page. Artor checks every 5 seconds while you're looking at the tab, and waits while it's in the background.

Each comment card on the dashboard also has a ··· menu (or right-click) to open the thread, open it in the prototype, copy a link, mark it read, resolve it, exclude it from AI, or delete it.

See New comments appear on their own.
September 28, 2026
feature
Customize your spaces
Give each space an icon, an emoji, a color or an image, so you can tell them apart at a glance. Choose Customize space in the space's ··· menu.
- Right-click a space card, a space in the sidebar, or an empty part of the page for the same actions as its menu.
- Sorting and Public only moved into a Filters submenu in the toolbar's ··· menu.
- Filter the Spaces page by name. Press / to jump to the filter.
- From the terminal: artor space color <space> <color>.
See Spaces.
September 28, 2026
feature
Delete prototypes and versions
A prototype you delete goes to the trash, where you can restore it for 30 days. To remove it for good right away, choose Delete permanently and retype its name.

You can also delete a single version. A version delete is always permanent. Any public link pinned to that version is turned off first, and latest moves to the newest version that's left.
- In a personal space, only its owner can delete. In any other space, an organization admin or that space's admin can.
- From the terminal: artor rm --permanent, artor rm <prototype> --version <n> and artor folder clear.
Update with artor update. See Remix, rename & delete.
September 28, 2026
improvement
Remix from the dashboard
Remix latest in a prototype's ··· menu, and Remix this version in a version's menu, give you a ready-to-copy way to fork it: a prompt for your AI agent, or the artor remix command to run yourself.

See Remix from the dashboard.
September 26, 2026
fix
Clearer messages for suspended accounts
When an account is suspended or scheduled for deletion, the CLI now says so and tells you what to do, instead of a generic "Token invalid". See When a command says your token no longer works.
September 26, 2026
improvement
Clearer settings pages and tab titles
Settings pages now show "Settings > Section" in the heading, browser tabs start with Artor, and a few sidebar labels are simpler (General, Environment, Sharing).
September 26, 2026
feature
Multi-account CLI login
artor login can now keep several accounts signed in on the same machine. Each project folder uses the right account automatically, asking once when more than one fits.
- artor account list shows every login and checks it still works.
- artor logout now revokes the token on the server.
- Every command shows which org and account it acts as.
Update with artor update. See Multiple accounts.
September 26, 2026
feature
AI agents can now preview your published prototype for debugging, via the CLI
artor open --signed-in creates a one-time link that signs the browser in, so an agent (or a fresh machine, or CI) can open a members-only preview right after publishing. The link must be opened within 60 seconds and the session lasts one hour. Add --json to get the link instead of opening a browser.

Update with artor update. See Signed-in links from the CLI.
September 26, 2026
improvement
No more pushing unnecessary files: .gitignore is honored, plus a new .artorignore
The source saved with every publish now skips whatever your .gitignore files skip. A new .artorignore (same syntax) lets you exclude more, or bring a file back with a ! line. Secrets like .env* are always left out. The saved source limit is now 50 MB compressed, and artor publish --list-source shows exactly what would be saved.

Update with artor update. See What goes into the saved source.
September 26, 2026
improvement
Improvements on static prototype sizes
Static build limits now follow your plan: 50 MB on Starter, 100 MB on Pro, 200 MB on Team and Enterprise. When a build is too big, the error tells you the one step your organization can take.

See What each plan includes.
September 26, 2026
improvement
Usage bars in the CLI
artor publish and artor usage now show usage bars, so you see how close you are to your plan's limits. artor usage also lists your build size limits.
September 19, 2026
feature
protect your public share links with a password
A public link can now ask for a password. Switch on Require a password when you create the link, or add one later from Edit, and anyone who opens it has to enter the password before they see the prototype. It is available on every plan.

A public link works for anyone who has it, and links travel: they get forwarded, pasted into a channel, left in an old email thread. A password keeps the prototype with the people you meant to show it to. It is useful when:
- The work is confidential. Client projects under NDA, an unreleased feature, a pitch you are not ready to make public.
- You are running user tests. Give each round of participants the link and a password, then change the password when the round ends. Turn on guest commenting and they can leave feedback without an account.
- The link goes somewhere you don't control. A client's shared inbox, a big group chat, a ticket that many people can read. Send the link there and the password somewhere else.
- You want to end access without breaking the link. Change the password and everyone has to ask you again, while the URL in your deck or doc stays the same.
Type your own, or press Generate for three short words that are easy to read out on a call. Copy it before you save: once saved, the password can't be shown again, only changed or removed. From the terminal:
```
artor share add --password
artor share set <share> --password
artor share set <share> --remove-password
```
Good to know:
- Changing the password locks the link again. Visitors who already got in need the new one.
- Members skip it. On the password page, Sign in takes a member of your organization straight to the prototype, as long as they can see its Space.
- Wrong guesses are limited. After too many, the page asks the visitor to wait a few minutes.
- Admins can require a password on every public link in Settings → Sharing. Links without one stop opening until a password is added, and the same link works again as soon as it is.
- Password changes show up in the audit log. The password itself never does.
Also in this release:
- Hide the review widget when you create a link. The create dialog has a Show the review widget switch for signed-in members, and the CLI has artor share add --hide-widget.
- A tidier public links table. One line per link, an Access column that shows its password and guest-commenting mode at a glance, a copy button that is always there, the exact expiry date on hover, and a Show disabled switch instead of two tabs. Right-click a row for its actions.
September 19, 2026
fix
prototype links open in the right organization
A link to a prototype, from a comment email or pasted into chat, now opens it even when you're working in another of your organizations. Artor switches you to the organization that holds the prototype, as long as you're a member. Before, the page said "Project not found", or kept loading when no organization was selected. It also works when the organization you had open was deleted or you were removed from it.

When a prototype really can't be opened, because it was deleted, sits in a Space you can't access, or belongs to an organization you're not in, the page now says Prototype not found with a Go to Spaces button, instead of leaving you stuck.

Good to know: your current organization is shared by every tab in your browser, so two tabs on prototypes from different organizations switch it back and forth, and the tab you're looking at wins. See Opening a prototype link.
September 19, 2026
improvement
an easier comment feed, on any screen
The comment feed on a prototype's dashboard page is easier to scan. Each thread is a card, and an unread thread has an orange dot on the author's avatar. Every version in the list shows its comment count and how many are new, like "3 comments · 1 new".

The filters fit on one row: the status select, Mark all read, and a ··· menu where you switch between This version and All versions.

On a phone, the version list folds into a single card that opens the full list, an open thread fills the screen, and Open latest and Share move into the ··· menu. See Triage from the dashboard.
August 6, 2026
feature
let clients comment without an account
A public link can now collect feedback. Turn on guest commenting and anyone who opens the link can leave comments through the review widget — no Artor account, no sign-up, no invite.

You choose how much to ask for: comment anonymously, ask for a name, or ask for a name and an email. Set it when you create the link, or change it later in Link settings. From the terminal:
```
artor share add --comments name
```
Guests see only their own notes, never your team's discussion or another visitor's. Their feedback lands in the same place as everyone else's — the triage list, the widget, and artor comments — clearly marked as guest and grouped per visitor, so you can tell one client's notes from another's. You, an org admin, or a space admin can delete anything a guest wrote.

Two things worth knowing: guest names and emails are typed by the guest and never verified, so treat them as a signature rather than proof, and guests are never emailed by Artor in any mode. Links you created before today are set to off — nothing you already handed out starts accepting comments on its own.

Everything else about a public link is unchanged: no source, no remix, nothing else in your org.

Also in this release:
- Repoint a live link. Open Edit on a link's row to point it at a different version, or switch between pinned and latest, without changing the URL your visitors already hold.
- artor share list shows each live link's guest-commenting mode, alongside its mode, expiry, and view count.
- Tapping a folder on your phone opens that folder. In list view on mobile Safari, every tap used to land in the last folder.
July 16, 2026
feature
sign in with a magic link
You can now sign in without a password at all. Enter your email and Artor sends a one-time sign-in link — open it and you're in. Each link works once and expires after an hour.

This is the default way to sign in now: nothing to set up, forget, or reset. Passwords still work if you like one — Use a password instead sits right under the link button.

Enter your email on the login screen and check your inbox.
July 16, 2026
feature
sign in with google
You can now sign in to Artor with your Google account. Pick Continue with Google on the login screen — one click, no password to create or remember.

If an Artor account already exists for that verified Google email, the two link automatically, so you keep every prototype, comment, and org you're part of. If you're new, it creates your account on the spot with your email already verified, no separate confirmation step.

Continue with Google is on both the sign-in and sign-up screens now.
July 9, 2026
feature
see why a prototype crashed
When a running prototype fails to boot, you no longer get a blank error page with no explanation. Artor now captures the crash output automatically and shows you the cause, plus a suggested fix.
```
artor logs
```
Read the crash tail from the terminal, or open the Logs tab in a version's details in the dashboard. Secret values from your environment variables are scrubbed out before the log is stored, so nothing sensitive ends up in the trace.
July 6, 2026
improvement
comments on any prototype
The in-page review widget now works on static prototypes too, not just node servers. Any published version, framework or plain HTML, gets the same commenting experience.

Drop a pin, quote some text, start a thread, and resolve it, on every prototype you ship.
July 6, 2026
improvement
rename your organization
Picked the wrong name when you signed up, or your team rebranded? You can now rename an organization from Settings without recreating it or losing any prototypes, comments, or history.

Your preview URLs keep working, and everyone on the team sees the new name right away.
July 4, 2026
feature
comment right on the prototype
Reviewers can now leave comments directly on the live prototype, in the page itself, with no separate tool and no screenshots. Click any element to drop a pin, or highlight a passage of text to quote it, then start a thread.

Comments are anchored to the element and to the exact version, so a note on v1 never drifts onto v2, and the pin follows the element even as the layout shifts. Threads support replies, resolve, and @mentions of anyone on your team.

Open a version's preview and start commenting. Everyone in the org sees the same threads.
July 4, 2026
feature
react router, remix, and tanstack start
Artor now publishes React Router v7, Remix, and TanStack Start apps as full running servers, with their API and server-rendered routes intact, alongside the Next.js and static support you already had.

Point artor publish at your project and Artor detects the framework, builds it the right way, and boot-tests the result before it goes live, so a prototype never silently loses its dynamic routes.
June 27, 2026
feature
bring your whole team in
Artor is built around orgs and teams — everyone on your team sees the same artor, leaves comments, and shares the same workspace. Inviting them is now seamless: they land on the invite page, see the org they're joining, and create an account right there if they don't have one — verified instantly, no separate signup flow.

If they're already signed in under a different email, they get a clear path to switch before accepting.

Invite your team from Settings → Members.
June 26, 2026
feature
install and update the cli anywhere
The CLI now installs and updates itself — no manual npm install -g required.
```
artor install   # first-time setup
artor update    # stay current
```
Works across npm, yarn, pnpm, and bun, and handles enterprise environments where global installs are locked down. When your CLI is out of date, artor publish tells you and offers to update before continuing.
June 25, 2026
feature
recopy a share link any time
You can now get a live share link back from the CLI whenever you need it — not just at the moment you create it.
```
artor share list
```
Useful when a designer asks for the link a week later, or you shared from a terminal session you no longer have open. Active links show their full URL; expired or turned-off links are clearly separated so you always know what's live.
June 24, 2026
feature
manage skills from the dashboard
Org skills and starter templates now have their own pages in Settings. You can see what's installed, sync to the latest version, and add or remove entries without opening a terminal.

Skills are the Claude Code instructions your team shares — pinned to an exact commit so everyone builds from the same playbook. The dashboard is now the place to manage them alongside the rest of your org settings.
June 24, 2026
feature
start new artor from a template
Your org can now maintain a library of starter templates — pre-built project scaffolds that anyone on the team can spin up instantly.
```
artor init --template <name>
```
Instead of starting from a blank repo every time, templates give your team a consistent, opinionated starting point: the right config, the right structure, the right dependencies already in place. Admins push templates from any local directory; members pick one when running artor init.
June 24, 2026
feature
publish any static site
You can now publish any folder that has an index.html at the root — no framework, no build config, no extra steps.

That means Figma-to-HTML exports, Framer or Webflow downloads, generated reports, or anything your AI tool spat out as plain HTML. It goes live the same way a Next.js prototype does: versioned, shareable, and accessible only to your team.

changelog

A retried publish never makes a second version

Registry list tells scripts whether the proxy is available

Comments inside dialogs and tabs

One setting for who can comment on a shared link

Profile pictures in the review widget

Publish a Next.js app from a monorepo

Members open shared links as themselves

The review widget stays with the page

A welcome for everyone who joins

Comments update on their own

Customize your spaces

Delete prototypes and versions

Remix from the dashboard

Clearer messages for suspended accounts

Clearer settings pages and tab titles

Multi-account CLI login

AI agents can now preview your published prototype for debugging, via the CLI

No more pushing unnecessary files: .gitignore is honored, plus a new .artorignore

Improvements on static prototype sizes

Usage bars in the CLI

protect your public share links with a password

prototype links open in the right organization

an easier comment feed, on any screen

let clients comment without an account

sign in with a magic link

sign in with google

see why a prototype crashed

comments on any prototype

rename your organization

comment right on the prototype

react router, remix, and tanstack start

bring your whole team in

install and update the cli anywhere

recopy a share link any time

manage skills from the dashboard

start new artor from a template

publish any static site