Radial app

Client review

Send clients a polished review link instead of a bare preview URL. The viewer carries your branding, embeds the site at real device widths, and gives the client one obvious way to say "approved" or "change this." No login for anyone.

Present to client

Open the publish menu and choose Present to client…. Add the client's name if you want the viewer to say who it's prepared for, and Radial deploys the current state of the site plus a branded review page around it, then hands you a stable link. Re-presenting later updates the same link; it never changes underneath the client.

This works even before the project has a GitHub remote. All it needs is a Vercel connection for the deploy.

What the client sees

• Your agency's name and logo, with a "Prepared for" line. No Radial branding anywhere.
• The real site, browsable page by page, with a desktop / tablet / mobile width toggle.
• Approve and Request changes buttons with a comment box.
• No account, no login. The link is unguessable, the same trust model as a Vercel preview URL.

Comments inside Radial

The Comment tool (C, or ⌘⇧C for the Comments pane) drops pins directly on elements of the live preview. Each comment stores the element it's anchored to, so it survives reloads and moves with the page.

• Pins are draggable; click one to read, reply, or resolve.
• Comments are stored in the project (.radial/comments.json), where terminal agents read them as context. Ask an agent to "work through the open comments" and it can see every pin, its element, and its page.
• When an agent resolves a comment, Radial says so with a toast rather than letting pins vanish silently.

Comments from the Vercel Toolbar

If the project is deployed on Vercel, comments people leave in the Vercel Toolbar on its preview deployments show up in Radial too, as pins on the same elements and rows in the Comments pane marked via Vercel. Replies fold in under the first message, attachments are downloaded into .radial/comment-images, and the row links back to the thread on vercel.com. Agents read them like any other comment.

• What it needs: the Vercel CLI 59.1 or newer (npm i -g vercel@latest), signed in with vercel login, and the folder linked to its Vercel project (vercel link, which Publish does for you). The Comments pane says which of these is missing.
• When: right after the project opens, every three minutes while Radial is in front, and on demand from the pane's actions menu (Pull from Vercel now) or radial comments pull. Vercel has no webhook for comments, so this is a poll.
• Pinned where it was left: a comment lands on the same element as on the deployment, and Radial keeps two fallbacks for a local page that differs by a wrapper. Opening a comment someone left on a phone or tablet switches the canvas to that preset first, so you see the layout they were looking at. The row says which branch and device it came from, and the thread links back to Vercel and to the preview page.
• Sent to the agent with everything Vercel captured: the deployment, the reviewer's device, and the React component tree at the element, which is usually enough to find the source without a search.
• Who owns what: Vercel owns the text, the element and the images; Radial owns whether you've addressed it and where you dragged the pin. A comment resolved on Vercel resolves here. One resolved in Radial is resolved on Vercel after your next publish, with a closing reply naming the pushed commit. Nothing is ever reopened by a pull.
• Comments only exist on preview deployments (the production alias needs the @vercel/toolbar package). Converting a comment to a Linear, Jira or GitHub issue resolves it on Vercel's side, so it resolves here too.