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

openclaw-studio

v0.0.12

Published

Install OpenClaw Studio with a single command:

Vulnerabilities

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

Links

Git

Maintainers

gpickett00gpickett00

Keywords

Readme

OpenClaw Studio Installer CLI

Install OpenClaw Studio with a single command:

npx openclaw-studio

This downloads the OpenClaw Studio app into ./openclaw-studio, installs dependencies, runs a preflight checklist (Node/npm/OpenClaw config + gateway reachability hint), writes Studio connection settings when possible, and prints next steps.

The CLI also checks npm for newer openclaw-studio versions (cached for 12 hours). If your local CLI is stale, it automatically re-runs using openclaw-studio@latest before continuing.

Requirements

  • Node.js 18+
  • npm
  • OpenClaw Gateway running (Studio connects to the gateway over WebSocket)

Note: OpenClaw itself recommends Node 22+. The Studio installer can run on Node 18+, but you'll need Node 22+ to run the OpenClaw gateway.

Usage

Skip the npm confirmation prompt:

npx -y openclaw-studio

npx openclaw-studio

Options

  • --gateway-url <ws(s)://...>: override the gateway URL used for checks and Studio auto-configuration
  • --gateway-token <token>: override the token used for Studio auto-configuration
  • --no-write-settings: do not write ~/.openclaw/openclaw-studio/settings.json (or your configured OpenClaw state dir)

If no config is found and no gateway is reachable, the installer will optionally prompt you to enter a remote gateway URL/token so Studio is pre-configured.

Doctor

Troubleshoot gateway/config/settings issues without reinstalling Studio:

npx -y openclaw-studio doctor --check

Apply safe fixes (writes Studio settings to point at the chosen gateway URL/token):

npx -y openclaw-studio doctor --fix

Troubleshooting

  • Missing config: run openclaw onboard or set OPENCLAW_CONFIG_PATH to a valid openclaw.json.
  • Node version: ensure node -v is 18 or newer.
  • Gateway unreachable: ensure your gateway is running and reachable (default hint: ws://127.0.0.1:18789). If you use a remote gateway, you'll set the URL/token in Studio Settings.

Development

Override the source repo with:

[email protected]:your-org/your-repo.git npx openclaw-studio

Build the CLI with:

npm run build