@lmctl-ai/lmctl 0.1.101 → 0.1.103

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 +4 -5
  2. package/dist/cli/index.js +542 -550
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -51,22 +51,21 @@ 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 wait` block until it finishes — that return is the wake. Daemon, web, API,
54
+ `lmctl more` block until it finishes — that return is the wake. Daemon, web, API,
55
55
  and MCP surfaces are secondary integration paths; the CLI is the golden path for
56
56
  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`, `check`, `push`, `code`, `serve`, `intake`,
61
- `mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`, `wait`,
60
+ `lmctl` top-level subcommands are: `api`, `chat`, `more`, `code`, `serve`, `intake`,
61
+ `mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`,
62
62
  `exec`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
63
63
  `run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
64
64
  `db`. Run `lmctl <command> --help` for details on each, and see 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 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.
68
+ - `lmctl more` flushes queued outbound lanes, shows jobs/queue status, and returns finished work or receipts.
70
69
 
71
70
  ## Model selection
72
71