@lmctl-ai/lmctl 0.1.154 → 0.1.155
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 +3 -3
- package/dist/cli/index.js +441 -443
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -57,12 +57,12 @@ Start with the plan -> lint -> seed -> chat flow. lmctl does not manage
|
|
|
57
57
|
foreground vs. background execution for provider turns or shell commands; use
|
|
58
58
|
the provider or host runtime's own background/task surface when you need async
|
|
59
59
|
execution.
|
|
60
|
-
Daemon, web,
|
|
61
|
-
|
|
60
|
+
Daemon, web, and API surfaces are secondary integration paths; the CLI is the
|
|
61
|
+
golden path for onboarding.
|
|
62
62
|
Lintable teamfile templates for research, writing, and review teams ship in the
|
|
63
63
|
[examples gallery](https://lmctl.com/examples/).
|
|
64
64
|
|
|
65
|
-
`lmctl` top-level subcommands are: `api`, `chat`, `serve`, `
|
|
65
|
+
`lmctl` top-level subcommands are: `api`, `chat`, `serve`, `device`,
|
|
66
66
|
`team`, `terminal`, `tail`, `health`, `recover`, `ls`, `lint`, `seed`, `hire`,
|
|
67
67
|
`refresh`, `clone`, `plan`, `workspace`, `diagnose`, `diagnose-prompt`,
|
|
68
68
|
`status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
|