BrowserRig v0.5.0

Components

• npm: browserrig@0.5.0
• Chrome extension: 0.1.3
• Extension protocol: 3

What's Changed

• docs(webmcp): record v1 discovery scope in plan by @Castor6 in #44
• docs(webmcp): explain optional Chrome testing flag in READMEs by @Castor6 in #45
• fix: preserve runtime and target safety during relay lifecycle changes by @Castor6 in #46
• feat!: enable native WebMCP discovery by default by @Castor6 in #48
• docs: close v0.6.0 intake and prepare v0.7.1 scope by @Castor6 in #49
• feat: add browser evidence and debugger ownership safeguards by @Castor6 in #50
• docs: prioritize Chrome for upstream compatibility and validation by @Castor6 in #51
• feat: improve compact snapshots and editable input helpers by @Castor6 in #52
• feat: add MCP recording controls and filesystem compatibility by @Castor6 in #53
• fix: preserve session pages and diagnose protected frames by @Castor6 in #54
• docs: close upstream v0.8.2 sync cycle by @Castor6 in #55
• Version Packages by @Castor6 in #47
• ci: stage the 0.5.0 release and finalize after approval by @Castor6 in #56

Full Changelog: v0.4.0...v0.5.0

BrowserRig v0.4.0

Components

• npm: browserrig@0.4.0
• Chrome extension: 0.1.2
• Extension protocol: 3

What's Changed

• feat(webmcp): add opt-in native website tools by @Castor6 in #42
• Version Packages by @Castor6 in #43

Full Changelog: v0.3.1...v0.4.0

BrowserRig v0.3.1

Components

• npm: browserrig@0.3.1
• Chrome extension: 0.1.2
• Extension protocol: 3

What's Changed

• docs: add product comparison and Chinese README by @Castor6 in #21
• ci: automate Chrome Web Store publishing by @Castor6 in #22
• docs: add upstream sync process by @Castor6 in #23
• fix: redact detailed ARIA snapshot values by @Castor6 in #24
• docs: complete upstream sync Batch 01 by @Castor6 in #26
• fix(relay): route browser-context CDP commands by @Castor6 in #27
• docs: complete upstream sync Batch 02 by @Castor6 in #28
• fix: recover managed relay and transient client reconnects by @Castor6 in #29
• docs: complete upstream sync Batch 03 by @Castor6 in #30
• fix(extension): recover connectivity after browser startup by @Castor6 in #31
• docs: complete upstream sync Batch 04 by @Castor6 in #32
• fix: settle handoffs and session deletion by @Castor6 in #33
• docs: complete upstream sync Batch 05 by @Castor6 in #34
• fix: settle network capture lifecycle once by @Castor6 in #35
• docs: complete upstream sync Batch 06 by @Castor6 in #36
• chore(sync): review upstream dependency compatibility by @Castor6 in #37
• docs: complete upstream sync Batch 07 by @Castor6 in #38
• test(smoke): close fixture connections by @Castor6 in #39
• docs: record upstream sync closure readiness by @Castor6 in #40
• docs(sync): close upstream v0.5.1 cycle by @Castor6 in #41
• Version Packages by @Castor6 in #25

Full Changelog: v0.3.0...v0.3.1

BrowserRig v0.3.0

Components

• npm: browserrig@0.3.0
• Chrome extension: 0.1.1
• Extension protocol: 3

What's Changed

• feat: add BrowserRig issue reporting by @Castor6 in #19
• Version Packages by @Castor6 in #20

Full Changelog: v0.2.2...v0.3.0

BrowserRig v0.2.2

Components

• npm: browserrig@0.2.2
• Chrome extension: 0.1.1
• Extension protocol: 3

What's Changed

• fix: download release candidates from GitHub by @Castor6 in #12
• ci: automate direct npm publishing by @Castor6 in #13
• docs: refresh Chrome Web Store screenshots by @Castor6 in #14
• fix(snapshot): recognize semantic main landmarks by @Castor6 in #15
• fix: support Node.js 22.22.0 and newer by @Castor6 in #17
• Version Packages by @Castor6 in #16

Full Changelog: v0.2.1...v0.2.2

BrowserRig v0.2.1

Components

• npm: browserrig@0.2.1
• Chrome extension: 0.1.1
• Extension protocol: 3

What's Changed

• ci: add Changesets version pull request workflow by @Castor6 in #1
• docs: clarify Changeset versioning rules by @Castor6 in #2
• feat: add native DeepSeek Harness plugin by @Castor6 in #4
• chore(extension): refresh store artwork by @Castor6 in #6
• Version Packages by @github-actions[bot] in #5
• ci: automate Changesets pull request checks by @Castor6 in #7
• ci: automate release candidate builds by @Castor6 in #8
• ci: automate Chrome extension versioning by @Castor6 in #9
• ci: automate staged npm and GitHub releases by @Castor6 in #11
• Version Packages by @Castor6 in #10

New Contributors

• @github-actions[bot] made their first contribution in #5

Full Changelog: v0.1.0...v0.2.1

BrowserRig v0.1.0

BrowserRig's first independent public release.

Highlights

• Control the user's existing signed-in Chrome through a local relay and extension, without launching a disposable browser profile.
• Adopt the active tab without a toolbar click or Chrome's browser-wide remote-debugging approval dialog.
• Keep explicit multi-tab attachment, background-tab control, Playwright execution, network capture, secrets, recording, journaling, MCP, and the public Effect client.
• Pin the production relay to BrowserRig's independent Chrome Web Store identity while retaining a source-development path for the bundled unpacked extension.
• Ship deterministic npm and Chrome Web Store artifacts with a documented dual-use security model.

Install

npm install --global browserrig@0.1.0

The Chrome Web Store listing is being prepared as an unlisted release. Until approval, load the bundled extension/dist directory as an unpacked extension.

Verified artifacts

• browserrig-0.1.0.tgz SHA-256: 8daa4b6630d9bbf00d9231eda6d91ba7bd0f87144bea299f4f0b5777d613143c
• browserrig-extension-0.1.0.zip SHA-256: 0d70be24e8e7a0ac5c71ff5cb84618c3ca5e3f25bc9f95894ae83c1e2b8c564e

See CHANGELOG.md for the complete release history and upstream lineage.