@lmctl-ai/lmctl 0.1.97 → 0.1.98
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 +16 -0
- package/README.md +3 -2
- package/dist/cli/index.js +568 -568
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
|
|
4
4
|
|
|
5
|
+
## 0.1.98 — 2026-07-10
|
|
6
|
+
|
|
7
|
+
- **`lmctl push` — flush your outbound queue.** In daemon-less push mode the sender drives delivery:
|
|
8
|
+
`lmctl push` sequentially delivers all of this node's queued mail to receivers that are currently
|
|
9
|
+
idle (one lane per turn, reusing the same delivery path as `chat`), and skips busy receivers so
|
|
10
|
+
their mail stays queued. It is single-instance per node — a second concurrent `push` is rejected
|
|
11
|
+
as a conflict and delivers nothing.
|
|
12
|
+
- **`lmctl check` — read-only status.** Reports this node's background jobs and its outbound queued
|
|
13
|
+
mail, grouped by `(sender, receiver)` lane with pending counts and each receiver's busy/idle. It
|
|
14
|
+
never delivers, marks, or mutates anything (including creating no tracked invocation).
|
|
15
|
+
- **Removed `lmctl recv` and `lmctl loop`.** In push mode the receiver never pulls (delivery is
|
|
16
|
+
pushed), and `loop` is replaced by launching `lmctl chat`/`lmctl push` in the background and
|
|
17
|
+
waking on `lmctl wait`. Both now error as unknown commands. `wait` is unchanged.
|
|
18
|
+
- The idle-target delivery used by `chat` is now a shared `deliverLane` helper that `push` reuses,
|
|
19
|
+
so the two can't drift.
|
|
20
|
+
|
|
5
21
|
## 0.1.97 — 2026-07-10
|
|
6
22
|
|
|
7
23
|
- **`lmctl chat` now carries the mailbox queue; `lmctl send` is removed.** One verb. Chatting a
|
package/README.md
CHANGED
|
@@ -57,7 +57,7 @@ onboarding.
|
|
|
57
57
|
Lintable teamfile templates for research, writing, and review teams ship in the
|
|
58
58
|
[examples gallery](https://lmctl.com/examples/).
|
|
59
59
|
|
|
60
|
-
`lmctl` top-level subcommands are: `api`, `chat`, `
|
|
60
|
+
`lmctl` top-level subcommands are: `api`, `chat`, `check`, `push`, `code`, `serve`, `intake`,
|
|
61
61
|
`mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`, `wait`,
|
|
62
62
|
`exec`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
|
|
63
63
|
`run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
|
|
@@ -65,7 +65,8 @@ Lintable teamfile templates for research, writing, and review teams ship in the
|
|
|
65
65
|
[documentation](https://lmctl.com/lmctl) to define your first team.
|
|
66
66
|
|
|
67
67
|
- `lmctl chat <teamfile> <alias> "message"` drives or messages a member; if a member-origin target is busy, chat queues the message for that lane.
|
|
68
|
-
- `lmctl
|
|
68
|
+
- `lmctl check` shows the calling member's background jobs and outbound queued lanes without mutating anything.
|
|
69
|
+
- `lmctl push` flushes the calling member's outbound queued lanes to idle receivers; busy receivers stay queued.
|
|
69
70
|
|
|
70
71
|
## Model selection
|
|
71
72
|
|