DIVE vs Handle Extension

Both are free, MIT-licensed browser tools for visual changes and agent hand-off. The choice is between DIVE's exports and connection modes, and Handle's local agent-session workflow.

Handle Extension is a close alternative, not just an annotation tool. Its Chrome side panel supports visual refinements, inline text editing and natural-language feedback, then returns context to your coding agent. DIVE offers live editing, recorded changes and comments with copy/export hand-off or Cloud, Local and Self-hosted MCP. The meaningful difference is workflow, not a free-versus-paid split.

Pick DIVE when

You use Firefox as well as Chromium, or want to review a scriptable page without first starting an agent session.
You want a portable copied/exported specification as well as direct MCP hand-off.
You want to choose between hosted Cloud, Local and Self-hosted relay connections.

Pick Handle Extension when

You work in Chrome with a local dev server and want the agent to initiate a live feedback session.
You want its setup command to configure a supported agent rather than enter the MCP configuration yourself.
You want to evaluate its session discovery and repeated feedback rounds with an explicit stop action.

Feature	DIVE	Handle Extension
Core editing workflow	Edit the rendered page, record changes, add comment pins and hand the specification to a developer or agent.	Select elements in a Chrome side panel, refine styles or text, attach notes and send structured feedback to the active agent.
Setup and browsers	Chrome/Chromium or Firefox extension. Start editing without MCP; configure it when you want a connected agent.	Chrome extension plus a local MCP server. The documented setup runs npx handle-ext@latest init and restarts the agent; invocation varies by agent.
Connection model	Cloud, Local or Self-hosted MCP, plus copy/export without a live agent connection.	Documented local stdio MCP and Socket.IO bridge. A discovery server exposes active sessions with agent and repository context.
Feedback rounds	Agent tools read changes, return browser previews and update statuses. Local mode also supports opt-in feedback rounds with immutable per-Send snapshots and an explicit Stop; Cloud and Self-hosted remain one-shot.	The published MCP implementation continues a live feedback session across rounds, with a user-stop action and a grace period for brief extension disconnects.
Cost and licence	Free, MIT-licensed. Your paid agent or model costs are separate.	Also free and MIT-licensed, using your existing agent. No paid extension tier is advertised on the reviewed page; agent costs remain separate.

The honest take

Handle deserves consideration if your work already revolves around a local coding-agent session. DIVE is the better fit when browser choice, portable hand-off or relay choice matters more. Do not confuse Handle Extension with Handle Studio: the separate Studio app's macOS requirement is not an extension restriction. Neither browser tool independently guarantees a correct source-code change.

How we checked

Checked on 16 September 2026. Browsed the extension page and its v1.0.3 revision notes; reviewed the public repository, MIT licence and MCP server source. The repository documents agent-specific commands rather than a universal /handle invocation. No extension installation, setup command or live agent round trip was performed; implementation details are source-reviewed, not runtime-verified.