@lmctl-ai/lmctl 0.1.156 → 0.1.157
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 +1 -1
- package/dist/cli/index.js +149 -143
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -71,7 +71,7 @@ Lintable teamfile templates for research, writing, and review teams ship in the
|
|
|
71
71
|
`status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
|
|
72
72
|
[documentation](https://lmctl.com/lmctl) to define your first team.
|
|
73
73
|
|
|
74
|
-
- `lmctl chat <teamfile> <alias> "message"` drives or messages a member. If a member-origin target is busy, chat queues the message for that sender->receiver lane; the next chat to that receiver when it is free delivers the queued lane plus the new message.
|
|
74
|
+
- `lmctl chat <teamfile> <alias> "message"` drives or messages a member. If a member-origin target is busy, chat queues the message for that sender->receiver lane; the next chat **from that same sender** to that receiver, when it is free, delivers the queued lane plus the new message. The lane key is `(sender, receiver)`: **a chat to that receiver from anyone else does not flush your queued mail.** If you go idle waiting for the reply you queued, nothing else will unblock it — you are the only party whose next chat flushes that lane.
|
|
75
75
|
|
|
76
76
|
## Model selection
|
|
77
77
|
|