pi-mtplx 0.1.4 → 0.1.5

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 CHANGED
@@ -39,7 +39,7 @@ Run `/mtplx` to open an interactive menu:
39
39
  | **Models** | Register or unregister models — ✓ means registered (click to unregister), ✗ means available (click to register) |
40
40
  | **Uninstall** | Remove the `mtplx` provider from Pi's config |
41
41
 
42
- > **To activate a model** after registering or unregistering it, open **`/model`** (or `/scoped-models`). pi-mtplx writes Pi's config files immediately, but Pi loads them into memory on startup; opening either picker refreshes that in-memory list. No `/reload` needed.
42
+ > **To activate a model** after registering or unregistering it, open **`/model`** (or `/scoped-models`). pi-mtplx writes Pi's config files immediately, but Pi loads them into memory on startup so a **newly registered** MTPLX model only appears in `/model` after you restart Pi with **`/quit`** and relaunch it (`pi`). Unregistering/re-registering an existing model is picked up by opening `/model`, but a brand-new model id requires the restart.
43
43
 
44
44
  ## Configuration
45
45
 
@@ -55,7 +55,7 @@ Models are registered in `~/.pi/agent/mtplx-models.json`. Each entry maps a Pi m
55
55
  }
56
56
  ```
57
57
 
58
- Register new models via the `/mtplx` → **Models** menu, or add entries manually to this file; then open `/model` (or `/scoped-models`) to activate them.
58
+ Register new models via the `/mtplx` → **Models** menu, or add entries manually to this file. To activate a **newly added** model, restart Pi with `/quit` and relaunch it (`pi`), then open `/model` (or `/scoped-models`) Pi reads this file at startup, so a brand-new model id won't show up in `/model` otherwise.
59
59
 
60
60
  ### Fan mode
61
61
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-mtplx",
3
- "version": "0.1.4",
3
+ "version": "0.1.5",
4
4
  "description": "Zero-config MTPLX integration for Pi coding agent",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -209,7 +209,7 @@ export async function manageModels(ctx: ExtensionContext): Promise<boolean> {
209
209
  return `${mark} ${id} — ${ref}`;
210
210
  });
211
211
  choices.push("Cancel");
212
- const picked = await ctx.ui.select("MTPLX models — ✓ registered in Pi · ✗ available in MTPLX — open /model after making changes", choices, undefined);
212
+ const picked = await ctx.ui.select("MTPLX models — ✓ registered in Pi · ✗ available in MTPLX — registering a new model needs a Pi restart (/quit → pi) to show up in /model", choices, undefined);
213
213
  if (!picked || picked === "Cancel") return false;
214
214
  const ref = picked.split(" — ").slice(1).join(" — ");
215
215
  const modelId = modelIdFromRef(ref);
@@ -291,7 +291,7 @@ export async function manageModels(ctx: ExtensionContext): Promise<boolean> {
291
291
  }
292
292
  // 3) Also enable the model in settings.json.
293
293
  enableModelInSettings(modelId);
294
- ctx.ui.notify(`Registered ${modelId} → ${ref}. Open /model to activate it.`, "info");
294
+ ctx.ui.notify(`Registered ${modelId} → ${ref}. Restart Pi with /quit (then relaunch with \`pi\`), then open /model to activate it.`, "info");
295
295
  return true;
296
296
  }
297
297
  /**