@goondocks/myco 0.4.2 → 0.4.3

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "source": {
         "source": "npm",
         "package": "@goondocks/myco",
-        "version": "0.4.1"
+        "version": "0.4.2"
       },
       "description": "Collective agent intelligence — captures session knowledge and serves it back via MCP",
       "license": "MIT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "myco",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "Collective agent intelligence — captures session knowledge and serves it back to your team via MCP",
   "author": {
     "name": "goondocks-co",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@goondocks/myco",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "Collective agent intelligence — Claude Code plugin",
   "type": "module",
   "main": "dist/index.js",

package/skills/myco/SKILL.md

@@ -207,6 +207,10 @@ The vault should get sharper over time, not just bigger. Every session should le
 2. If you find relevant context, factor it into your recommendation
 3. After the decision is made, `myco_remember` the rationale
 
+## Reconfiguration
+
+To change LLM providers, models, or digest settings on an existing vault, see `references/reconfiguration.md`. It covers the exact CLI commands, flag names, and order of operations (setup-llm → restart → rebuild if needed → verify).
+
 ## Maintenance
 
 For the full CLI reference with all flags, see `references/cli-usage.md`.

package/skills/myco/references/reconfiguration.md

@@ -0,0 +1,92 @@
+# Reconfiguration
+
+Workflows for changing LLM providers, models, and digest settings on an existing vault. **Use the AskUserQuestion tool** to ask which settings to change — do not guess.
+
+## Changing LLM or Embedding Provider/Model
+
+Follow this exact order:
+
+```bash
+# 1. Detect what's available
+node <plugin-root>/dist/src/cli.js detect-providers
+
+# 2. Apply the change (use the correct --llm- or --embedding- prefixed flags)
+node <plugin-root>/dist/src/cli.js setup-llm \
+  --llm-provider <provider> --llm-model <model> \
+  --embedding-provider <provider> --embedding-model <model>
+
+# 3. ALWAYS restart daemon after any config change
+node <plugin-root>/dist/src/cli.js restart
+
+# 4. Only rebuild if the EMBEDDING model changed (not needed for LLM-only changes)
+node <plugin-root>/dist/src/cli.js rebuild
+
+# 5. Verify connectivity
+node <plugin-root>/dist/src/cli.js verify
+```
+
+### Critical Flags
+
+The `setup-llm` command uses `--llm-provider`, `--llm-model`, `--embedding-provider`, `--embedding-model` — NOT `--provider` or `--model`. Only pass flags for settings the user explicitly wants to change.
+
+### Order Matters
+
+1. `setup-llm` writes config
+2. `restart` loads the new config into the daemon
+3. `rebuild` re-embeds with the new embedding model (skip if embedding didn't change)
+4. `verify` confirms everything works
+
+### Embedding Model Warning
+
+If the embedding model changed, tell the user: "Changing the embedding model requires a full vector index rebuild. This may take a few minutes."
+
+## Changing Digest Settings
+
+```bash
+node <plugin-root>/dist/src/cli.js setup-digest \
+  --context-window <number> --inject-tier <tier>
+node <plugin-root>/dist/src/cli.js restart
+```
+
+For all available `setup-digest` flags (tiers, provider override, metabolism tuning, token budgets), see `cli-usage.md`.
+
+## Viewing Current Settings
+
+```bash
+node <plugin-root>/dist/src/cli.js setup-llm --show
+node <plugin-root>/dist/src/cli.js setup-digest --show
+```
+
+## Common Scenarios
+
+### "Change my LLM model" (same provider)
+
+```bash
+node <plugin-root>/dist/src/cli.js setup-llm --llm-model qwen3.5:35b
+node <plugin-root>/dist/src/cli.js restart
+node <plugin-root>/dist/src/cli.js verify
+```
+
+No rebuild needed — embedding didn't change.
+
+### "Switch from Ollama to LM Studio"
+
+```bash
+node <plugin-root>/dist/src/cli.js detect-providers
+node <plugin-root>/dist/src/cli.js setup-llm \
+  --llm-provider lm-studio --llm-model "qwen/qwen3.5-35b-a3b"
+node <plugin-root>/dist/src/cli.js restart
+node <plugin-root>/dist/src/cli.js verify
+```
+
+### "Change everything" (provider, model, and embedding)
+
+```bash
+node <plugin-root>/dist/src/cli.js detect-providers
+node <plugin-root>/dist/src/cli.js setup-llm \
+  --llm-provider ollama --llm-model qwen3.5:35b \
+  --embedding-provider ollama --embedding-model bge-m3
+node <plugin-root>/dist/src/cli.js restart
+node <plugin-root>/dist/src/cli.js rebuild
+node <plugin-root>/dist/src/cli.js verify
+```

package/skills/setup/SKILL.md

@@ -19,7 +19,7 @@ Run:
 node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js stats
 ```
 
-- If the command **succeeds** (exit code 0): tell the user "Myco is already configured" and invoke the `myco` skill to handle reconfiguration or display status. Stop here — do not continue with the setup flow.
+- If the command **succeeds** (exit code 0): the vault already exists. Tell the user "Myco is already configured at `<vault-path>`." Then invoke the `myco` skill using the Skill tool — the `myco` skill handles all reconfiguration, status checks, and ongoing management. **Stop here. Do not continue with the setup flow. Do not attempt reconfiguration yourself.**
 - If the command **fails** (exit code non-zero or vault not found): proceed to Step 2.
 
 ## Step 2: Detect System
@@ -50,11 +50,11 @@ Record: detected RAM (GB), recommended model, digest context window, and default
 
 ## Step 3: Ask Questions
 
-Ask one question at a time. Do not batch questions. Wait for each answer before asking the next.
+**Use the AskUserQuestion tool for every question.** Present choices as selectable options. Do not ask questions in plain text — always use AskUserQuestion so the user can select from options. Wait for each answer before asking the next.
 
 ### Question 1: Vault Location
 
-Ask the user where to store the vault. Present three choices:
+Use AskUserQuestion to ask the user where to store the vault. Present three choices:
 
 - **Project-local** — `.myco/` in the current directory
 - **Centralized** — `~/.myco/vaults/<project-name>/` (where `<project-name>` is the current directory's basename)