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

@vibecodr/cli

v1.0.8

Published

The official Vibecodr CLI: hosted browser, hosted computer, capsule uploads, Pulse operations, and agent-client MCP setup under one command.

Downloads

3,400

Readme

Vibecodr CLI

npm

The official Vibecodr CLI. One package, one install command, one coherent surface for:

  • Hosted browser tools (render, screenshot, PDF, crawl, snapshot, ask).
  • Hosted computer tools (run, test, work follow, work submit, proof).
  • Capsule uploads (zip + image) into Pulse and the hosted MCP gateway.
  • Pulse lifecycle (setup, publish, list, get, status, run, archive, restore, create, deploy).
  • Adding Vibecodr to the apps people actually use: Codex, Cursor, VS Code, Windsurf, Claude Desktop, and Claude Code.
  • Direct OAuth login, device-code login, status, doctor, diagnostics.

Install

npm install -g @vibecodr/cli

This installs three bin entries that all point at the same dispatcher:

  • vibecodr — canonical name. The full unified command surface.
  • vibecodr-mcp — compatibility alias for users coming from @vibecodr/[email protected].
  • vc-tools — compatibility alias for users coming from @vibecodr/[email protected]. Produces byte-equivalent output to the standalone vc-tools binary on every hosted Agent Computer command.

You can also install the legacy tombstone package; it forwards to the same dispatcher:

npm install -g @vibecodr/vc-tools

Pin to a specific version (recommended for CI):

npm install -g @vibecodr/[email protected]

Quick start

If you are not sure what you need yet, start here:

vibecodr status
vibecodr doctor

The default human experience is intentionally simple: the CLI should tell you what is connected, what is missing, and the next command to run. The underlying surfaces stay explicit for scripting, debugging, and release verification.

# 1. Sign in for publishing, uploads, Pulses, and MCP Gateway tools.
vibecodr login

# 2. Add Vibecodr to Codex. Other supported apps: Cursor, VS Code, Windsurf,
#    Claude Desktop, and Claude Code.
vibecodr install codex

# 3. Set up the hosted Agent Computer when you want browser/computer work.
vibecodr start
vibecodr browser screenshot https://example.com --out ./proof

Power users and automation should prefer the explicit surfaces and stable JSON:

vibecodr mcp tools --json --non-interactive
vibecodr mcp call get_account_capabilities --input-json '{}' --json --non-interactive
vibecodr status --json --non-interactive

Surfaces

The CLI talks to two hosted endpoints. Every command targets exactly one of them:

| Endpoint | Commands | |---|---| | tools.vibecodr.space | start, setup, login agent, logout agent, agent, connect, try, browser, computer, work, proof, jobs, artifacts, usage, limits, grants, retention, scheduled-qa, plans, dashboard, inspect | | openai.vibecodr.space/mcp | login mcp, logout mcp, mcp tools, mcp call, tools, call, feedback, upload, pulse, pulse-setup, pulse-publish, whoami | | Shared local diagnostics/install | status, doctor, install, uninstall, config |

CLI auth is independent of the auth your editor (Codex, Cursor, VS Code, Windsurf, Claude Desktop, Claude Code) negotiates with the gateway; each client owns its own session. vibecodr login defaults to the MCP Gateway lane. Use vibecodr login agent for the hosted Agent Computer credential lane.

Migrating from @vibecodr/[email protected] or @vibecodr/[email protected]

You should not need to change anything. Every bin name, env var prefix (VC_TOOLS_*, VIBECDR_MCP_*), keyring service ID (@vibecodr/vc-tools, @vibecodr/mcp), config dir, Cloudflare worker route, JWT claim, page slug, and durable API key remains addressable. See MIGRATION.md for the three-section breakdown.

Documentation

Repository status

This repository is the unified home of the Vibecodr CLI. It ships:

  • The published npm package @vibecodr/cli.
  • The Cloudflare worker source for tools.vibecodr.space (in src/hosted/) and the matching D1 migrations (in migrations/).

Apache-2.0 licensed.