@loompad/cli 1.2.3 → 1.2.4
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/CHANGELOG.md +14 -0
- package/README.md +10 -0
- package/dist/cli/index.js +26 -3
- package/dist/cli/index.js.map +1 -1
- package/dist/core/orchestra.d.ts +1 -1
- package/dist/core/orchestra.js +7 -2
- package/dist/core/orchestra.js.map +1 -1
- package/dist/daemon/client.d.ts +3 -0
- package/dist/daemon/client.js +3 -0
- package/dist/daemon/client.js.map +1 -1
- package/dist/daemon/routes/project-team.js +17 -0
- package/dist/daemon/routes/project-team.js.map +1 -1
- package/dist/daemon/runner.js +22 -9
- package/dist/daemon/runner.js.map +1 -1
- package/dist/daemon/team-coordinator.d.ts +1 -1
- package/dist/daemon/team-coordinator.js +2 -2
- package/dist/daemon/team-coordinator.js.map +1 -1
- package/dist/daemon/team.d.ts +33 -0
- package/dist/daemon/team.js +48 -0
- package/dist/daemon/team.js.map +1 -1
- package/dist/web/app.css +8 -0
- package/dist/web/app.js +44 -1
- package/dist/web/app.js.map +2 -2
- package/docs/release-notes/v1.2.4.md +13 -0
- package/docs/teams.md +3 -0
- package/package.json +1 -1
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
## Loom 1.2.4: two machines, one goal, set up in one step
|
|
2
|
+
|
|
3
|
+
### Set up team auto-orchestration in one step
|
|
4
|
+
- **`loom team auto`** checks whether goals can split across your teammates' machines here. It says which of their agents a goal would get, and what's missing.
|
|
5
|
+
- **`loom team auto on`** does the setup:
|
|
6
|
+
- shares the project;
|
|
7
|
+
- writes `loom.team.json` if the repo has none (commit and merge it);
|
|
8
|
+
- turns on your machine's shared runner, so teammates' goals can use your agents too.
|
|
9
|
+
- **The Team tab** shows the same status on a **Two machines, one goal** card, with a **Turn on** button.
|
|
10
|
+
|
|
11
|
+
### Steadier on a teammate's machine
|
|
12
|
+
- **A teammate's task no longer fails to commit.** Loom on their machine was saving its own end-of-turn checkpoint at the same moment and could undo the task's changes. The task's commit is now built separately, so nothing interferes.
|
|
13
|
+
- **Follow-ups reach the teammate.** When your orchestrator asks a teammate's task for more ("also fix the test"), their machine now gets that request on top of its earlier work, instead of the whole task again.
|
package/docs/teams.md
CHANGED
|
@@ -171,6 +171,9 @@ machine. Your orchestrator sees each teammate's agents as `team:<agent>` workers
|
|
|
171
171
|
self-contained tasks go to a teammate, tightly coupled ones stay with you. Nobody
|
|
172
172
|
on their side clicks anything.
|
|
173
173
|
|
|
174
|
+
`loom team auto` checks it's ready and says what's missing; `loom team auto on` does the
|
|
175
|
+
setup below for you (the Team tab's **Turn on** is the same thing).
|
|
176
|
+
|
|
174
177
|
```bash
|
|
175
178
|
# once, in the repo: let teammates' runners take its work (reviewed like any policy change)
|
|
176
179
|
echo '{ "runners": { "shared": true } }' > loom.team.json
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@loompad/cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.4",
|
|
4
4
|
"description": "Loom — local-first control plane for coding agents: one CLI, shared memory, baton handoffs and routes across Claude Code, OpenCode, and friends.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|