@lmctl-ai/lmctl 0.1.82 → 0.1.83
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 +5 -5
- package/dist/cli/index.js +583 -576
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,14 +45,14 @@ lmctl run https://lmctl.com/workflows/research.compound.json
|
|
|
45
45
|
lmctl plan ./my-project
|
|
46
46
|
lmctl lint ./my-project/my-project.lmctl
|
|
47
47
|
lmctl seed ./my-project/my-project.lmctl
|
|
48
|
-
lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next steps."
|
|
49
|
-
lmctl jobs watch <id>
|
|
48
|
+
lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next steps."
|
|
50
49
|
```
|
|
51
50
|
|
|
52
51
|
Start with `lmctl run <url>` for published workflows. For a custom AI-Lead team,
|
|
53
|
-
use the plan -> lint -> seed ->
|
|
54
|
-
|
|
55
|
-
integration paths; the CLI/job portal
|
|
52
|
+
use the plan -> lint -> seed -> chat flow. Use provider-native background
|
|
53
|
+
execution for long turns, with `lmctl jobs` as the tracked work portal. Daemon,
|
|
54
|
+
web, API, and MCP surfaces are secondary integration paths; the CLI/job portal
|
|
55
|
+
is the golden path for onboarding.
|
|
56
56
|
Lintable teamfile templates for research, writing, and review teams ship in the
|
|
57
57
|
[examples gallery](https://lmctl.com/examples/).
|
|
58
58
|
|