@lmctl-ai/lmctl 0.1.25 → 0.1.27
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/CHANGELOG.md +10 -0
- package/README.md +1 -1
- package/dist/cli/index.js +468 -490
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,16 @@ All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
- Teamfiles no longer hardcode `sessiondir`. `seed`/`hire` don't bake it in
|
|
8
|
+
and `clone` strips it, so a teamfile is portable to any directory;
|
|
9
|
+
`sessiondir` defaults to the teamfile's own folder. An explicit
|
|
10
|
+
`sessiondir=` is still honored for a member that runs elsewhere. `lmctl lint`
|
|
11
|
+
now warns when a member's sessiondir is not writable, so permission problems
|
|
12
|
+
surface before seed.
|
|
13
|
+
- Removed the top-level `lmctl init` command. Provider setup (installing and
|
|
14
|
+
authenticating each provider CLI) is now a documentation concern; lmctl
|
|
15
|
+
detects missing providers/auth at use time during seed/chat. `lmctl status`
|
|
16
|
+
no longer shows a persisted active-providers list.
|
|
7
17
|
- Removed static `_CONNECT_` cross-team routing and the `lmctl connect` command.
|
|
8
18
|
Legacy `_CONNECT_` lines now parse as deprecated no-ops with a lint warning,
|
|
9
19
|
cross-team Lead sends work at runtime without predeclared edges, runtime
|
package/README.md
CHANGED
|
@@ -45,7 +45,7 @@ lmctl run https://lmctl.com/workflows/research.compound.json
|
|
|
45
45
|
```
|
|
46
46
|
|
|
47
47
|
`lmctl` provides subcommands including `api`, `chat`, `code`, `serve`, `intake`,
|
|
48
|
-
`mcp`, `monitor`, `team`, `workflow`, `project`, `workspace`, `diagnose`,
|
|
48
|
+
`mcp`, `monitor`, `team`, `workflow`, `project`, `workspace`, `diagnose`,
|
|
49
49
|
`status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
|
|
50
50
|
[documentation](https://lmctl.com/lmctl) to define your first team.
|
|
51
51
|
|