npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@panerelay/agent-browser

v0.10.1

Published

Use agent-browser with current-tab or all-supported-tabs authorization in your existing browser through Panerelay.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

f-loatf-loattuyantuyan

Keywords

Readme

@panerelay/agent-browser

Use agent-browser with the Chrome or Microsoft Edge session you already use. Choose the current tab for focused work or all supported web tabs for cross-page workflows; Panerelay keeps active control separately visible and releasable while agent-browser retains its normal CLI and MCP commands, waits, and page-state semantics.

This is an opt-in automation tool integration. It is a peer of the browser-use integration and is not installed by the engine-neutral Panerelay setup command.

Before you start

Panerelay setup verifies agent-browser but does not install, update, downgrade, or add it to PATH.

Set up with your Agent

Install the unified Skill, then ask your Agent to use its agent-browser workflow:

npx skills add https://github.com/F-loat/panerelay --skill panerelay

The Skill defines environment inspection, official upstream installation when needed, Panerelay integration, the user authorization stop, verification, and troubleshooting.

Set up manually

After agent-browser --version reports a supported version, install and diagnose the Panerelay integration:

npx --yes @panerelay/setup --agent-browser
npx --yes @panerelay/setup doctor --agent-browser

Open Panerelay in the browser and choose current-tab or all-supported-tabs authorization for the task. Then verify the selected authorization boundary:

agent-browser --provider panerelay tab list

Success means the doctor checks pass and agent-browser lists only the tabs authorized in the selected Panerelay browser. Setup and Provider selection never grant site permission or authorize a tab.

What setup adds

@panerelay/setup --agent-browser installs the Panerelay Provider and registers the exact compatible integration. The independently managed panerelay Skill tells Agents how to use it; this package remains a setup-managed runtime and is not intended to be invoked directly by Agents.

Daily use and defaults

Use standard agent-browser commands with --provider panerelay. If you explicitly want Panerelay as the user-level default:

npx --yes @panerelay/setup --agent-browser --global-default

Provider defaults change routing only. They do not grant browser permission, authorize a tab, or acquire the active control lease.

New Side Panel conversations may inject a reserved 56-character panerelay-v2-... session value for the originating tab. Use that exact value with --session and --provider panerelay; it stays within agent-browser 0.33.0's session-name limit while the Provider selects the named live browser and orders the already-authorized target as agent-browser's local t1. Do not construct or shorten the value manually or substitute a similar URL/title when it is unavailable. Malformed and legacy target values fail closed, while ordinary session names keep the existing default-browser and tab-order behavior.

When more than one Panerelay browser is connected, choose one in Extension settings or with the CLI installed by base Setup:

panerelay browsers
panerelay browser use chrome

An unavailable default or ambiguous browser choice fails closed. Every launched session remains pinned to the browser through which it was created, including cleanup.

Compatibility and limits

agent-browser 0.33.0 is both the minimum supported version and the exact initial Chrome-verified baseline. Newer versions meet the version floor but require their own evidence before being classified as Verified. Microsoft Edge uses the same Chromium Provider path and remains Forwarded until representative evidence is recorded.

Panerelay operates only authorized tabs. It does not own browser-process features such as isolated profiles, launch-time proxy changes, or closing the user's browser process.