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

@steel-dev/cli

v0.3.1

Published

Steel CLI — this package installs the native binary. See https://steel.dev for details.

Readme

@steel-dev/cli

Steel CLI for browser automation, API tools, and agent workflows.

This package now integrates agent-browser directly into steel browser, so you can keep familiar browser commands while using Steel-native session lifecycle, auth, and endpoint handling.

Jump To

Install

curl -LsSf https://setup.steel.dev | sh

Or download directly from GitHub Releases.

Upgrading from npm

If you previously installed via npm i -g @steel-dev/cli:

npm update -g @steel-dev/cli   # auto-installs native binary
# Then optionally:
npm uninstall -g @steel-dev/cli
export PATH="$HOME/.steel/bin:$PATH"

Quick Start

Cloud mode (default)

steel login
steel browser start --session my-job
steel browser open https://example.com --session my-job
steel browser snapshot -i --session my-job
steel browser stop

Self-hosted endpoint

steel browser start --api-url https://steel.your-domain.dev/v1 --session my-job
steel browser open https://example.com --api-url https://steel.your-domain.dev/v1 --session my-job

Local runtime (localhost flow)

steel dev install
steel dev start
steel browser start --local --session local-job
steel browser open https://example.com --session local-job
steel browser stop
steel dev stop

Agent-Browser Integration

steel browser is directly backed by the vendored agent-browser runtime.

Steel-owned lifecycle commands:

  • steel browser start
  • steel browser stop
  • steel browser sessions
  • steel browser live

All other steel browser <command> calls are inherited from upstream runtime behavior and routed through Steel.

Migration from upstream agent-browser is typically command-prefix only:

  • before: agent-browser <command> ...
  • after: steel browser <command> ...

Read more:

Command Overview

| Group | Commands | | ------------------- | ------------------------------------------------------------------------------------- | | Quickstart | forge, run | | Browser lifecycle | browser start, browser stop, browser sessions, browser live | | Browser passthrough | steel browser <inherited-command> | | Browser profiles | profile import, profile sync, profile list, profile delete | | API tools | scrape, screenshot, pdf | | Local runtime | dev install, dev start, dev stop | | Account and utility | login, logout, config, settings, cache, docs, support, star, update |

For full flags and argument schemas, use the generated reference:

Endpoint Resolution

For browser lifecycle, browser passthrough bootstrap, and top-level API tools (scrape, screenshot, pdf), endpoint selection is deterministic.

Self-hosted precedence (highest to lowest):

  1. --api-url <url>
  2. STEEL_BROWSER_API_URL
  3. STEEL_LOCAL_API_URL
  4. browser.apiUrl in ~/.config/steel/config.json
  5. http://localhost:3000/v1

Cloud precedence:

  1. STEEL_API_URL
  2. https://api.steel.dev/v1

Attach-flag override rule:

  • If --cdp or --auto-connect is provided, Steel bootstrap injection is skipped and passthrough args are forwarded unchanged.

Output and Runtime Notes

  • steel scrape defaults to markdown-first output for token efficiency; use --raw for full JSON payload.
  • steel browser start and steel browser sessions emit display-safe connect URLs with sensitive query values redacted.
  • Browser command paths bypass auto-update checks for lower interactive latency.

Documentation Map

Primary docs:

Reference docs:

Agent skill: