@lmctl-ai/lmctl 0.1.115 → 0.1.116

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 CHANGED
@@ -49,24 +49,22 @@ lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next
49
49
  ```
50
50
 
51
51
  Start with `lmctl run <url>` for published workflows. For a custom AI-Lead team,
52
- use the plan -> lint -> seed -> chat flow. For long turns, background a tracked
53
- invocation (`lmctl exec -- <command> &` or a backgrounded `lmctl chat`) and let
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.
52
+ use the plan -> lint -> seed -> chat flow. lmctl does not manage foreground vs.
53
+ background execution for provider turns or shell commands; use the provider or
54
+ host runtime's own background/task surface when you need async execution.
56
55
  Daemon, web, API, and MCP surfaces are secondary integration paths; the CLI is
57
56
  the golden path for onboarding.
58
57
  Lintable teamfile templates for research, writing, and review teams ship in the
59
58
  [examples gallery](https://lmctl.com/examples/).
60
59
 
61
- `lmctl` top-level subcommands are: `api`, `chat`, `notify_me`, `code`, `serve`, `intake`,
60
+ `lmctl` top-level subcommands are: `api`, `chat`, `code`, `serve`, `intake`,
62
61
  `mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`,
63
- `exec`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
62
+ `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
64
63
  `run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
65
64
  `db`. Run `lmctl <command> --help` for details on each, and see the
66
65
  [documentation](https://lmctl.com/lmctl) to define your first team.
67
66
 
68
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.
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."
70
68
 
71
69
  ## Model selection
72
70