Every prototype your team builds, in one place. Everyone comments anywhere in the UI.
One designer builds in Claude Code, another in Codex or Lovable. Publish every build to your team's folders and share one link with developers, product managers and stakeholders. They comment anywhere in the UI, and your coding agent ships the fix.
Nobody knows where the prototypes are. Or where the feedback went.
In Figma, everyone knew where every design was. Now each prototype lives on its builder's own link.
Publish it to critlab and it lands in your team's folders, with a thumbnail, its status and every version on the same link. ⌘K finds any prototype or comment, and Starred and Recents keep yours close.
Everyone builds with a different tool.
Claude Code, Codex, Cursor or Lovable: publish the static build from any of them, as a folder, a zip or a single HTML file, or let your coding agent publish it. Every prototype gets the same viewer, the same comments and one link.
Feedback comes back in Slack, Teams and email.
Developers, product managers and stakeholders comment anywhere in the UI. Each comment keeps a screenshot, the screen size and the version it was left on, and your coding agent reads it over MCP or the crit CLI and ships the fix.
Engineers ask what changed and where the code is.
It is in the viewer: Inspect the styles and spacing of any part of the page, read the files and see what changed between versions, with each version's commit and branch when you publish from git.
One loop for the whole team. From review to shipped change.
Moves to the next tab every few seconds. Choose a tab to stop.
A terminal: crit publish puts the prototype online and prints its share link. Tina and Leo comment on two elements. Then, in Claude Code, the agent pulls both comments over MCP, commits the fix, publishes version 2 to the same link and resolves both comments.
- 1
Publish from your agent
One command, or ask your agent. Each build is a new version on the same link, with its commit and branch from your checkout.
- 2
Review together, live
Designers, product managers and engineers comment anywhere in the UI, on desktop, tablet or mobile, and see each other's cursors.
- 3
Keep the context beside it
Links to the PRD, the tickets and the research, and PDF or Markdown documents, sit on the folder for your team and your agents.
- 4
Your agent ships the fix
It reads the comments with what each reviewer saw, publishes a new version and resolves them. Everyone sees it without a reload.
What your team gets. From the first comment to the shipped change.
Get feedback.
Press C and comment anywhere in the UI. Each comment comes with a screenshot of what the reviewer saw.
Replies, reactions, resolve.
Reviewers talk it through: your agent replies, reacts when it's on it, and resolves once shipped.
Every version, one link.
Switch versions from the viewer's bar. Each comment stays with the version it was left on.
Desktop, tablet and mobile.
Switch the prototype between three screen sizes. Every comment shows the breakpoint it was left on.
Canvas view.
Your screens side by side on one canvas, by breakpoint, with the links between them. Click one to open it.
Inspect and code.
Inspect an element's styles and spacing, read the files and see what changed between versions. You decide who sees the code.
Built for agents.
Over MCP or the crit CLI, your agent publishes, reads what reviewers saw, and resolves.
Live cursors and presence.
See who is in the prototype and where each person is pointing, everyone in their own colour.
Follow and Spotlight.
Present to a client with Spotlight and everyone follows your view. Or follow one person on your own.
Live updates.
New comments, replies and resolved threads appear for everyone, without a reload.
Notifications.
Know when a reviewer comments and when your agent ships the fix. In the app, by email, or as a digest.
Collaboration workspace.
Folders per project or team, every prototype and its versions in one place for your whole team.
One prototype, three ways in. Each role gets what it needs.
Product designers
Comments land where the reviewer left them in your design, with a screenshot of what they saw. Filter them by version and breakpoint, and see every screen side by side on the canvas.
Product managers
Bring stakeholders in with a link or as guests, keep the PRD and the tickets on the folder, and see what is still open on every version. Notifications tell you when a fix ships.
Design engineers and developers
Your agent reads each comment with its CSS selector, the screen size and a screenshot, and ships the fix. Inspect, the files and the changes between versions are in the viewer, and you decide who sees the code.
Questions
Anything else? Write to us at support@critlab.app