DIVE vs pls-fix

pls-fix focuses on comment-pinning bugs. DIVE covers comments plus full visual editing, MCP handoff, and structured exports.

pls-fix is a specialised tool for filing visual bug reports with annotations. DIVE is a broader design surface, comment pins are one feature among many (Layers tree, Design controls, Changes tab, MCP).

Pick DIVE when

You want to fix the bug, not just annotate it.
You want to ship the structured diff to an AI agent.
You want one tool for designers, developers, QA, PMs, and content.

Pick pls-fix when

All you need is comment pins on screenshots.
You don't need to edit the page itself.

Feature	DIVE	pls-fix
Visual editing on a scriptable webpage	Yes, typography, colour, layout, spacing, motion and effects on localhost, staging or production pages the extension can script. Browser-protected pages are excluded.	Comment / pin only
MCP (Model Context Protocol) handoff to AI agents	Yes, Cloud, Local, and Self-hosted modes; eight common session tools, plus Local feedback rounds	No
Persistent change history (Changes tab)	Yes, searchable, filterable, exportable	Per-comment threads
Open source	Yes (MIT)	Check current licence
Price	Free MIT-licensed extension	Check current pricing
Markdown / JSON export of the diff	Yes	Comments / links
Best fit for	Designers, developers, QA, PMs, content, indie hackers, agencies, vibe coders	Bug reporting & feedback

The honest take

If you only need to pin comments on a deployed page, pls-fix is purpose-built. If you also want to make the fix, ship the spec to engineering, or run a full design review, DIVE covers more ground.