@giladbarnea/pi-simple-team 1.0.32 → 1.0.33

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 CHANGED
@@ -92,7 +92,7 @@ The command opens an overlay rolling recent statuses, messages, and a separate e
92
92
 
93
93
  ### 🏋️ Woken up when needed. Works freely otherwise.
94
94
 
95
- Tokens, intelligence and time are never wasted on busy-polling for messages.
95
+ **Tokens, intelligence and time are never wasted on busy-polling for messages.**
96
96
 
97
97
  Instead, `pi-simple-team` pushes messages to the recipients.
98
98
 
@@ -109,6 +109,8 @@ This is both efficient and effective:
109
109
 
110
110
  ### 🟢 Statuses everyone can see.
111
111
 
112
+ For free, at any time. Like setting a Slack status.
113
+
112
114
  Teammates publish a one-liner:
113
115
 
114
116
  > <span style="color:grey">implementer  </span> Done, 89 tests green, awaiting review.
@@ -119,74 +121,81 @@ Your main agent calls `teamstatus` and understands exactly what is going on. Mai
119
121
 
120
122
  ### 🌡️ Context window self-awareness
121
123
 
124
+ **The team manages its own context:**
125
+
122
126
  Teammates know how much free context they have left.
123
127
 
124
128
  Main agent knows its own and everyone else's too.
125
129
 
126
130
  They will hand off work autonomously when it's time to say goodbye.
127
131
 
128
- You can stop babysitting everyone's context window.
132
+ You can stop babysitting context windows.
129
133
 
130
134
  ### 📣 Interrupts, when justified.
131
135
 
132
136
  > _Situation: Late afternoon. Team finished production hotfix and started wrap up. There is one problem though._
133
137
 
134
- - 17:32:00: Security scout spots a private SSH key not covered by `.gitignore`.
135
- - 17:32:01: Release teammate sets status: _Ran `git add .`, preparing commit and push._
136
- - 17:32:02: Scout immediately interrupts. Key never leaves the machine. Developer keeps their job.
138
+ - 17:32:00: `security-guard` spots a private SSH key not covered by `.gitignore`.
139
+ - 17:32:01: `release-owner` sets status: _Ran `git add .`, preparing commit and push._
140
+ - 17:32:02: `security-guard` immediately interrupts `release-owner`. Key never leaves the machine. Developer keeps their job another day 👍
137
141
 
138
142
  ### 📡 Live, zero-cost observability
139
143
 
140
- Your main uses `teamlog` when it needs to understand the chain of events in high granularity: a timestamped, filterable timeline of messages, tool calls, and lifecycle events.
144
+ Your main uses `teamlog` when it needs to understand the chain of events in high granularity.
145
+
146
+ Provides main a timestamped, filterable, append-only record of the team’s messages, tool calls, and lifecycle events.
141
147
 
142
- ### 🪟 Herdr Mode
148
+ ### 🌅 Herdr Support
143
149
 
