@goondocks/myco 0.2.11 → 0.2.12
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/commands/init.md
CHANGED
|
@@ -7,35 +7,56 @@ description: Initialize Myco in the current project — sets up vault, config, a
|
|
|
7
7
|
|
|
8
8
|
Guide the user through setup, then run the CLI to create the vault. **Do NOT create files manually — the CLI handles all vault creation, config writing, and env configuration.**
|
|
9
9
|
|
|
10
|
+
**Ask each question one at a time using AskUserQuestion with selectable options.** Wait for the user's answer before proceeding to the next question. Do NOT combine multiple questions into one message.
|
|
11
|
+
|
|
10
12
|
## Step 1: Choose vault location
|
|
11
13
|
|
|
12
|
-
Ask the user
|
|
14
|
+
Ask the user:
|
|
15
|
+
|
|
16
|
+
**Question:** "Where would you like to store the Myco vault?"
|
|
17
|
+
|
|
18
|
+
**Options:**
|
|
19
|
+
- "In the project (.myco/)" — vault lives with the code, can be committed to git for team sharing
|
|
20
|
+
- "Centralized (~/.myco/vaults/<project-name>/)" — vault stays outside the repo, good for public repos or personal use
|
|
21
|
+
- "Custom path" — specify your own location
|
|
13
22
|
|
|
14
|
-
|
|
15
|
-
>
|
|
16
|
-
> 1. **In the project** (`.myco/`) — vault lives with the code, can be committed to git for team sharing
|
|
17
|
-
> 2. **Centralized** (`~/.myco/vaults/<project-name>/`) — vault stays outside the repo, good for public repos or personal use
|
|
18
|
-
> 3. **Custom path** — specify your own location
|
|
23
|
+
If the user picks "Custom path", ask them to type the path.
|
|
19
24
|
|
|
20
|
-
## Step 2: Choose
|
|
25
|
+
## Step 2: Choose LLM provider
|
|
21
26
|
|
|
22
|
-
|
|
27
|
+
First, detect available providers by checking local endpoints:
|
|
23
28
|
|
|
24
29
|
- **Ollama** — `curl -s http://localhost:11434/api/tags` — list model names
|
|
25
30
|
- **LM Studio** — `curl -s http://localhost:1234/v1/models` — list model IDs
|
|
26
31
|
- **Anthropic** — check if `ANTHROPIC_API_KEY` is set
|
|
27
32
|
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
33
|
+
Then ask the user:
|
|
34
|
+
|
|
35
|
+
**Question:** "Which LLM provider for summarization?"
|
|
36
|
+
|
|
37
|
+
**Options:** List only providers that are actually running, with recommended models noted. Example:
|
|
38
|
+
- "Ollama — gpt-oss (recommended)"
|
|
39
|
+
- "LM Studio — openai/gpt-oss-20b"
|
|
40
|
+
- "Anthropic"
|
|
41
|
+
|
|
42
|
+
After the user picks a provider, ask them to choose a specific model from the available models on that provider.
|
|
43
|
+
|
|
44
|
+
## Step 3: Choose embedding provider
|
|
45
|
+
|
|
46
|
+
Ask the user:
|
|
47
|
+
|
|
48
|
+
**Question:** "Which embedding provider?"
|
|
49
|
+
|
|
50
|
+
**Options:** List only providers that are running and support embeddings (Anthropic does not). Example:
|
|
51
|
+
- "Ollama — bge-m3 (recommended)"
|
|
52
|
+
- "LM Studio — text-embedding-bge-m3"
|
|
31
53
|
|
|
32
|
-
|
|
54
|
+
After the user picks a provider, ask them to choose a specific embedding model.
|
|
33
55
|
|
|
34
|
-
If the recommended model isn't available, offer to pull it:
|
|
35
|
-
- **Ollama**: `ollama pull
|
|
36
|
-
- **LM Studio**: `lms get <owner/model>`
|
|
56
|
+
If the recommended embedding model isn't available, offer to pull it:
|
|
57
|
+
- **Ollama**: `ollama pull bge-m3`
|
|
37
58
|
|
|
38
|
-
## Step
|
|
59
|
+
## Step 4: Run the CLI
|
|
39
60
|
|
|
40
61
|
Run the init command with all gathered inputs. The CLI creates the vault, writes config, sets up the FTS index, and configures `MYCO_VAULT_DIR` if the vault is external:
|
|
41
62
|
|
|
@@ -50,7 +71,7 @@ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js init \
|
|
|
50
71
|
--embedding-url <base-url>
|
|
51
72
|
```
|
|
52
73
|
|
|
53
|
-
## Step
|
|
74
|
+
## Step 5: Verify
|
|
54
75
|
|
|
55
76
|
After the CLI completes, confirm providers are reachable:
|
|
56
77
|
|