@lmctl-ai/lmctl 0.1.212 → 0.1.214
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 +22 -0
- package/dist/cli/index.js +539 -539
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,28 @@
|
|
|
2
2
|
|
|
3
3
|
All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
|
|
4
4
|
|
|
5
|
+
## Unreleased
|
|
6
|
+
|
|
7
|
+
- **A live `lmctl chat` dispatch no longer orphans the receiver's own background
|
|
8
|
+
work — and its duration is now subtree-bound, not turn-bound.** Previously the
|
|
9
|
+
provider transport closed the agent's stdin the instant its turn produced
|
|
10
|
+
visible text; headless `claude -p` treats that as "turn over" and exits, so any
|
|
11
|
+
dispatches the agent had fired during that turn (its own `lmctl chat` calls to
|
|
12
|
+
team members) were killed mid-flight along with their completion
|
|
13
|
+
notifications. The transport now defers that close while the session still has
|
|
14
|
+
live dispatched work of its own, and for a short quiescence window afterwards
|
|
15
|
+
so the completion notification is actually delivered.
|
|
16
|
+
- **Consequence for every caller of the synchronous path: a `chat` to an agent
|
|
17
|
+
that delegates further now returns when that agent's delegated work finishes,
|
|
18
|
+
not when its own reply is written.** *Do not wrap a live `lmctl chat` call in a
|
|
19
|
+
fixed `timeout N` — of any duration.* There is no safe fixed `N` when the true
|
|
20
|
+
duration depends on a delegation subtree, and the `SIGTERM` a timeout sends
|
|
21
|
+
does not stay contained to the sender: it propagates into the receiver's live
|
|
22
|
+
turn and can cascade further down the chain. Run the dispatch without a
|
|
23
|
+
deadline and track completion through your own runtime's background-task
|
|
24
|
+
notification instead. Receivers that dispatch nothing are unaffected (the
|
|
25
|
+
no-outstanding-work path is a single check, as before).
|
|
26
|
+
|
|
5
27
|
## 0.1.100 — 2026-07-11
|
|
6
28
|
|
|
7
29
|
- **`lmctl wait` is now state-based, fixing a missed-wake for tracked jobs.** A backgrounded job
|