Comments pinned to the element, a chat you can steer, and reviews that walk the flow
A comment now attaches to the element under the cursor, arrives with the screen and control it came from, and stays on the screen it was left on even in a hash-routed app. Runner chat gained everything people arrive already knowing: edit an earlier message, queue one mid-answer, drop in an image. Design review drives the page instead of taking a screenshot of it, asks a question when a request is ambiguous, and lands in the workspace the link belongs to.
- Comments pinned to the element they are aboutImproved
The widget outlines the control under the cursor, pins the comment to it, and marks up the screenshot with a crop around that element before upload. Each comment records the screen’s own title and the control it sits on alongside the full URL, so a digest names the Billing settings screen and the Change plan button rather than a route fragment. Hash-routed apps are handled too: every screen shows its own feedback instead of the whole app’s.
Widget documentation - Comments that keep up with your releasesNew
Every comment is stamped with the version of the page it was left on, and the review screen numbers them into a v1, v2, v3 timeline you can filter by. Declare your own version with a data-sd-version attribute, then choose what a release does to older comments: keep them open, or resolve them. Summarising saves its digest and serves it again while the comments are unchanged, so the next person reading waits on nothing.
- A Runner chat you can steer mid-answerImproved
Type while an answer is streaming and it queues, or send it now to steer the run already in progress. Up arrow edits an earlier message and re-runs from that point, /compact summarises a long conversation without clearing the transcript, images paste or drop into the composer, and the page context the agent is using is a chip you can switch off.
- Design review that walks the flowImproved
A review drives the page rather than taking one screenshot per link: it opens menus, follows the flow and reviews as the project’s default actor, so it carries that actor’s sign-in, tools and knowledge. When a request is ambiguous it puts one question back in the Slack thread and waits, and a reply there continues the same review. Reviews started from Slack, Linear or Figma land in the workspace and project their link belongs to.
Design review in Slack - Workspace rules from what you already shipImproved
Fill the workspace Guidelines library straight from a published Storybook or a GitHub repository, so rules cite the components, variants and token values your design system actually ships rather than a generic standard. Apply a set of workspace rules to design reviews in bulk, and add new ones through a stepped flow instead of a wall of fields.
- Interview films at a length you will watchImproved
A synthesised round fits a two to five minute window, with narration written to a length budget rather than cut short at the end. A finished render is reachable from the interview itself, and a transcript screenshot opens full size in a modal.
- Workers that come back after a sleepImproved
A device worker recovers on its own once a dropped heartbeat resumes, so closing a laptop lid no longer leaves a dead entry in the list. The workspace worker list clears its duplicates, and an internal link an agent is given is routed to a worker owned by the person who asked for it.
Self-hosted workers - Smaller things across the productImproved
Report a bug with images pasted, dragged or picked into the Feedback dialog, up to five, and Cmd/Ctrl + Enter to send. The command bar ranks results as you type, inbox items deep link to the run or comment they are about, the Mac app renders release notes as formatted text, the Figma plugin’s chat and filter counts behave, and the /signin link on the marketing site lands on the app login.
- Steadier under the hoodImproved
Runs no longer strand in progress: a participant that times out is cancelled and reconciled rather than abandoned. Scheduled work wakes on the moment it is due instead of polling for it, and an error is ticketed with its context and trace attached rather than patched blind.