PointChat
PointChat compared
Several tools let you point at part of a web page and pass that to an AI coding agent. They differ in what you have to install, what the agent receives, and where your notes are stored.
Short version
- PointChat (pointchat.app) is a Chrome extension. It works on any page you open, including localhost and file://, without adding anything to your project. You copy your comments as Markdown and paste them into Claude Code, Cursor, Codex or another agent. No account, no server, no MCP.
- Pick a tool with MCP if you want the agent to read and resolve feedback by itself instead of you pasting it.
- Pick a tool that reads React source locations if you only work on your own React app in development and want
file:linein the prompt. - Pick a team bug tracker if clients or teammates report issues and you need accounts, boards and integrations.
Side by side
Competitor details are taken from each product's own site, docs, GitHub README or store page on 2026-10-22. "Not documented" means we did not find it in those pages, not that the product cannot do it. Corrections: pointchat@playverseai.com.
| Tool | What you install | What the agent receives | How it reaches the agent | Storage / account | Where it works |
|---|---|---|---|---|---|
| PointChat | Chrome extension; nothing in your project | URL, heading path, table row and column, element text, CSS selector, selected text, image region, your note; page state (tab or dropdown) when relevant | Copy as Markdown; page text fenced as UNTRUSTED | Local extension storage; no account; no network requests | Any page you open, including localhost and file:// |
| Agentation | npm React component in your project; optional local MCP | CSS selector, React component tree, source path when exposed, computed styles | Markdown to clipboard; MCP with two-way status | localStorage, optional SQLite; no account | React 18+ pages that include the component |
| React Grab | npm package / npx grab, dev-time script | HTML, component name, source file and line | Clipboard | Not documented | Your own React app in development |
| MarkLayer | Web app or Chrome extension | CSS selector, computed styles, layout, framework components; drawings and highlights | Share link that works as a remote MCP; Markdown from the inspector | Cloud once shared; no account for guests | Any page; extension covers localhost |
| Markagent | Chrome extension | CSS selector, DOM, React component and source in dev, URL, viewport, screenshot | Markdown to clipboard | Local; no account | Any open page, including localhost |
| BugHerd | Browser extension or site script | Screenshot or recording, URL, CSS selector, browser and OS, comments | Official MCP; Jira, Linear, GitHub and Slack sync | Cloud; account required | Sites with the extension or script |
| Vercel Toolbar Comments | Toolbar on Vercel preview deployments | Comment threads on a page position or text | Inbox and Slack; agent export not documented | Vercel cloud; Vercel account | Vercel preview deployments |
What PointChat does not do
- No MCP server: the agent does not pull or resolve comments on its own. You paste the Markdown.
- No React source mapping: it gives the selector, element text and headings, not
file:line. - No sharing, accounts or real-time collaboration. Export and import JSON to move comments.
- No drawing tools, screen recording, console or network logs.
Why the Markdown is structured this way
CSS selectors from a rendered page often contain generated class names. PointChat also sends the text the agent can search for in your source: the element's own text, the headings above it, and the table row and column. Page text is wrapped in fences labelled UNTRUSTED so the agent treats it as data, not instructions. Tracking parameters and tokens are removed from saved URLs.