144
- `pi-simple-team` can give each teammate a Pi session in its own [Herdr](https://herdr.dev) pane. Just ask your main agent to do that.
150
+ `pi-simple-team` can open a teammate direct Pi session in a dedicated [Herdr](https://herdr.dev) pane. Just ask your main agent to do that.
145
151
 
146
152
  - Live view of the room.
147
153
  - Talk directly with teammates.
148
154
 
155
+ I recommend starting with “Captain here”. Feels good and the surprise on their faces is priceless.
156
+
149
157
  ### 🧱 Teammates are durable Pi sessions.
150
158
 
151
- A teammate is a normal Pi session with a team attachment.
159
+ A teammate is just a Pi session with a team attachment.
152
160
 
153
- This means teammates survive shutdown, whole team or member by member.
161
+ This means **teammates (and thus, teams) survive shutdown.**
154
162
 
155
- Have a teammate do work, exit Pi entirely, come back tomorrow in a brand-new session: main wakes that same teammate into the new conversation, everything it learned intact.
163
+ Have a teammate do work, exit Pi entirely, come back tomorrow in a brand-new session, and ask main to get you that teammate by its Pi session id. Everything it learned stays intact.
156
164
 
157
165
  You can even `/resume` a teammate session directly if you ever want a cozy one-on-one.
158
166
 
159
- The full lifecycle and persistence rules live in [ARCHITECTURE.md](ARCHITECTURE.md).
160
-
161
- ## 🪾 Teams all the way down (optionally)
167
+ ## 🪾 It’s teams all the way down (optionally)
162
168
 
163
- Tell main you want to give a teammate the ability to manage its own team(s).
169
+ Tell main you want to **have a teammate manage its own team(s).**
164
170
 
165
- This is a powerful technique to create a new layer of context breathing room.
171
+ This is a powerful technique to create a **separate layer of context.**
166
172
 
167
173
  That teammate will spawn, steer and observe its own team(s) without costing tokens to its siblings or parent.
168
174
 
169
- The tradeoff, like any higher-order delegation, is reduced control: you are moved one level further away from the action.
175
+ The tradeoff, like any higher-order delegation, is reduced control: you are moved one level further away from the trenches.
170
176
 
171
177
  This is opt-in: teammates by default can't create teams.
172
178
 
179
+ This technique plays even nicer if your main assumes the first mate[^1] or captain[^2] rank.
180
+
173
181
  ---
174
182
 
175
183
  ## 🧬 Graphs engineer themselves
176
184
 
177
- **Because** it does nothing special, `pi-simple-team` can construct any team graph you need:
185
+ **Because** it does nothing special, `pi-simple-team` can **construct any agentic graph you need:**
178
186
 
179
- You:
187
+ You tell main:
180
188
  > **Team goal:**
181
- > 1. Map all customer–product money streams in the database.
182
- > 2. Feed this knowledge into the harness.
183
- > 3. Prove the data analysis agent passes the new evals.
189
+ > 1. Map the database for all customer ⟷ purchases money streams.
190
+ > 2. Feed the new knowledge into the memory layer.
191
+ > 3. Make the data analysis agent pass the new purchases evals.
184
192
  >
185
193
  > **Note:**
186
- > - #1 and #3 are _saturation loops._ Stop only when you can't find anything new.
187
- > - Let teammates #1 and #3 create their own teams to loop until task is complete.
194
+ > - #1 is a **saturation loop.** Stop only when you can't find anything new.
195
+ > - #3 is a **hill-climbing loop.** Stop only the evals are green.
196
+ > - Teammates #1 and #3 create their own teams to loop until task is complete.
188
197
 
189
- That prompt gives you this graph:
198
+ That prompt creates this graph:
190
199
 
191
200
  ![The team graph: 1-map (Scout and Devil’s advocate) feeding subagent dispatch, feeding 3-eval (Engineer and Performance watcher)](screenshots/team-graph.png)
192
201
 
@@ -226,7 +235,13 @@ Kept minimal:
226
235
  **Functional:**
227
236
 
228
237
  - [x] Resume all or selected teammates from a dormant team.
229
- - [x] Add new teammates after a team has spawned.
238
+ - [x] Add teammates after a team has spawned.
230
239
  - [x] Let opted-in teammates create and manage teams of their own.
231
- - [ ] Main forces `/compact` on select teammate.
240
+ - [x] Remove teammates from a team.
241
+ - [ ] Main triggers `/compact` on select teammate.
232
242
  - [ ] Teammates auto-reminded to hand off on low context.
243
+
244
+ ---
245
+
246
+ [^1]: `skills/ai-to-ai/references/ranks/firstmate.md`
247
+ [^2]: `skills/ai-to-ai/references/ranks/captain.md`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@giladbarnea/pi-simple-team",
3
- "version": "1.0.32",
3
+ "version": "1.0.33",
4
4
  "description": "A flat, live team of Pi agents.",
5
5
  "keywords": [
6
6
  "pi-package",
Binary file