DIVE vs VisBug

VisBug edits the live page but has no agent / MCP handoff and no session persistence.

VisBug is the OG of in-browser visual editing, small toolbar, quick edits, no persistence. DIVE is the version of that idea built for the AI-coding-agent era.

Pick DIVE when

You want edits that persist and export to a structured diff.
You want to ship the diff to an AI agent.
You need the full design surface (motion, effects, contrast checker, layers).

Pick VisBug when

You want a tiny zero-config toolbar and nothing more.

Feature	DIVE	VisBug
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.	Yes, toolbar-based
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-session, not exportable
Open source	Yes (MIT)	Apache 2.0
Price	Free MIT-licensed extension	Free
Markdown / JSON export of the diff	Yes	Copy CSS
Best fit for	Designers, developers, QA, PMs, content, indie hackers, agencies, vibe coders	Quick in-browser tweaks

The honest take

VisBug is fantastic and influential. DIVE is closest in spirit to it but built for a different era and a different handoff target.