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

@adityabelgaonkar/browsy

v0.1.2

Published

Connect terminal MCP agents to your existing Chrome session locally.

Vulnerabilities

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

Links

Git

Maintainers

adityabelgaonkaradityabelgaonkar

Keywords

chromemcpbrowseragentsnative-messaging

Readme

Browsy CLI

Connect MCP terminal agents to your existing authenticated Chrome session through a local Native Messaging host. macOS, Linux, Windows 10/11, Node.js 22.12+, MIT licensed.

Install Browsy in Chrome, then install the companion and connect your agent:

npm install -g @adityabelgaonkar/browsy
browsy setup --agent codex

Chrome stays open and signed into your websites. Built-in sidebar chat works without this CLI. The source repository also documents unpacked extension installation.

From the repository root:

pnpm install --frozen-lockfile
pnpm build
node packages/cli/dist/index.js setup --agent codex

On Windows use PowerShell and Windows Node.js, not WSL.

Load apps/extension/dist unpacked in Chrome. Setup registers the bridge and adds its MCP server to the chosen agent. Use --agent claude or --agent opencode instead; start a new agent session afterward. The extension reconnects automatically. See the repository quick start.

After building:

npm install -g ./packages/cli
browsy setup --agent codex

For another MCP client, browsy setup prints configuration to add manually.

| Command | Purpose | | ----------- | --------------------------------------------------------------------------------- | | setup | Register the bridge and configure the selected agent with --agent | | install | Register the native host and print Codex, Claude Code, and OpenCode configuration | | doctor | Check executable paths, registration, permissions, and extension connection | | config | Print agent configuration again | | mcp | Start the stdio MCP server | | uninstall | Remove this installation's host registration and configuration |

Use --home DIRECTORY consistently to select a bridge home (default ~/.agent-native). setup and install support --extension-id, --browser, --chrome-path, and --manifest-dir. setup, install, doctor, config, and uninstall support --json.

--agent-config FILE selects a Claude Code or OpenCode configuration file. Existing JSON/JSONC settings and OpenCode comments are preserved; changed existing files receive a backup. Codex uses its own CLI to register the server. Running without --agent leaves agent settings untouched.

The bundle includes runtime dependencies. Chrome starts the host with recorded absolute executable paths; no separate daemon or public network control endpoint is needed. Reinstall after moving the bundle or changing the recorded Node installation. Browser requests interrupted after sending are never replayed automatically.