sluglistComparison
sluglist vs BugHerd
BugHerd's signature is sticky-note feedback pinned to page elements, flowing into a hosted kanban board — loved by agencies collecting website feedback from clients. sluglist captures the same kind of element-anchored reports, but outputs them as files with CSS selectors and error context, delivered to storage you own.
What BugHerd is
BugHerd is a commercial, hosted website-feedback tool: clients and testers pin comments to specific page elements (via a widget or browser extension), each pin carrying a screenshot and technical metadata, and everything is managed on BugHerd's kanban board with tracker integrations. It targets agencies and web teams, priced as a subscription.
Written in good faith from public information, August 2026. BugHerd is a trademark of its owner and is not affiliated with sluglist — check their site for current features and pricing.
Side by side
| sluglist | BugHerd | |
|---|---|---|
| License & hosting | MIT open source. No hosted service, no accounts — artifacts go to storage you own via connectors. | Proprietary SaaS — feedback lives on BugHerd's kanban board and servers. |
| Pricing | Free. Your only cost is your own storage/endpoint. | Subscription, per plan/members, with a free trial. |
| Element anchoring | Element mode records a smart CSS selector (data-testid → id → aria → landmark), element text, DOM path and a React component hint — machine-readable localization. | Pins feedback visually to the element on the page — excellent for humans scanning a page for notes. |
| Coding agents | First-class: artifacts are markdown/YAML files an agent reads; four bundled Claude Code skills generate the checklist, walk it in a browser, fix what failed and re-test. | Tasks live on the hosted board; not designed as local files for an agent loop. |
| Autonomous QA loop | A QA agent records evidence-backed verdicts (no fail without a screenshot, no pass without performing the check); npx sluglist status reads the artifacts and says whether another fix→re-test round is worth running, so the loop ends on green — or stops honestly on a stall. | Not offered: the board tracks task status a person sets, not verdicts an agent recorded with evidence. |
| Triage workflow | None by design — one-way capture with a stable artifact format you pipe into your own tracker. | Built-in kanban board with columns, assignments and severity, plus tracker integrations. |
| Acceptance checklists | Built in: the client walks a checklist on staging; verdicts land in session.yaml as a coverage map; flags open linked issues. | Not the model; feedback is ad-hoc pinned tasks. |
| Data flow & privacy | Zero phone-home (test-enforced). Input masking, PII text scrubbing, screenshot consent under the production preset. | Data is processed and stored by the service; capabilities depend on plan and their policies. |
Pick BugHerd when…
- Your clients and PMs want a visual kanban board with pins on the page, zero setup on your side.
- You want membership, assignments and severity handled in a hosted tool.
- Website-design review with many ad-hoc visual notes is the main job.
Pick sluglist when…
- You want element-anchored reports as data (selector + component + errors), not just pins for humans.
- Client sign-off should be a structured checklist with a coverage map, not a pile of notes.
- Feedback must stay on your infrastructure; the widget must be MIT and free.
- A coding agent is part of your fix loop — and you want its verdicts backed by evidence rather than taken on trust.
The part a hosted dashboard has no answer for
Every tool in this category ends at a good report. sluglist keeps going: a QA agent walks an acceptance checklist in a real browser and records verdicts with evidence — no fail without a screenshot, no pass without performing the check — a fix agent answers them in fixes.yaml, and npx sluglist status reads the artifacts to decide whether another round is worth running. The loop ends on green, or stops and says which item has failed twice and needs a human.
Frequently asked questions
Does sluglist show feedback pinned on the page like BugHerd?
No — sluglist has no overlay of past reports. It captures element-anchored reports (selector, DOM path, component hint, screenshot) as files for your tracker or agent. BugHerd is the better fit if stakeholders review feedback visually on the page itself.
Can clients use sluglist without accounts, like BugHerd guests?
Yes — there are no accounts at all. The widget is on your staging site; identity, if you need it, comes from your app or from a reporter form field.
Which handles client acceptance testing better?
BugHerd collects ad-hoc feedback well, but sluglist's checklist mode is purpose-built for sign-off: the client walks the list of what shipped, and you get pass/fail/never-checked per item, with flagged issues linked. See the client-acceptance use case.