@lmctl-ai/lmctl 0.1.79 → 0.1.81
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 +17 -3
- package/dist/cli/index.js +713 -692
- package/dist/cli/schema.sql +12 -1
- package/examples/README.md +25 -0
- package/examples/book-team.lmctl +15 -0
- package/examples/opencode.json +24 -58
- package/examples/research-team.lmctl +15 -0
- package/examples/review-team.lmctl +15 -0
- package/package.json +1 -2
package/README.md
CHANGED
|
@@ -42,11 +42,25 @@ npm install -g @lmctl-ai/lmctl
|
|
|
42
42
|
lmctl --help
|
|
43
43
|
lmctl status
|
|
44
44
|
lmctl run https://lmctl.com/workflows/research.compound.json
|
|
45
|
+
lmctl plan ./my-project
|
|
46
|
+
lmctl lint ./my-project/my-project.lmctl
|
|
47
|
+
lmctl seed ./my-project/my-project.lmctl
|
|
48
|
+
lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next steps." --detach
|
|
49
|
+
lmctl jobs watch <id>
|
|
45
50
|
```
|
|
46
51
|
|
|
47
|
-
`lmctl
|
|
48
|
-
|
|
49
|
-
|
|
52
|
+
Start with `lmctl run <url>` for published workflows. For a custom AI-Lead team,
|
|
53
|
+
use the plan -> lint -> seed -> `chat --detach` -> `jobs watch` flow so work is
|
|
54
|
+
tracked and recoverable. Daemon, web, API, and MCP surfaces are secondary
|
|
55
|
+
integration paths; the CLI/job portal is the golden path for onboarding.
|
|
56
|
+
Lintable teamfile templates for research, writing, and review teams ship in the
|
|
57
|
+
[examples gallery](https://lmctl.com/examples/).
|
|
58
|
+
|
|
59
|
+
`lmctl` top-level subcommands are: `api`, `chat`, `code`, `serve`, `intake`,
|
|
60
|
+
`mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`, `jobs`,
|
|
61
|
+
`nudge`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
|
|
62
|
+
`run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
|
|
63
|
+
`db`. Run `lmctl <command> --help` for details on each, and see the
|
|
50
64
|
[documentation](https://lmctl.com/lmctl) to define your first team.
|
|
51
65
|
|
|
52
66
|
## Model selection
|