Website review for the whole team
Point it out. Claude fixes it. You sign off.
Leave a note on the website itself. Claude Code picks it up, changes the code and hands it back with the before and after, ready for you to approve.
For now, access is by invitation.
01 · Point it out
Everyone points at it, right on the website.
Design, development, QA or whoever signs off: with the Chrome extension, each person clicks what is wrong and says it in their own words. The note already knows where it is.
- Click what is wrongThe note is pinned to that element, with a capture of it.
- Draw on the captureA circle, an arrow, a box or a few words, so it is clear at first glance.
- No need to say whereThe page, the element and the screen width go into the note by themselves.
02 · Fix
Claude picks them up and gets to work.
Claude Code connects to the panel with one line and a permission in the browser, with nothing to paste. It sees the new notes, picks up the ones nobody has taken, reads their capture and element, changes the code and leaves them “Ready for review”, saying what it did.
- Assigned notes stay assignedA note assigned to someone stays with that person.
- @Claude goes firstWhen someone writes to Claude in a note, or answers it, that note is the first one it sees.
claude mcp add --transport http --scope user boolu https://boolu.app/mcp
The first time, Claude Code opens the browser: you sign in if needed and give it access. Everything it does is signed by Claude, and it never closes or deletes notes.
03 · Check
You check it on the page itself.
When you review it, the before capture sits over the page as it is now, at the width the note was left at, and Claude's cursors mark the areas that changed. Drag the edge, see it, and give your verdict.
- At the width it was left atA mobile note is reviewed at 375 px, with its before on top.
- ApproveThe note closes, with its before and after kept.
- Send back, with the reasonIt goes back to Claude with what is missing, ahead of the rest.
In the panel
Every note, with everything in view.
The page with what was pointed out, the before and after, what Claude said, the conversation and where it stands. Enough to decide at a glance.
04 · Live
The whole team, at once.
The board and the open note update by themselves: a card someone else moves slides across with their cursor, Claude's too, and every project shows who is in it right now.
- Guests, per projectClients, freelancers or anyone outside the team see only the project you invite them to, leave notes like the team, and never count as a team member.
- Mentions@Name emails that person; @Claude tells Claude.
- In the extension tooOn the page itself you see when Claude picks up a note and when it leaves it for review.
05 · Reviewing
Everything you need to review a website.
The extension brings a reviewer's tools to the page itself. Whatever you measure, record or try out goes with the note.
Measure
Sizes and distances, as in a design tool. Pin one element, hover another and see the gap between them; press Enter and the measurement becomes a note, already written.
Screen
The page at a phone's 375 px or a tablet's 768, without leaving the tool. The note says the width it was left at.
Video with your voice
When a capture is not enough, record the tab while you talk, up to ten minutes, and the note writes itself when you stop. Available on the Studio and Agency plans.
Variables
Try out the colors, sizes and spacing the page uses, its CSS variables, right on the page. The ones you change go with the note.
06 · Connected
It connects to what you already use.
The extension signs in with your panel account, with no password. Any Claude Code session connects with one line. And updates reach the project's channel.
- Sign in with BooluThe extension opens the panel in the browser and you give it access: it never sees your password. Each browser shows up in your profile, and you disconnect it from there.
- MCP, for any Claude sessionWith 7 tools: boolu_projects, boolu_notes, boolu_note, boolu_start, boolu_comment, boolu_fixed, boolu_ask.
- Updates in SlackA message in the project's channel when a note comes in and when it is ready for review, with its capture.
- Private filesCaptures and videos are never public: they open with a session, a token or a signed link that expires.
Pricing
One price per team, not per person.
Prices exclude VAT. Guests never count as team members. Every new workspace starts with 14 days of the Studio plan, no card.
Free
To try it on one website.
€0a month
€0a year
No card.
No card.
- 1 project
- 2 team members
- Unlimited guests
- Notes, captures and measurements
- Claude over MCP
Studio
RecommendedFor a team that ships websites every month.
€29 a month
€290a year
14-day trial, no card.
Save €58 a year.
- Unlimited projects
- 5 team members
- Unlimited guests
- Video recording
- Review with before and after
- Claude over MCP
Agency
For several teams and many clients at once.
€79a month
€790a year
Save €158 a year.
- Everything in Studio
- 20 team members
- Connectors (Slack)
- Priority support
For now, access is by invitation. Already have an account? Sign in.
Questions
What people usually ask.
What do I need to use it?
Chrome with the extension, to leave notes; the board works in any browser. For Claude to work on the notes, Claude Code connected to the panel over MCP: one line in the terminal and a permission in the browser.
Do I have to paste passwords or tokens anywhere?
No. The extension signs in with “Sign in with Boolu”: it opens the panel in the browser, you sign in if needed and give it access, and it never sees your password. Claude Code does the same the first time it connects. Every access shows up in your profile or in Connect Claude, and you remove it from there.
Does Claude change the code without anyone seeing?
Claude works in your folder, in your Claude Code session, with the permissions you give it. What it does in the panel is signed by Claude, and it never closes or deletes notes: the note comes back “Ready for review” with what changed, and it does not close until a person checks it. If it is not right, you send it back with the reason.
Which websites does it work on?
Any you open in Chrome: local, staging or production. Each project keeps its addresses, and the extension knows which project each page belongs to. Chrome does not let extensions into its own pages, the Chrome Web Store or PDFs.
What do guests see?
Only the projects you invite them to. They leave notes and reply just like the team, and they never count as team members on any plan.
What happens when the trial ends?
The workspace moves to the Free plan unless you choose another. Nothing is lost: everything in it can still be read and worked on, and you are asked to upgrade only when you add more than the plan allows.
Where are captures and videos stored?
Privately. They never have a public address: they open with a session in the panel, the extension's token or a signed link that expires.
And you
Start with one website.
Install the extension, open the page and point out the first thing that is not right. The rest reaches the board on its own.
For now, access is by invitation.