Visual feedback for AI agents and teams. Click an element on any page, say what should change — the comment carries the element.
Users
98
+98 in 30 days
Rating
5.0 / 5
+5.00 in 30 days
Ratings
2
+2 in 30 days
Store rank
#85K
#71K among extensions
Version
1.1.1
updated 25 Sep 2026
Users
monthly, 1 months
Latest, 16 Oct 2026:98 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 16 Oct 2026:2 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About VibeComments — Visual Feedback for AI Agents
VibeComments puts a comment on the element itself.
Click a button, a card, a heading — on localhost, on a preview URL, or on the
site you already shipped — and write what should change. The comment is anchored
to that element, not to the page, so whoever reads it next lands on the one you
meant instead of the three next to it.
WHAT YOU DO WITH IT
• Copy the batch for your agent. Every open comment goes to the clipboard as one
block, with the element and the page it belongs to. Paste it into the coding
agent you already run and it has what it needs to make the change.
• Or let the agent read them itself. Start the local server
(npx @vibecomments/local) and your coding agent reads the comments over MCP,
answers on the thread and resolves what it has done — on your own machine.
The extension's MCP tab walks you through connecting it.
• Or hand it to a person. Threads live on the element, with replies and a status
of open or resolved — so the argument happens on the screen everybody is
looking at, rather than in a doc that describes it.
ANCHORS THAT SURVIVE A DEPLOY
A comment records several ways to find its element again — selectors, an XPath,
and a quote of the text around it — and tries them in order when the page has
changed underneath. If the element moved but is still there, the comment moves
with it. If the match had to be approximate, the extension says so instead of
pretending.
SEE IT AT PHONE WIDTH
Open the page at a phone or tablet width without leaving the tab — iPhone and
iPad presets, a custom size, and rotate — and leave comments on the layout a
small screen actually gets.
LOCAL BY DEFAULT
With no account, everything stays in the extension's own storage on your
machine — the pages you visit never see it, and neither do we. If you start the
local MCP server, the extension also hands your comments to it at
127.0.0.1 — still your machine, still not us. Signing in is
what creates a server-side copy, and it exists for one reason: a comment has to
be able to reach a teammate.
WITH A TEAM
Teams are invite-only during the beta: you join an organization by invitation,
then sign in with a six-digit code sent to that address. No password to choose
and none to store. An organization holds projects, each project is scoped to its own
URLs, and members join a project as editor or viewer. Comments, replies and
emoji reactions arrive over a live connection, so a teammate's answer appears
without a reload.
WHAT IT NEVER DOES
• It does not read the pages you visit. It records the element you picked and
the words you typed about it — nothing else from the page.
• It contains no analytics. No tracking SDK, no third-party scripts, no
advertising identifiers, no telemetry of any kind in the extension.
• It sells nothing to anybody. There are no advertisers to sell to.
Support: support@vibecomments.com
Growth
Window
Users
Change
Ratings
Rating
7 days
−7
−6.7%
0
0.00
30 days
+98
–
+2
+5.00
Chrome Web Store search rankings
Where VibeComments — Visual Feedback for AI Agents appears when people search the store, with the 30 day change