@lmctl-ai/lmctl 0.1.22 → 0.1.24

package/CHANGELOG.md

@@ -4,6 +4,11 @@ All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
 
 ## Unreleased
 
+- Removed static `_CONNECT_` cross-team routing and the `lmctl connect` command.
+  Legacy `_CONNECT_` lines now parse as deprecated no-ops with a lint warning,
+  cross-team Lead sends work at runtime without predeclared edges, runtime
+  cycle protection uses `team_chat_log` + `agent_inflight`, and migration v38
+  drops the retired `team_connection` table.
 - Replaced native `better-sqlite3` with built-in `node:sqlite`; Node >=24.15.0
   is now required and npm install no longer has a native SQLite build step.
 - Added `provider=opencode` model-effort selection with `_MEMBER_ ... model=<id> effort=<variant>`.

package/README.md

@@ -20,6 +20,10 @@ Two things set it apart from how "multi-agent" and "AI review" usually work:
   tools have one provider auto-spawn agents you can't steer. In lmctl you divide
   the work, compose the team in plain text, pick the provider and model for each
   role, and tune how they interact.
+- **Any model, local or remote — any mix in one team.** Alongside the major CLIs,
+  the OpenCode provider reaches any model: local (Ollama) or remote (DeepSeek,
+  Qwen, OpenRouter, Copilot's GPT/Claude/Gemini, and more). Put any collection of
+  them in a single team, working together — not one model at a time.
 
 > **Public preview.** Free to use during the preview. Closed-source, proprietary
 > software distributed in binary form — see the [License](https://lmctl.com/lmctl/docs/license).