@lmctl-ai/lmctl 0.1.194 → 0.1.196
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 +13 -2
- package/dist/cli/index.js +596 -639
- package/durable-memory/model_selection.md +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -51,7 +51,7 @@ lmctl mail sent --limit 100 --cursor "$NEXT_CURSOR" --json
|
|
|
51
51
|
|
|
52
52
|
`lmctl status` is team/SELF-scoped: from a member session it shows your
|
|
53
53
|
identity, team roster busy/idle state, recent activity in both directions, and
|
|
54
|
-
pending mailbox lanes. From a plain operator shell it shows a
|
|
54
|
+
pending mailbox lanes. From a plain operator shell it shows a DB-wide summary.
|
|
55
55
|
Use `lmctl status --json` for the full machine-readable view; `--project` and
|
|
56
56
|
`--web` are not status flags.
|
|
57
57
|
|
|
@@ -69,10 +69,21 @@ Lintable teamfile templates for research, writing, and review teams ship in the
|
|
|
69
69
|
|
|
70
70
|
`lmctl` top-level subcommands are: `api`, `chat`, `serve`, `device`,
|
|
71
71
|
`team`, `terminal`, `tail`, `health`, `recover`, `ls`, `lint`, `seed`, `hire`,
|
|
72
|
-
`refresh`, `clone`, `plan`, `
|
|
72
|
+
`refresh`, `clone`, `plan`, `diagnose`, `diagnose-prompt`,
|
|
73
73
|
`mail`, `status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
|
|
74
74
|
[documentation](https://lmctl.com/lmctl) to define your first team.
|
|
75
75
|
|
|
76
|
+
Abstract managed-team providers retain the config keys
|
|
77
|
+
`workspace.provider1`, `workspace.provider2`, and `workspace.provider3`.
|
|
78
|
+
Set their concrete provider names directly in `~/.lmctl/state.db`; the key
|
|
79
|
+
names remain stable for compatibility:
|
|
80
|
+
|
|
81
|
+
```sh
|
|
82
|
+
sqlite3 ~/.lmctl/state.db "INSERT OR REPLACE INTO lmctl_config(key,value,updated_at) VALUES('workspace.provider1','claude',strftime('%Y-%m-%dT%H:%M:%fZ','now'));"
|
|
83
|
+
sqlite3 ~/.lmctl/state.db "INSERT OR REPLACE INTO lmctl_config(key,value,updated_at) VALUES('workspace.provider2','codex',strftime('%Y-%m-%dT%H:%M:%fZ','now'));"
|
|
84
|
+
sqlite3 ~/.lmctl/state.db "INSERT OR REPLACE INTO lmctl_config(key,value,updated_at) VALUES('workspace.provider3','gemini',strftime('%Y-%m-%dT%H:%M:%fZ','now'));"
|
|
85
|
+
```
|
|
86
|
+
|
|
76
87
|
`lmctl mail` exposes read-only primitives over the event-log substrate only:
|
|
77
88
|
list messages sent from SELF, read a message's ordered event history, check its
|
|
78
89
|
historical provider transcript, and render causal delegation lineage. It does
|