Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
R

roke22/pisha

Independent directory — not the official site. Details below come from the project's public repository.

Teams of AI coding agents (Claude Code, Codex CLI, Grok CLI), each led by a coordinator, on any of your machines.

5 ★ measured · checked 2026-11-19

Before you install: command ownership unverified - shown for reference only · license MIT · link reachable

First step (reference only, ownership unverified): npx pisha-server # dashboard at http://127.0.0.1:7787

★ 5·updated 2026-11-18
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site

After install: how to tell it works

  1. What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
  2. One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
  3. If that does not work — This project has no troubleshooting notes. Search its issues for "install".

The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.

Star count
5 ★ · roke22/pisha · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-15 · last seen 2026-11-20 · seen 6× · listed by 1 sources
Score
score 103 · 5 ★ · 1 sources · repo
Install
see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository roke22/pisha;first catalogued 2026-11-15;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

Pisha: multi-agent Claude Code with a coordinator and a live dashboard

Excerpted from the repository README (abridged)

A coordinator agent that runs teams of Claude Code agents — fast, unattended, and visible live.
Leer en español · Website · Examples · Reference · Discussions · v0.0.12
Pisha gives Claude Code a coordinator: you tell it what you want, and it splits the work among a team of workers (other Claude Code sessions), follows their progress, approves their safe actions and only comes back to you for the decisions that matter.
A web dashboard keeps what needs you in one inbox, shows each team with its plan, and opens a whole team live, like a wall of terminals: what each agent is doing, what Claude is saying, and who is waiting for you. From there you also add your computers and open new sessions on them. Task boards, in step with GitHub Projects if you want, keep the work for people and agents alike.
Coordinators and workers can also be Codex CLI or Grok CLI sessions, mixed with Claude Code ones in the same team (experimental): see Codex CLI and Grok CLI.
Pisha is multi-agent orchestration for Claude Code: parallel Claude Code sessions on one machine or many, coordinated by another Claude Code session, with a self-hosted web dashboard and web terminal to run and watch them from any browser. It is open source (MIT), a single Node.js server with no dependencies, and installs as a Claude Code plugin.
## Quick start
bash
npx pisha-server # dashboard at http://127.0.0.1:7787
Only Node.js 22 is needed. Or with Docker: docker run -d -p 127.0.0.1:7787:7787 -v pisha-data:/data ghcr.io/roke22/pisha.
Create the first owner with the server token it prints (you will need an authenticator app for the codes), open Machines → Add machine and run the one command it shows on each computer where agents should work. That's it: the details, Docker and HTTPS are in steps 1 and 2 below.
### Just want to try it? Docker
One command starts the dashboard and a machine that runs Claude Code, in a single container. Everything it keeps (the dashboard's data, Claude Code's login, your projects) goes in one folder, deploy/demo/pisha.
1. Start it (the first time it builds the image, a few minutes):
bash
cd deploy/demo
docker-compose up -d # or: docker compose up -d
2. Read the server token, once it has started (some 20 seconds):
bash
cat pisha/data/server-token
It is also in the logs, in the Pisha demo box: docker-compose logs. It stays the same when the container restarts.
3. Create the first owner: open http://localhost:7787 and give the token, your name, email and a password; then add the code to your authenticator app. Then New team (the + next to Your teams in the sidebar) in the folder /pisha/projects with the subfolder demo, an example project with three personas. The first time, Claude Code asks in the session's terminal for its theme, your Claude login (/login) and whether you trust the folder; the login is kept for every later session.
To stop it, docker-compose down (the folder stays). To update it, git fetch --tags && git checkout "$(git tag --sort=-v:refname | head -1)" and then docker-compose up -d --build. Only this computer can reach it. More in the demo's README.
## What you can do with it
Build a feature across several repositories at once: the backend, the web app and the mobile app, each with its own worker, kept in step by the coordinator.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/roke22-pisha/)
Source
github · https://github.com/roke22/pisha
Browse by field
Open source
Traction
5 ★
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index