Skip to contentSkip to Content
Reviewing a prototype

Reviewing a prototype

You received a prototype link. Here’s everything you need to review it and leave feedback, no setup required.

Click the link. If you’re already signed in to your Artor org, the prototype opens immediately. If not, you’ll see a sign-in page. Sign in with your org account and you’ll land straight on the prototype.

If you see a “request access” page, the prototype has been closed by its owner. Use the form on that page to notify them, or reach out directly.

No Artor account?

If you were sent a public link, it opens with no sign-in at all. You’ll see the running prototype, and — if whoever shared it turned on guest commenting — the review widget too. Skip ahead to Reviewing as a guest for what that’s like.

What you’re looking at

The prototype opens and runs normally, with an Artor review widget layered on top. The prototype behaves like a real app — click through it, scroll, fill in forms. What you’re seeing is the version the link points to. Use demo information when filling in forms: a prototype can be connected to services that perform real actions.

The toolbar

The widget shows up as a small floating toolbar in the corner of the page — comment, show/hide comments, show/dim resolved, and a chevron to tuck the toolbar out of the way. Hover any icon for a moment to see what it does and its keyboard shortcut. Click the chevron (or press M) to minimize the toolbar down to a single pill; click it again to bring the full toolbar back. Your comment pins stay visible the whole time — minimizing only tucks away the toolbar itself.

Pause animations

Freeze a moving prototype so you can review a particular moment and pin feedback to it.

  1. Click Pause animations in the toolbar, or press P while you’re not typing.
  2. Leave your comment on the paused view.
  3. Click Resume animations, or press P again, to continue.
The actual Artor review toolbar with animations paused and the Resume animations tooltip showing the P shortcut.

The toolbar shows Resume animations while the page is paused. You can still scroll and leave comments. Videos and audio stay paused until you play them again. Some custom animations may keep running.

Leaving a comment

  1. Open the Comment tool in the review widget.
  2. Click the element you want to comment on — a button, a heading, a card.
  3. A composer opens. Type your feedback and hit Send.
The actual Artor SDK comment thread: an element pin, AI ignore, Resolve, and the reply composer.

Comments stay with the element and version you’re reviewing. Open a pin to read and reply in the Comment thread panel.

The pin stays attached as you scroll or resize the page. Teammates with access to this version can see the feedback. Comments stay with this version; they don’t move to the next one.

Commenting on copy rather than a component? Select the text instead: a small Comment button appears next to the selection, and the comment anchors to that exact quote, highlighted inline. See Commenting on selected text.

Tips for useful feedback:

  • Click the specific element you mean — the anchor is part of the context.
  • Need to press a button or follow a link while the comment tool is armed? Hold Ctrl and click — the click goes to the page instead of placing a comment (the hover chip reminds you on anything clickable).
  • Be specific: “the button label is unclear” is more actionable than “something feels off here.”
  • Screenshots aren’t needed; the comment ties itself to the exact version and element.
  • In the composer, Enter sends (Shift+Enter for a new line) and Esc cancels. A character counter shows how much room is left; Send stays disabled until you’ve typed something.
  • Type @ to mention a teammate — a picker opens (Arrow keys, Enter to pick, Esc to close), and the person you choose may get an email depending on their notification settings. See Mentioning a teammate.

Resolving feedback

When a comment has been dealt with, open its thread and hit Resolve — the pin dims and slides behind the Show resolved toggle, keeping the open items front and center. Got it wrong, or the issue came back? Reopen puts the thread back in the active set. Members with access to the version can resolve or reopen. This is reversible. You can do the same from the terminal with artor comments resolve.

Reading what’s there

Open a pin to read its thread, then use the reply box to continue the discussion. You can edit or delete your own messages. Teammates may receive reply emails depending on their notification settings.

  • An unread dot marks new activity. It is remembered only in this browser.
  • AI ignore leaves a thread for a human when an agent works through feedback.
  • Copy details for AI, in ···, copies one thread for a manual handoff. For an ongoing review, your coding agent can read threads directly through the Artor CLI.

You can also open the prototype in the dashboard to filter, reply to, and resolve its threads across versions. If access is turned off, comments remain readable, but replying and status changes are blocked until access is restored.

Reviewing as a guest

A public link may allow you to comment without an account. Choose Add a comment or press C, then click an element or select text. Type your feedback and press Enter. Choose Done commenting to return to using the prototype.

The first comment may ask for your name or email. These details aren’t verified, and Artor won’t email you. An anonymous link lets you start without entering either.

You see only threads you started, including the team’s replies there. Other guests’ notes and the team’s separate discussions aren’t shown to you.

You can reply in your own threads and edit or delete your own messages. Resolving, mentions, AI ignore, and copying thread links are available only to members.

Stay in the same browser to return to your notes. Clearing cookies or switching devices can make you appear as a new guest. If the link moves to a new version, the earlier notes stay on the previous version for the team to review.

If commenting is turned off during your review, the widget becomes read-only and explains why.

The dashboard shows the full version history for each prototype. If you’ve been sent a link to latest, you’ll always see the newest version. For feedback on a particular build, ask for a specific version. Publishing a new numbered version keeps the earlier version available. Replacing an existing version in overwrite mode is an exception; see Deployments & versions.

To compare versions: open the version list in the dashboard and switch between them. Each version has its own independent set of comments.

What to do next

The publish → review loopCLI reference