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

@teamclaws/teamclaw

v2026.4.3-2

Published

OpenClaw virtual software team orchestration plugin

Downloads

911

Vulnerabilities

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

Links

Git

Maintainers

topcheertopcheer

Keywords

openclawpluginteamclawmulti-agentorchestrationvirtual-teamsdlcmulti-role

Readme

@teamclaws/teamclaw

TeamClaw is an OpenClaw plugin that turns multiple roles into a collaborative virtual software team.

It supports:

  • controller / worker modes
  • externally registered workers
  • adaptive kickoff planning for medium/complex work, with per-role assessments before task creation
  • clarifications, workspace browsing, controller UI visibility, and a matching desktop client
  • Git-based collaboration
  • on-demand worker provisioning with process, docker, and kubernetes

Install

For the easiest guided setup, run:

npx -y @teamclaws/teamclaw install

The guided installer automatically uses OpenClaw's break-glass install flag for TeamClaw, because TeamClaw legitimately needs host orchestration capabilities that the built-in scanner marks as critical.

This installer can:

  • install/update the TeamClaw plugin in OpenClaw
  • detect your local openclaw.json
  • let you choose the installation mode
  • support dedicated worker-only installs with --install-mode worker
  • let you choose a model from the models already defined in OpenClaw
  • let you choose the OpenClaw workspace directory
  • default TeamClaw to a dedicated teamclaw agent/workspace instead of reusing main
  • copy the effective host model into the dedicated TeamClaw agent config when independent mode is used
  • bootstrap TeamClaw auth profiles from the host OpenClaw auth store when available
  • prefill Docker/Kubernetes provisioning with the published TeamClaw runtime image
  • prefill Docker workspace persistence with a named volume and Kubernetes persistence with a PVC name

By default, guided install now uses an independent TeamClaw agent/workspace layout:

  • agent:teamclaw:* sessions
  • sibling workspace such as ~/.openclaw/workspace-teamclaw

In practice, this means TeamClaw keeps its own agent state, workspace, and auth-profile copy instead of reusing the host main agent. Use this default unless you explicitly need legacy compatibility with a shared main workspace.

For advanced compatibility only, you can force the legacy shared-main layout:

npx -y @teamclaws/teamclaw install --agent-mode main

If you only want to install the plugin manually, use:

openclaw plugins install --dangerously-force-unsafe-install @teamclaws/teamclaw

If you want to force the ClawHub package path, use:

openclaw plugins install --dangerously-force-unsafe-install clawhub:@teamclaws/teamclaw

Then enable and configure TeamClaw in your openclaw.json.

The published TeamClaw runtime image also preinstalls the clawhub CLI, so containerized workers can discover and install skills from ClawHub without an extra bootstrap step.

Maintainer release flow

For maintainers, TeamClaw now uses two release paths:

  1. npm package — published by GitHub Actions via .github/workflows/teamclaw-plugin-npm-release.yml
  2. ClawHub code plugin + bundled skills — published manually from the CLI

The npm publish workflow runs automatically when:

  • a tag matching v* is pushed
  • or relevant package files change on main (src/**, .github/workflows/teamclaw-plugin-npm-release.yml, scripts/sync-teamclaw-plugin-manifest.mjs, scripts/teamclaw-package-check.mjs, scripts/teamclaw-npm-publish.sh)

It also supports workflow_dispatch for a specific commit SHA on main.

Before the first real npm publish, GitHub must already be configured for npm trusted publishing with the npm-release environment and this workflow file.

Before either release path, sync and validate the generated plugin manifest:

npm --prefix src run manifest:sync
npm --prefix src run release:check

Preview the ClawHub release commands without publishing:

npm --prefix src run release:clawhub:dry-run

When ready to publish to ClawHub, log in first and then run:

clawhub login
bash scripts/teamclaw-clawhub-release.sh --publish

The ClawHub release helper publishes the @teamclaws/teamclaw code plugin from src/ and then publishes only the bundled skills under src/skills/. Update each skill's frontmatter version: in src/skills/*/SKILL.md before a real publish if that skill changed.

Recommended first setup

For a first-time setup, the safest path is:

  1. Start with single-host process provisioning
  2. Validate the workflow with a small smoke-test task
  3. Expand to external workers, Docker, or Kubernetes after the basics are working

When on-demand provisioning is enabled, TeamClaw now treats controller startup as a readiness phase, not just a process-up check. During that warm-up, /api/v1/health returns a non-OK status until the controller has verified writable runtime paths and successfully brought the configured startup worker roles online. If workerProvisioningRoles is empty, startup readiness defaults to waiting for a warm developer worker.

Documentation