DarnlyWe make Darnly, so read this list with that in mind. We've tried to be fair: each tool below is the best pick for someone, and Darnly isn't the best pick for most of the cases here. Facts about other tools come from their own pages, checked between 3 and 10 November 2026.
The short list
| Tool | Best for | Price | Agent access |
|---|---|---|---|
| Darnly | Bugs you find yourself while testing, kept as a list your agent works through | Free | Files in your project, or MCP |
| MarkLayer | Annotating a live page by link and letting the agent resolve each comment | Free | MCP |
| Shotline | Client feedback by link, with the agent posting before and after proof | Free (1 canvas), Pro $19 a month billed yearly | MCP |
| Jam | Bugs that need a video, and bugs from teammates or customers | Free plan (30 Jams a month), Team $14 per creator a month | MCP |
| Marker.io | Feedback from clients through a widget on your site | From $39 a month, 15-day trial | MCP |
| TraceBug | The most evidence per bug: replay, network, repro steps, a generated test | Free, open source | MCP |
| FeedBug | Tester pins that become Linear or GitHub issues | Free (25 reports a month), MCP on Pro | MCP (Pro) |
| Disbug | One-click capture with errors, network and events, pulled by an agent | Free for solo developers | CLI and MCP |
| Pastel | Reviewing whole pages and files with clients | 14-day trial, then paid | MCP |
| MarkAgent | Marking elements and copying a ready prompt to paste | Free | Copy and paste |
| Claude in Chrome | Claude Code checking its own work in your browser | Needs a paid Claude plan | Built in |
| Chrome DevTools MCP | Any agent driving its own Chrome to look for problems | Free, open source | MCP |
| Cursor Design Mode | Pointing at an element and changing it right away inside Cursor | Part of Cursor | Built in |
| A plain screenshot | One visual bug, right now | Free | Paste |
1. Darnly
A free Chrome extension and Mac app. Press one key, click the broken part, type what you expected. Each bug is saved in your project's .darnly/inbox/ (or an optional cloud inbox) with a screenshot boxed in red, the element, the file that drew it on a local project, recent errors and requests, and the steps that led to it. You can say "Change only this one" or "Change all like it". Then say "fix my Darnly bugs": the agent works through the list, checks each fix in a browser when it can, and marks it fixed with a note.
Pick it if you build alone with Claude Code, Codex or Cursor and find bugs in batches while you use your own app. Skip it if you need video, bugs come from clients, or you track work in Jira or Linear. It has no tracker integrations.
2. MarkLayer
A free web app and Chrome extension. Paste a URL and annotate the live page, or use the extension for pages behind a login, then share the link; viewers need no account. Each comment is tied to an element by its CSS selector and keeps the browser and viewport. Its MCP server lets Claude Code or Cursor watch for comments, reply, and resolve them. Its page doesn't mention console errors or network requests. More in Darnly vs MarkLayer.
Pick it if you want a free, shareable review link that others can comment on and your agent can resolve.
3. Shotline
A feedback tool where clients comment on a shared link with no install or account. Website pins capture the selector, viewport, screenshot and console errors. Through its MCP server, Claude Code, Cursor, Codex or Windsurf resolve pins and post a fix summary with a before and after screenshot. Free covers one project and one canvas; Pro is $19 a month billed yearly. Localhost needs a tunnel like ngrok. More in Darnly vs Shotline.
Pick it if clients review your work and you want the agent to show proof of each fix.
4. Jam
A screen recorder for software teams. A Jam holds a video or screenshot, console logs, network requests, user events and an AI summary. Recording Links let anyone record a bug with nothing to install, and Jam MCP lets Claude Code, Cursor and Codex read a Jam. The free plan allows 30 Jams a month. More in Darnly vs Jam.
Pick it if bugs need a recording, or they come from teammates, QA or customers.
5. Marker.io
A paid feedback tool for teams and agencies. A widget on your site lets clients report bugs without an account, and reports go to Jira, Linear, Trello, GitHub and more. It has its own MCP server. Plans start at $39 a month billed yearly. More in Darnly vs Marker.io.
Pick it if clients or a team send you feedback and you already use a tracker.
6. TraceBug
A free, open-source browser extension that records a lot per bug: session replay, network calls, repro steps and a generated Playwright test, with an MCP server and export to GitHub or Jira. It also runs in Firefox. More in Darnly vs TraceBug.
Pick it if you want the fullest record of each bug, or a test that fails until it's fixed.
7. FeedBug
A script tag you add to your site. Testers click where the bug is, and FeedBug captures a screenshot, console logs, JavaScript errors, failed requests and the clicked element, then creates a Linear or GitHub issue. Its MCP server, which traces a report to its source file, is on the paid plans. Free allows 1 project and 25 reports a month.
Pick it if testers report bugs on your site and your work lives in Linear or GitHub.
8. Disbug
A Chrome extension plus a CLI and MCP server. One click captures a screenshot, console errors, network logs, the DOM selector, a trail of events and browser details, and an agent pulls the latest session or just the fields it needs. It says it is free for solo developers and is being rebuilt in public.
Pick it if you want an agent to pull full technical captures and don't mind an early-stage tool.
9. Pastel
A website annotation tool for designers and agencies. Reviewers comment on a shared link without logging in, comments can become tasks, and an MCP server lets Cursor, Claude or ChatGPT act on them. It has a 14-day trial.
Pick it if you review whole pages and files with clients.
10. MarkAgent
A free Chrome extension that runs entirely on your machine. Mark elements, add a note, and it copies markdown (page, element, React component and file in dev mode, screenshot) to paste into your agent. Journey mode records your clicks as numbered steps. There's no inbox or MCP: you paste each report yourself.
Pick it if you like pasting a prompt straight into the chat and want nothing stored anywhere.
11. Claude in Chrome
Lets Claude Code open and drive your Chrome during a session: read the page, click, and check its own fix. It needs a paid Claude plan, and each browser step uses your plan's usage. More in Darnly vs Claude in Chrome.
Pick it if you're in a Claude Code session and want the agent to look for itself.
12. Chrome DevTools MCP
An open-source MCP server from the Chrome team that lets any agent open its own Chrome, read the console and network, and take screenshots. More in Darnly vs Chrome DevTools MCP.
Pick it if you use Cursor, Codex or another agent and want it to inspect the page itself.
13. Cursor Design Mode
Cursor's visual editor lets you point at an element in Cursor's own browser and have the agent change it right away. More in Darnly vs Cursor Design Mode.
Pick it if you work in Cursor and want live tweaks while you build.
14. A plain screenshot
Take a screenshot, paste it into the chat, and write one sentence on what you expected. In our test this fixed visual bugs as often as a Darnly report and cost less. It falls short when the cause is an error you can't see, or when you have ten bugs to describe. More in Darnly vs a plain screenshot and how to show Claude Code a bug.
Pick it if it's one visual bug and you're already in the chat.
How to choose
- Who finds the bug? You: Darnly, MarkAgent, TraceBug, Disbug or a screenshot. Clients or a team: MarkLayer, Shotline, Pastel, Marker.io, Jam or FeedBug. The agent itself: Claude in Chrome or Chrome DevTools MCP.
- One bug or many? For one, paste a screenshot. For a testing session with ten, a capture tool with an inbox saves the retyping.
- Do you need video? Only Jam and TraceBug record.
- Does it need to reach a tracker? Marker.io, Jam, TraceBug and FeedBug export to trackers. Darnly and MarkAgent don't.
- Should the agent report back? Darnly, MarkLayer and Shotline let the agent mark each item done.
Many people use two: an agent browser to check fixes during a session, and a capture tool for what they notice the rest of the time.
Want to try it? Add Darnly to Chrome.