Review: comment on your live app
Click any element of your real, running app and say what's off. Each comment knows its file, line and design token, your agent fixes it, and the commit that names it closes it. Onbrand also moves to onbrand.tools.
Not blue: use --brand here.
Design feedback usually arrives as a screenshot with a red circle on it, and someone has to work out which file that circle points at. Review puts the comment on the element itself, in your real app, and gives it everything an engineer or an agent needs to fix it.
Comment on any element
Add one line to your site:
<script src="https://onbrand.tools/s/<slug>.js" defer></script>
It does nothing for visitors. People you invite open the site with ?review at the end of the address, click any element and say what's off. onbrand init adds the line for you, in index.html, app/layout.tsx, pages/_document.tsx, SvelteKit's src/app.html or an Astro layout.
Each comment knows:
- The file and line it points at. The
onbrand/viteandonbrand/babelplugins tag each element with its source, such assrc/components/Button.tsx:42. They run in dev and on preview deploys and stay out of production builds. - The design token it should use, taken from your design system.
- The text and class names to search for, even without the plugins.
Review together
Invite the people who review your design. Everyone in a review sees the others' cursors and new comments as they happen, so a design review can happen on the product itself instead of in a meeting about screenshots.
Fixes land through your agent
onbrand feedback gives your agent the open comments as Markdown, or over MCP. It can reply, ask the reviewer a question or mark a comment done:
onbrand feedback reply ob-13 "Switched to the brand color" --done
A commit whose subject names a comment, like ob-13, closes it on the next publish. The dashboard shows each fix before and after, so the person who asked can see it landed.
Onbrand moves to onbrand.tools
0.7.0 also gave Onbrand its own address. The app, sign-in and the install guide live at onbrand.tools, and design systems are hosted at sites.onbrand.tools/<name>/, apart from your Onbrand account, so a page's own code can never reach it. Onbrand now runs on Cloudflare, close to wherever your team is.
Nothing changes on your side: every old address, link, install command and GitHub workflow keeps working and is sent to the new one.
Get it
Run onbrand init --review in a repo that's already set up to add just the Review pieces, or have your agent read the install guide. Then share your site's address with ?review on the end.