Can browser drag and drop prove that an agent's work is correct?

CODING AGENT WORKFLOW · PRACTICAL GUIDE

Approval-Gated Browser Drag and Drop

Move native draggable items to declared page drop targets through Playwright with an explicit review and approval step.

THE PROBLEM

Kanban boards, sortable lists, and file-free drag interfaces cannot be completed by click-only browser tools. A drag can also move or submit data, so treating it as an ordinary click can have unexpected effects.

HOW THIS TOOL WORKS

browser_inspect exposes visible native draggable sources and declared drop targets. browser_drag proposes one source-to-target move but does not execute it. Review both labels and call browser_confirm separately; the one-use approval expires after five minutes and is cancelled if the inspected page state changes.

Local sample task board with a draggable review card in To do and an empty Done lane — Local demo with synthetic content. Try it from the example page.

TRY IT

1. browser_inspect({}) → choose fresh refs marked dragSource and dropTarget.
2. browser_drag({ sourceRef: "r3", targetRef: "r7" }) → review both labels and the proposed move.
3. browser_confirm({ approvalToken: "<token returned by browser_drag>", approve: true }) → execute only after review.

LIMITS

This supports DOM-backed native draggable sources and declared drop targets. It does not infer arbitrary mouse gestures, drag calendar time ranges, upload files, or verify the page application's business outcome; inspect the resulting page after each approved move.