An open-source tool for validating code changes with browser recordings
Why This Matters
Directly addresses browser automation and fine-tuning (Claude Code) with specific technical content (Playwright traces, HAR files, console logs).
Abstract
Lately I've been experimenting on an open-source project called Canary. It takes a code diff, identifies the UI flows that are likely affected, and then uses Claude Code to test those paths in a real browser. Every run captures video, screenshots, network traffic, HAR files, console logs, and Playwright traces. The result is both a validation run and a replayable Playwright script.
Links
Metadata
Save to Vault
Save this article directly to your Obsidian vault. Opens Obsidian with the note pre-filled.
Will save to: vault/inbox/signals/2026-06-07-an-open-source-tool-for-validating-code-changes-with-browser-recordings.md