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

berry-claw

v0.1.0-alpha.0

Published

AI agent product built on berry-agent-sdk

Readme

berry-claw 🐾

A local-first AI agent product built on berry-agent-sdk — multi-provider, multi-agent, with a built-in observability dashboard.

eating our own dog food


Install

npm install -g berry-claw

Or one-shot via npx:

npx berry-claw

Requires Node.js ≥ 20.


Quick start

# 1. First-time setup (creates ~/.berry-claw/, asks about optional deps)
berry-claw setup

# 2. Launch server + Web UI
berry-claw

# 3. Open http://localhost:3210 and add a provider + agent in Settings.

That's it. No config file to hand-edit; the Web UI walks you through it.


CLI

| Command | What it does | |---|---| | berry-claw | Start server + Web UI (default) | | berry-claw start | Same as above (explicit) | | berry-claw setup | First-time setup wizard | | berry-claw doctor | Environment self-check | | berry-claw install browser | Install the browser runtime for the browser tool | | berry-claw version | Print version | | berry-claw help | Show help |

Environment

| Variable | Default | Meaning | |---|---|---| | PORT | 3210 | HTTP port | | BERRY_CLAW_HOME | ~/.berry-claw | Data directory (agents, sessions, observe DB, config) |


What's inside

  • Multi-provider: Anthropic / OpenAI-compatible. Route requests by model name.
  • Multi-agent: Create/switch/inspect agents with their own tools, skills, and workspace.
  • Chat UI: Streaming WebSocket, tool-call view, session history.
  • Observability: Cost, cache hit-rate, guard decisions, compaction timeline, turn-level inference detail.
  • Settings UI: Provider + agent + credentials management.

Optional capabilities

Some features need extra runtime assets that aren't shipped by default:

| Capability | Install | Why it's optional | |---|---|---| | Browser tool | berry-claw install browser | Downloads Chromium (~150 MB). Only needed if you let agents drive real pages. |

berry-claw doctor will tell you what's missing.


SDK integration

berry-claw is a thin product shell over berry-agent-sdk:

| SDK Package | Usage | |---|---| | @berry-agent/core | Agent loop, sessions, providers, retry/timeout, compaction | | @berry-agent/tools-common | Built-in tools (read/write/edit/shell/search/web/browser) | | @berry-agent/observe | createObserveRouter() — drops in the whole observe REST API | | @berry-agent/safe | compositeGuard(directoryScope, denyList) for tool-guard policy | | @berry-agent/mcp | Wire MCP servers as Berry tools (shared + per-agent) | | @berry-agent/memory-file | File-system memory provider for agent long-term context | | @berry-agent/models | Unified model registry + provider tier resolution | | @berry-agent/team | Multi-agent orchestration (worklist, roles, leader) |


Data layout

~/.berry-claw/
├── config.json          # providers + agents + credentials (mode 0600)
├── observe.db           # SQLite: cost, cache, guard, turns, inferences
├── agents/
│   └── <agent-id>/      # each agent's isolated workspace
└── sessions/
    └── <agent-id>/*.json

Develop

From a clone of the repo:

npm install
npm run dev               # backend (3210) + Vite dev server (3211)
npm test                  # unit tests

Run the built CLI against the local code:

npm run build
node dist/cli.js doctor

Status

Alpha. Functional but rough edges. Primary purpose right now is SDK validation.