@lmctl-ai/lmctl 0.1.111 → 0.1.113

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.
Files changed (3) hide show
  1. package/README.md +6 -5
  2. package/dist/cli/index.js +67 -61
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -51,13 +51,14 @@ lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next
51
51
  Start with `lmctl run <url>` for published workflows. For a custom AI-Lead team,
52
52
  use the plan -> lint -> seed -> chat flow. For long turns, background a tracked
53
53
  invocation (`lmctl exec -- <command> &` or a backgrounded `lmctl chat`) and let
54
- `lmctl more` block until it finishes — that return is the wake. Daemon, web, API,
55
- and MCP surfaces are secondary integration paths; the CLI is the golden path for
56
- onboarding.
54
+ `lmctl notify_me` block until something lands — that return is the wake. Call it
55
+ in the foreground; it holds your process and returns when a member finishes.
56
+ Daemon, web, API, and MCP surfaces are secondary integration paths; the CLI is
57
+ the golden path for onboarding.
57
58
  Lintable teamfile templates for research, writing, and review teams ship in the
58
59
  [examples gallery](https://lmctl.com/examples/).
59
60
 
60
- `lmctl` top-level subcommands are: `api`, `chat`, `more`, `code`, `serve`, `intake`,
61
+ `lmctl` top-level subcommands are: `api`, `chat`, `notify_me`, `code`, `serve`, `intake`,
61
62
  `mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`,
62
63
  `exec`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
63
64
  `run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
@@ -65,7 +66,7 @@ Lintable teamfile templates for research, writing, and review teams ship in the
65
66
  [documentation](https://lmctl.com/lmctl) to define your first team.
66
67
 
67
68
  - `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 more` flushes queued outbound lanes, shows jobs/queue status, and returns finished work or receipts.
69
+ - `lmctl notify_me` is the foreground wait: "I'm done with this round; my delegations are all running in the background; I'm taking a break — notify me when something lands."
69
70
 
70
71
  ## Model selection
71
72