@lmctl-ai/lmctl 0.1.24 → 0.1.25
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 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -15,7 +15,9 @@ Two things set it apart from how "multi-agent" and "AI review" usually work:
|
|
|
15
15
|
- **Review is adversarial, not self-review.** The reviewer is a different
|
|
16
16
|
provider *and* model from the author — a Claude lead hands coding to Codex and
|
|
17
17
|
has Gemini review it — so a model's blind spots aren't rubber-stamped by
|
|
18
|
-
itself in a different hat.
|
|
18
|
+
itself in a different hat. Different models have different (uncorrelated) blind
|
|
19
|
+
spots; that **model diversity** is the point — a varied team catches what one
|
|
20
|
+
model, or its clones, can't.
|
|
19
21
|
- **You build and tune the team — the provider doesn't.** Most "multi-agent"
|
|
20
22
|
tools have one provider auto-spawn agents you can't steer. In lmctl you divide
|
|
21
23
|
the work, compose the team in plain text, pick the provider and model for each
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lmctl-ai/lmctl",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.25",
|
|
4
4
|
"description": "A provider-agnostic control plane for teams of AI coding agents — across providers, with independent review and durable memory.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"homepage": "https://lmctl.com",
|