@lmctl-ai/lmctl 0.1.214 → 0.1.216

package/durable-memory/model_selection.md

@@ -13,6 +13,14 @@ For `.lmctl` teamfile compatibility mode:
   opens a short-lived ACP session and asks opencode itself to validate
   `model=` and `effort=`. It never sends a prompt. See the `## OpenCode`
   section below.
+- `kimi` model validation reads configured aliases from
+  `$KIMI_CODE_HOME/config.toml` (default `~/.kimi-code/config.toml`) and
+  WARNS (never injects) when `model=` isn't one of the declared
+  `[models.<alias>]` table names, or when the config file itself is
+  missing/unreadable. Same rationale as opencode: kimi model aliases are
+  user-defined, not a fixed vendor catalog, so a hardcoded list in this
+  doc would be wrong for every user whose aliases differ. See the
+  `## Kimi` section below.
 - `copilot` accepts `model=` syntactically, but model selection is not
   supported and lint warns that the value is ignored.
 - `lmctl seed <teamfile>` passes `model=` through to the provider seed
@@ -138,11 +146,43 @@ Example:
 _MEMBER_ alias=Reviewer provider=opencode model=github-copilot/gpt-5.4 effort=xhigh sessionid=<seeded-id>
 ```
 
+## Kimi
+
+Kimi (Moonshot AI's Kimi Code CLI) speaks ACP, same transport family as opencode/
+gemini/copilot. `model=` values are **user-defined aliases** declared in
+`$KIMI_CODE_HOME/config.toml` under `[models.<alias>]` table headers (e.g.
+`[models."kimi-code/k3"]`), not a fixed vendor catalog — same shape as opencode,
+not claude/codex. `lmctl` does not manage this file; it only reads it to validate
+`model=` at lint/seed time and warns (never injects) when the config is missing
+or the alias isn't declared.
+
+Kimi's ACP mode defaults to permission-**prompting** (unlike every argv-YOLO or
+config-file-YOLO provider). lmctl forces it into full-auto via an ACP protocol
+call (`session/set_config_option`, `configId: "mode"`, `value: "auto"`) sent
+after `session/new`/`session/load` and before the first `session/prompt` —
+fail-closed: if that call is rejected, lmctl throws rather than proceeding, on
+both the one-shot transport (`src/providers/transports/acp.ts`) and the
+persistent `lmctl serve`/daemon path (`src/serve/persistent-adapters.ts`). See
+`src/providers/yolo-contract.ts`'s `PROTOCOL_LEVEL_YOLO` set for the contract.
+
+Kimi 0.28.x exposes `thinking` through ACP only as an `on`/`off` toggle.
+Turning it on selects the current model alias's `default_effort` from
+`config.toml`; it does not accept a session-level effort value. Choose or
+define a different model alias when a different default effort is required.
+Accordingly, lmctl warns that `_MEMBER_ effort=` is ignored for Kimi.
+
+Example:
+
+```md
+_MEMBER_ alias=Reviewer provider=kimi model="kimi-code/k3" sessionid=<seeded-id>
+```
+
 `effort=` support by provider:
 
 | Provider | Status |
 | --- | --- |
 | `opencode` | Supported (via the model's declared `variants` in opencode.json). |
+| `kimi` | Not supported on the Kimi 0.28.x baseline; effort is fixed by the selected model alias's `default_effort`. |
 | `claude` | Claude Code has native `--effort`, but lmctl has not wired `_MEMBER_ effort=` to Claude yet. |
 | `codex` | Native effort surfaces exist; lmctl has not wired `_MEMBER_ effort=` to Codex yet. |
 | `agy` | No verified effort flag; only `--model` supported. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lmctl-ai/lmctl",
-  "version": "0.1.214",
+  "version": "0.1.216",
   "description": "A provider-agnostic control plane for teams of AI coding agents — across providers, with independent review and durable memory.",
   "type": "module",
   "homepage": "https://lmctl.com",