Repository navigation
Pisha v0.0.11
SquadraHQ is now Pisha. 0.0.11 adds task boards that stay in step with GitHub Projects, a new look across the dashboard, and an install in one command with npx pisha-server or Docker.
SquadraHQ is now Pisha
New name, new logo, new repository (roke22/pisha). Everything is renamed, the code included: pisha-server, pisha-host, the pisha plugin, PISHA_* variables. This is a clean break: see Updating from 0.0.10 below.
Task boards
- A board keeps the company's tasks, for people and agents alike, in columns or as a list, with types, labels, priority, due date, comments, history and an id such as
SQ-12. - Each column can be a step of the flow: who handles it (a team's coordinator, one agent or a person), what to do there, and where a task goes when it is done or isn't acceptable.
- Giving a task to an agent tells nobody by itself. Hand out as many as you want, then Notify the teams: each coordinator gets one message with its team's new tasks.
- Subtasks up to 8 levels deep, a trash to restore deleted tasks, and agents that read and update the board through the plugin, filtered by the server.
In step with GitHub
- Connect a board to a GitHub project and the two follow each other both ways: columns, agents, types, labels, sub-issues and comments, edited or deleted comments included.
- A task's people are the issue's assignees, by the GitHub user each person sets in their profile.
- Pull requests on their tasks: a PR that names a task (
SQ-12in its title, branch or description) or closes its issue shows on the task with its state and review. Merging it moves the task to Done, unless the board says not to. - GitHub is asked only while the board is in use, and nothing that comes from it tells an agent until you say so.
A new look
- Built on affectUI's free components (MIT), with a new font and colours, in light and dark.
- Inbox: each entry a card with its state, a Running tab with who is at work and a live clock for each one, and counts that update as things change.
- Org chart: each team a group, its coordinator first and its workers below, each agent with what it is on and for how long, what it does now and how full its context is. Work handed to a worker runs down to it as a light, and pressing an agent opens its terminal.
- Machines in a grid of cards, with their details, installed agents, folders and limits in sections.
Install in one command
npx pisha-serveror with Docker:
docker run -d --name pisha -p 7787:7787 -v pisha-data:/data ghcr.io/roke22/pishaIts data lives in ~/.pisha (or /data in the container). Cloning the repository still works too.
Updating from 0.0.10
This is a clean break. A server or a machine of 0.0.10 or earlier is installed again, not upgraded, and what SquadraHQ kept is not brought over.
- Start the new server with
npx pisha-serveror the Docker image, and create the first owner with the token it prints. - On each machine, remove the old one (
squadra-host service remove,squadra-host forget --close-sessions,claude plugin uninstall squadra@squadra && claude plugin marketplace remove squadra), then add it again from Machines → Add machine.
From now on, updating means npx pisha-server@latest (or docker pull ghcr.io/roke22/pisha), then pisha-host update on each machine.