ClawTeam-OpenClaw: a fork that tells you not to install it from PyPI
ClawTeam fork fully adapted for OpenClaw — multi-agent swarm coordination with OpenClaw as the default agent
At a glance
- What is it?
- ClawTeam-OpenClaw is a Python CLI that spawns coding agents into their own git worktrees and coordinates them over the command line, with OpenClaw as the default agent. The repository contradicts itself in a few places worth knowing before you install: optional ZeroMQ and Redis extras against a comparison table that says it uses neither, twelve README files behind an eleven link language bar, and an install warning that stops mid sentence.
- Who is it for?
- This is a sensible default if you already run CLI coding agents and want them to fan out over real git branches rather than share one working tree. Two things to settle first.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- win4r/ClawTeam-OpenClaw1,475 ★ · +24
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| win4r/ClawTeam-OpenClaw | 1.5k | 1.5k |
24 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The install warning is the most useful paragraph and it stops mid sentence
The install step opens with a warning not to run either of the two obvious commands. `pip install clawteam` is called out because it installs the upstream PyPI version, which defaults to `claude` and lacks the OpenClaw adaptations this fork exists to add. `npm install -g clawteam` is called out because it installs an unrelated package that squats the name.
The first half of that warning is complete and actionable. The second is not: the sentence naming the name squatting package ends there, with no statement of what to do instead, and no follow up line. A reader who was about to install from npm is left with a prohibition and no alternative, at exactly the point where they need one.
What the page does show elsewhere is the sanctioned route. The Windows native path installs the checkout in editable form with `py -3 -m pip install -e .`, which is consistent with a project intended to be used from source rather than from an index.
Optional ZeroMQ and Redis extras contradict the comparison table
The table arguing for the project lists its infrastructure as a filesystem plus tmux, and lists Redis, message queues and databases as what other frameworks require. The manifest disagrees, or rather qualifies the table.
Two optional dependency groups exist alongside the five required packages. One is named `p2p` and pulls a ZeroMQ binding, and one is named `redis` and pins the Redis client. So the tool has both a message queue and a cache available to it, and the table describes the default rather than the ceiling.
The required set is small and ordinary: a terminal UI framework, a validation library, a console formatting library, a prompt library, a TOML reader that installs only below Python 3.11, and a Model Context Protocol package. The manifest also registers a second console entry point named `clawteam-mcp` alongside the main command, so a protocol server ships in the box, and neither the table nor the visible part of the page mentions it.
Release tags carry build metadata and one is formatted differently
The three releases are named after the fork's own suffix rather than the upstream project. The newest is a zero point three point zero with a build metadata suffix reading `openclaw2`, described as an upstream sync plus auto respawn hardening plus compatibility with a dated OpenClaw release. The one before it carries the same shape with `openclaw1`, and the oldest carries `openclaw.1`, with a dot where the other two have none.
That dot is the only structural difference between two tags that are otherwise the same series, and it means the three names do not sort or match consistently against each other. Build metadata after a plus sign is also ignored when versions are compared, so all of this decoration is invisible to any tool doing version arithmetic.
The manifest agrees with the newest tag down to the suffix, since its version field carries the same string, and it classifies the project at an alpha development status. The most recent push and the newest release share the same date, 2026-07-03, so at least the two are in step.
Windows drops to subprocess and the attach command still needs tmux
Platform support is described as a graceful degradation rather than a port. Linux and macOS keep the original tmux first workflow. Windows 10 and 11 are supported with an automatic fallback to a subprocess backend, and three specific concerns are routed through a shared compatibility layer so Unix only behaviour fails safely: task locking, process liveness checks, and signal registration.
The degradation is not complete, and the page is direct about the gap. The attach command still requires tmux, so on Windows the recommended way to watch a team is the board server instead, and anyone who wants the original workflow is pointed at WSL. Checking which backend was chosen is a single command, `clawteam config get default_backend`, which should print `subprocess` on Windows.
The prerequisite check is equally concrete, three version commands for Python, tmux and whichever agent is installed. Python 3.10 is the floor, and the install table gives a different command per platform for it, from the python.org installer on Windows to a versioned Homebrew formula on macOS.
Every worker gets a worktree, a session and an identity
The spawning model is the core of the tool, and the manual path shows all three objects a worker receives. A leader creates a team, then spawns named workers against tasks, and each worker is given its own git worktree, its own spawn backend session, and its own identity:
# Create a team
clawteam team spawn-team my-team -d "Build the auth module" -n leader
# Spawn workers — each gets a git worktree plus its own backend session
clawteam spawn --team my-team --agent-name alice --task "Implement OAuth2 flow"
clawteam spawn --team my-team --agent-name bob --task "Write unit tests for auth"
# Watch them work
clawteam board serve --port 8080
clawteam board attach my-team # Linux/macOS/WSL with tmuxThe comparison table calls this isolation, and specifies that it is real branches rather than containers or virtual environments. Coordination between workers runs through task and inbox commands that the page says are auto injected into each worker's prompt, which is why the workers report without being told the syntax. Monitoring has two forms, a tiled terminal view or a web interface on a port you choose.
Twelve README files sit behind an eleven link language bar
Human facing translation is extensive. The header carries a language bar linking eleven files: English, two Chinese variants, Japanese, Korean, French, Spanish, German, Italian, Russian and Brazilian Portuguese.
The repository root holds twelve README files. Both a `README_KO.md` and a `README_KR.md` are present, and only the first appears in the language bar, so two files claim Korean and one of them is unreachable from the page that is supposed to index them. Which one is current is not stated anywhere.
Alongside the human documentation the repository also ships documentation aimed at agents. There is a `CLAUDE.md`, a directory named for that assistant's configuration, a second directory named for agents in general, a skills directory, and a lock file for it. So the same project is described twice over, once for people reading a browser page and once for a coding agent that reads the checkout, and the translations will drift from the agent facing files as a matter of course.
Package metadata credits the upstream author and the fork's own URLs
The manifest's author field names the upstream organisation, with an email address, while every project URL in the same file points at the fork: homepage, repository and issue tracker all resolve to the fork's own repository. Installed metadata will therefore attribute the package to the upstream project while the links send you to the fork, which is the sort of mismatch that makes a support question land in the wrong tracker.
The license is declared twice, once as a text field and once as a classifier, both MIT, matching the license file at the root. The lint configuration sets a line length of 100 while also ignoring the rule that reports long lines, so the first setting documents intent and the second removes the check.
The same tree also carries an npm project, named for the website rather than the tool, at version 0.0.0, whose only scripts build and preview a site from a Vite config inside a website directory. Its presence is a fair warning about the namespace clash the install section is trying to head off, since a name squat on npm would not be the only package in this repository using that word.
Editorial conclusion
This is a sensible default if you already run CLI coding agents and want them to fan out over real git branches rather than share one working tree. Two things to settle first. Install from the repository, not from a package index, because the README says the indexed builds are the wrong code, and because the npm warning is truncated you cannot tell from the page what it would have told you to do instead. And on Windows, accept that the visual workflow is gone by default and use the board server or WSL. Read the manifest rather than the comparison table before you conclude the project has no queueing or cache options, because it ships both as extras.
Frequently asked questions
Can OpenClaw have multiple agents?
That is the shape this project is built around. OpenClaw is the default agent, a leader calls the spawn command to create workers, and each worker receives its own git worktree, its own spawn backend session and its own identity, with coordination running through task and inbox commands injected into each prompt.
What does ClawTeam-OpenClaw need before it will run?
Python 3.10 or newer and at least one CLI coding agent, with tmux required for the full visual workflow on Linux and macOS. On Windows tmux is optional because the subprocess backend is the default there, and `clawteam config get default_backend` is the command that confirms which one was chosen.
Why does ClawTeam-OpenClaw warn against installing clawteam from PyPI or npm?
The PyPI build is the upstream version, which defaults to `claude` and lacks the OpenClaw adaptations this fork adds. The npm warning names an unrelated package that squats the name, and that sentence ends without stating an alternative.
Does ClawTeam-OpenClaw need Redis or a message queue?
Not by default. The comparison table lists a filesystem and tmux as its infrastructure, but the manifest ships two optional dependency groups, one named `p2p` that pulls a ZeroMQ binding and one named `redis` that pins the Redis client.
How do I watch a team run on Windows?
The attach command still requires tmux, so the page directs Windows users to the board server for live monitoring instead, or to running the project inside WSL if they want the original terminal workflow back.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/win4r-clawteam-openclaw)Star history chart for your README
[](https://hysenlabs.com/projects/win4r-clawteam-openclaw)Was this useful?