hivemind-agents 0.1.4 → 0.1.6
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 +17 -0
- package/dist/hivemind.mjs +81 -65
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -35,6 +35,19 @@ records goals, contracts, decisions and tasks in hivemind (tasks unassigned, wit
|
|
|
35
35
|
each teammate's agent can claim one by key. You can also add things yourself with `hivemind add` or
|
|
36
36
|
in the dashboard (`hivemind open`).
|
|
37
37
|
|
|
38
|
+
## When the plan changes direction
|
|
39
|
+
|
|
40
|
+
Plans change mid-hackathon. hivemind makes sure the old direction doesn't linger next to the new one:
|
|
41
|
+
|
|
42
|
+
- **New goals must say how they relate** to existing ones: they *replace* them, or are a *competing
|
|
43
|
+
proposal*. Competing goals are flagged to every agent ("the team hasn't picked one yet, ask the
|
|
44
|
+
user") until someone resolves them.
|
|
45
|
+
- Decisions and contracts can **replace** earlier ones, and agents are shown existing entries when
|
|
46
|
+
they add new ones so they can spot contradictions. The background extractor removes entries that
|
|
47
|
+
the work clearly abandoned.
|
|
48
|
+
- `hivemind review` (or the `plan_review` tool) has the model check the whole plan for contradictions
|
|
49
|
+
and suggest fixes (~15 s).
|
|
50
|
+
|
|
38
51
|
## How it works
|
|
39
52
|
|
|
40
53
|
```
|
|
@@ -54,6 +67,9 @@ in the dashboard (`hivemind open`).
|
|
|
54
67
|
new part of its transcript and pulls out the things teammates need: contracts, decisions and task
|
|
55
68
|
progress, each with a quote as evidence. Agents can also publish explicitly through MCP tools
|
|
56
69
|
(`contract_publish`, `decision_log`, `task_add`, `task_claim`, …), and they're told to for anything urgent.
|
|
70
|
+
- **Work doesn't go unrecorded.** Before an agent's first file edit, if it has no task in progress it's
|
|
71
|
+
asked to claim one (and shown the unclaimed tasks). After a turn that changed files, if neither the
|
|
72
|
+
agent nor the extractor recorded anything, it's reminded to update its task.
|
|
57
73
|
- **Updates arrive in seconds.** Typically 2–5 s from one agent's change to the other machine,
|
|
58
74
|
then shown at that agent's next tool call.
|
|
59
75
|
|
|
@@ -84,6 +100,7 @@ Same hooks and MCP tools, no npm needed. Use either the plugin or `npx … insta
|
|
|
84
100
|
hivemind status who's in the plan, last sync
|
|
85
101
|
hivemind plan print the shared plan
|
|
86
102
|
hivemind open live dashboard in your browser (and a form to add to the plan)
|
|
103
|
+
hivemind review check the plan for contradictions
|
|
87
104
|
hivemind add <goal|task|contract|decision|question> <key> <text> [--breaking]
|
|
88
105
|
hivemind doctor check that everything is wired up
|
|
89
106
|
hivemind disable turn hivemind off for this clone (hivemind enable to undo)
|