@giladbarnea/pi-simple-team 1.0.1 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +98 -27
- package/package.json +3 -1
- package/screenshots/1.png +0 -0
- package/screenshots/2.png +0 -0
package/README.md
CHANGED
|
@@ -1,11 +1,26 @@
|
|
|
1
|
+
<div align="center">
|
|
2
|
+
|
|
1
3
|
# pi-simple-team
|
|
2
4
|
|
|
3
5
|
> **The team extension with no features.**
|
|
4
6
|
|
|
5
|
-
|
|
7
|
+
[](https://github.com/earendil-works/pi)
|
|
8
|
+
[](https://www.npmjs.com/package/@giladbarnea/pi-simple-team)
|
|
9
|
+
[](https://github.com/giladbarnea/pi-simple-team/actions/workflows/test.yml)
|
|
10
|
+
[](LICENSE)
|
|
11
|
+
[](https://www.typescriptlang.org/)
|
|
12
|
+
[](https://bun.sh/)
|
|
13
|
+
|
|
14
|
+
**No roles. No org chart. No mailboxes. No routing rules.**
|
|
6
15
|
|
|
7
16
|
`pi-simple-team` spawns a flat team of Pi agents that can all talk to each other, like the responsible adults they are, **and then stays out of the way.**
|
|
8
17
|
|
|
18
|
+
</div>
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
|
|
9
24
|
## Why
|
|
10
25
|
|
|
11
26
|
The best work I've ever done happened in a small room with a few capable people, building something together.
|
|
@@ -14,53 +29,77 @@ Yell out "has anyone figured out the auth service yet?" instead of filing a "req
|
|
|
14
29
|
|
|
15
30
|
Tap the person next to you and ask them to grind you on your idea.
|
|
16
31
|
|
|
17
|
-
|
|
32
|
+
**That's the whole design. Not a swarm, not a company. *A room.***
|
|
33
|
+
|
|
34
|
+
## Using `pi-simple-team`
|
|
35
|
+
|
|
36
|
+
Ask your main agent for a team.
|
|
37
|
+
|
|
38
|
+
**Throw a team at something important.**
|
|
39
|
+
|
|
40
|
+
**You:** "Create an implementer–reviewer team to complete `PLAN.md`."
|
|
41
|
+
**Main:** "Created the pair. They'll work through it together; they'll let me know when they're done."
|
|
42
|
+
|
|
43
|
+
**Follow the breach wherever it leads.**
|
|
18
44
|
|
|
19
|
-
|
|
45
|
+
**You:** "Find how the model got into our systems and trace everything it touched."
|
|
46
|
+
**Main:** "Created an eight-agent incident team. They're tracing the intrusion from different angles, sharing new leads as they surface. The net will tighten around the model and take the shape of the blast radius."
|
|
47
|
+
|
|
48
|
+
<br>
|
|
49
|
+
|
|
50
|
+

|
|
51
|
+
|
|
52
|
+
<div align="center"><em><code>pi-simple-team</code> in the TUI.</em></div>
|
|
20
53
|
|
|
21
54
|
## The mechanics
|
|
22
55
|
|
|
23
|
-
The team is *live*, *dynamic*, and *scales* in proportion to the task's complexity.
|
|
24
56
|
|
|
25
|
-
It doesn't force itself into a pre-existing box. It maps itself to the shape of the problem space.
|
|
26
57
|
|
|
27
|
-
|
|
58
|
+
### Push, not pull.
|
|
28
59
|
|
|
29
|
-
|
|
60
|
+
- ✔ No inbox to forget.
|
|
61
|
+
- ✔ no polling to exhaust your context window.
|
|
30
62
|
|
|
31
|
-
|
|
63
|
+
*{screenshot of Codex filling up the entire visible chat with countless* `Waiting agents to finish...`*}*
|
|
32
64
|
|
|
33
|
-
|
|
65
|
+
### Messages arrive without breaking stride.
|
|
34
66
|
|
|
35
|
-
|
|
67
|
+
- ⚡ Sub-second, when the recipient is idle.
|
|
68
|
+
- 🏎️ The moment the current bout of work ends, when busy.
|
|
36
69
|
|
|
37
|
-
- Sub-second, when the recipient is idle.
|
|
38
|
-
- The moment the current bout of work ends, when busy.
|
|
39
70
|
|
|
40
|
-
#### Interrupts, when the situation calls for it.
|
|
41
71
|
|
|
42
|
-
|
|
72
|
+
### Statuses everyone can see.
|
|
43
73
|
|
|
44
|
-
|
|
74
|
+
Teammates publish a one-liner:
|
|
45
75
|
|
|
46
|
-
|
|
76
|
+
- "Done, 89 tests green, awaiting review".
|
|
77
|
+
- "Reading implementation, will finalize review in a few minutes"
|
|
47
78
|
|
|
48
|
-
|
|
79
|
+
Your main agent calls `teamstatus` and understands exactly what's going on without asking and cluttering the teammates' context.
|
|
49
80
|
|
|
50
|
-
|
|
81
|
+
### Interrupts, when the situation calls for it.
|
|
51
82
|
|
|
52
|
-
|
|
83
|
+
*Team has finished a production hotfix and started to wrap up.*
|
|
53
84
|
|
|
54
|
-
|
|
85
|
+
- Security scout spots a private SSH key not covered by `.gitignore`.
|
|
86
|
+
- At the same time, Release teammate sets status: "Ran `git add .`, preparing commit and push."
|
|
87
|
+
- Scout immediately interrupts them. Key never leaves the machine. Developer keeps their job.
|
|
55
88
|
|
|
56
|
-
One shared briefing, an individual prompt per teammate. Flat by default; if the task wants a reviewer gate or a lead, your main agent prompts it into being — that's a sentence, not a framework.
|
|
57
89
|
|
|
58
|
-
## Tools
|
|
59
90
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
91
|
+
### Complete observability by design.
|
|
92
|
+
|
|
93
|
+
The main agent can access one exhaustive, **timestamped history** of tool calls, messages, and lifecycle events, **recorded by the harness itself.**
|
|
94
|
+
|
|
95
|
+
Main can filter and page that shared timeline on demand.
|
|
96
|
+
|
|
97
|
+
Useful for tracing a failure *across* teammates—without asking anyone to reconstruct it from memory.
|
|
98
|
+
|
|
99
|
+
<br>
|
|
100
|
+
|
|
101
|
+

|
|
102
|
+
<div align="center"><em>Visual representation of the team log.</em></div>
|
|
64
103
|
|
|
65
104
|
## Install
|
|
66
105
|
|
|
@@ -68,4 +107,36 @@ One shared briefing, an individual prompt per teammate. Flat by default; if the
|
|
|
68
107
|
pi install npm:@giladbarnea/pi-simple-team
|
|
69
108
|
```
|
|
70
109
|
|
|
71
|
-
|
|
110
|
+
|
|
111
|
+
|
|
112
|
+
## Tools
|
|
113
|
+
|
|
114
|
+
|
|
115
|
+
Kept minimal:
|
|
116
|
+
|
|
117
|
+
|
|
118
|
+
| Role | For | Tools |
|
|
119
|
+
| -------------- | -------------- | ----------------------------- |
|
|
120
|
+
| **Main agent** | Team lifecycle | `team_spawn`, `team_shutdown` |
|
|
121
|
+
| | With team | `teamsend` |
|
|
122
|
+
| | On team | `teamstatus`, `teamlog` |
|
|
123
|
+
| **Teammates** | With teammates | `teamsend` |
|
|
124
|
+
| | With main | `teammain` |
|
|
125
|
+
| | For everyone | `teamstatus` |
|
|
126
|
+
|
|
127
|
+
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
|
|
131
|
+
|
|
132
|
+
## Roadmap
|
|
133
|
+
|
|
134
|
+
|
|
135
|
+
|
|
136
|
+
### User involvement track
|
|
137
|
+
|
|
138
|
+
Slash commands for:
|
|
139
|
+
|
|
140
|
+
- [ ] 💠 Live control panel.
|
|
141
|
+
- [ ] 👋 Joining and steering teams.
|
|
142
|
+
- [ ] 🪄 Spawning teams directly.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@giladbarnea/pi-simple-team",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"description": "A flat, live team of Pi agents.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -23,6 +23,8 @@
|
|
|
23
23
|
"files": [
|
|
24
24
|
"*.ts",
|
|
25
25
|
"render-support",
|
|
26
|
+
"screenshots/1.png",
|
|
27
|
+
"screenshots/2.png",
|
|
26
28
|
"README.md",
|
|
27
29
|
"LICENSE"
|
|
28
30
|
],
|
|
Binary file
|
|
Binary file
|