#1244·rod

wand: a separate module built from a snapshot of rod, addressing several open issues here (v0.1.0-rc.1)

Author: Fly-PlaygroudCreated Sep 8, 2026Updated Sep 8, 2026

Not a bug report and not a request — an index, so that someone searching this tracker for one of the issues below finds where it was addressed. Close it whenever you like.

wand (github.com/headlesslab/wand) is a browser automation library for Go. Its code began as a snapshot of this repository at commit 393ac0d (2024-12-07), renamed to its own module path and maintained independently by headlesslab, under upstream's MIT licence with the attribution in NOTICE kept as it is. Thanks to ysmood and to everyone who contributed here.

It is a separate module rather than a continuation of this one, and it offers no API compatibility contract with rod. Its first release candidate, v0.1.0-rc.1, went out today. It redesigns no API.

Open issues here that it addresses

Each has a regression test that fails on the snapshot and passes on wand. I have left a one-line comment on each of these with the test's name, so this list is just the index.

  • User mode on Chrome >= 136 — #1189, #1184
  • go get -u and the cached-browser panic — #1203, #1195, #1237, #1202
  • Page, element and hijack — #1179 (WaitRepaint and the page context), #1226 (per-session CDP states), #1198 and #1034 (element screenshot at DPR != 1), #982 (a bad hijack regexp panicking)
  • Launcher — #1045 (no linux/arm64 browser to download), #828 (FreeBSD lookup)
  • leakless — #865, #1214, #1232, and the antivirus reports in #1229 and #720
  • WebSocket, partially — #1092: the Sec-WebSocket-Key and the control frames, not the header ergonomics or the close codes

Nine more fixes come from unmerged pull requests here; the release notes list them with their numbers and their original authors.

Where the detail is

One caveat worth repeating here rather than making anyone find it: an API modernization is planned that will change wand's API in a later minor, so go get -u=patch is the safe upgrade, and moving now means adapting again later.

Nothing in this issue asks for a change to this repository.