@goondocks/myco 0.27.19 → 1.0.0

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.
Files changed (13) hide show
  1. package/README.md +9 -6
  2. package/dist/ui/assets/index-DE6oYYru.css +2 -0
  3. package/dist/ui/assets/index-Doue33fQ.js +415 -0
  4. package/dist/ui/index.html +2 -2
  5. package/package.json +13 -13
  6. package/scripts/select-binary.mjs +23 -0
  7. package/skills/myco/SKILL.md +27 -48
  8. package/skills/myco/references/cli-usage.md +30 -30
  9. package/skills/myco/references/reconfiguration.md +20 -20
  10. package/skills/myco/references/vault-status.md +13 -13
  11. package/skills/myco/references/wisdom.md +2 -2
  12. package/dist/ui/assets/index-D80qRqAU.css +0 -2
  13. package/dist/ui/assets/index-GRKrkWAI.js +0 -415
package/dist/ui/index.html CHANGED
@@ -5,8 +5,8 @@
5
5
  <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
6
6
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
7
7
  <title>Myco</title>
8
- <script type="module" crossorigin src="/assets/index-GRKrkWAI.js"></script>
9
- <link rel="stylesheet" crossorigin href="/assets/index-D80qRqAU.css">
8
+ <script type="module" crossorigin src="/assets/index-Doue33fQ.js"></script>
9
+ <link rel="stylesheet" crossorigin href="/assets/index-DE6oYYru.css">
10
10
  </head>
11
11
  <body>
12
12
  <div id="root"></div>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@goondocks/myco",
3
- "version": "0.27.19",
3
+ "version": "1.0.0",
4
4
  "description": "Collective agent intelligence — Claude Code plugin",
5
5
  "type": "module",
6
6
  "bin": {
@@ -59,35 +59,35 @@
59
59
  "directory": "packages/myco"
60
60
  },
61
61
  "dependencies": {
62
- "@anthropic-ai/claude-agent-sdk": "^0.3.143",
63
- "@anthropic-ai/sdk": "^0.96.0",
62
+ "@anthropic-ai/claude-agent-sdk": "^0.3.152",
63
+ "@anthropic-ai/sdk": "^0.99.0",
64
64
  "@inquirer/prompts": "^8.4.2",
65
65
  "@modelcontextprotocol/sdk": "^1.28.0",
66
- "@openai/agents": "^0.11.4",
66
+ "@openai/agents": "^0.11.5",
67
67
  "chokidar": "^5.0.0",
68
68
  "gray-matter": "^4.0.3",
69
- "semver": "^7.7.4",
70
- "shell-quote": "^1.8.1",
69
+ "semver": "^7.8.1",
70
+ "shell-quote": "^1.8.4",
71
71
  "smol-toml": "^1.6.1",
72
72
  "yaml": "^2.8.4",
73
73
  "zod": "^4.4.3"
74
74
  },
75
75
  "optionalDependencies": {
76
- "@goondocks/myco-darwin-arm64": "0.27.19",
77
- "@goondocks/myco-darwin-x64": "0.27.19",
78
- "@goondocks/myco-linux-x64": "0.27.19",
79
- "@goondocks/myco-linux-arm64": "0.27.19",
80
- "@goondocks/myco-windows-x64": "0.27.19"
76
+ "@goondocks/myco-darwin-arm64": "1.0.0",
77
+ "@goondocks/myco-darwin-x64": "1.0.0",
78
+ "@goondocks/myco-linux-arm64": "1.0.0",
79
+ "@goondocks/myco-linux-x64": "1.0.0",
80
+ "@goondocks/myco-windows-x64": "1.0.0"
81
81
  },
82
82
  "devDependencies": {
83
83
  "@goondocks/myco-shared": "*",
84
84
  "@types/bun": "^1.3.14",
85
- "@types/node": "^25.9.0",
85
+ "@types/node": "^25.9.1",
86
86
  "@types/semver": "^7.7.1",
87
87
  "@types/shell-quote": "^1.7.5",
88
88
  "@vscode/ripgrep": "^1.15.14",
89
89
  "sqlite-vec": "^0.1.8",
90
- "tsx": "^4.0.0",
90
+ "tsx": "^4.22.3",
91
91
  "typescript": "^6.0.3"
92
92
  }
93
93
  }
package/scripts/select-binary.mjs CHANGED
@@ -80,3 +80,26 @@ fs.writeFileSync(
80
80
  );
81
81
 
82
82
  process.stdout.write(`[myco] Selected platform binary: ${binaryPath}\n`);
83
+
84
+ // Self-install as a managed OS service so launchd / systemd starts the
85
+ // daemon at every login from the moment Myco is installed. Skipped in
86
+ // source checkouts (no published dist/), skipped silently on failure
87
+ // (the daemon's lazy-spawn path still works; doctor will surface the
88
+ // gap). Plan reference: Decision 13 / Step 12.
89
+ if (!isSourceCheckout) {
90
+ const distSelfInstall = path.join(pkgRoot, 'dist/src/service/self-install.js');
91
+ if (fs.existsSync(distSelfInstall)) {
92
+ try {
93
+ const mod = await import(distSelfInstall);
94
+ const stderrLogger = {
95
+ info: (kind, message) => process.stderr.write(`[myco] ${kind}: ${message}\n`),
96
+ debug: () => undefined,
97
+ warn: (kind, message) => process.stderr.write(`[myco] ${kind}: ${message}\n`),
98
+ error: (kind, message) => process.stderr.write(`[myco] ${kind}: ${message}\n`),
99
+ };
100
+ await mod.ensureSelfInstalledAsService(stderrLogger);
101
+ } catch (err) {
102
+ process.stderr.write(`[myco] Service install skipped: ${err?.message ?? err}\n`);
103
+ }
104
+ }
105
+ }
package/skills/myco/SKILL.md CHANGED
@@ -32,20 +32,18 @@ Use the CLI tool surface below for going deeper than the automatic context injec
32
32
 
33
33
  ## Setup
34
34
 
35
- If the vault isn't configured, run `myco init` in the project directory for guided first-time setup.
36
-
37
- For reconfiguration, status checks, and ongoing management, use the CLI commands and tool surfaces documented below. For detailed vault health checks, see `references/vault-status.md`.
35
+ Setup is automatic. Installing the global `myco` binary brings up the daemon and creates a default Grove; opening this project in any supported agent registers it on the first hook. For ongoing status checks and per-project overrides (portable Grove identity, dogfood binary pinning), use the dashboard's Symbionts page. For detailed vault health checks, see `references/vault-status.md`.
38
36
 
39
37
  ## CLI Tool Reference
40
38
 
41
- The stable portable path is the project-resolved CLI launcher. In an initialized project, prefer `node .agents/myco-cli.cjs` because it reads `.myco/runtime.command` in project scope and therefore works with dogfood aliases, worktree-local runtimes, and renamed binaries. The sibling `.agents/myco-run.cjs` launcher is reserved for capture hooks and may intentionally route git worktrees through the main checkout runtime so session data lands in the main vault. If the CLI launcher is not present, use host MCP tools when available, then fall back to `myco-run` or `myco` only when the command is known to be on PATH for this project.
39
+ The stable portable path is the `myco` CLI on your PATH. Prefer `myco tool call …`: the binary walks up from the working directory for a `.myco/runtime.command` pin before dispatching, so it automatically honors dogfood aliases, worktree-local runtimes, and renamed binaries. (The project-local `.agents/myco-cli.cjs` launcher that earlier versions shipped is retired — the global install no longer writes it.) When `myco` is not on PATH — e.g. GUI- or launchd-spawned agents whose environment omits `~/.local/bin` — fall back to the absolute global launcher the hooks themselves use: `node ~/.myco/launcher.cjs tool call …`, which performs the same layered pin resolution. Host MCP tools (`myco_*`) are the other fallback when the agent exposes Myco cleanly.
42
40
 
43
- Project-resolved CLI:
41
+ Myco CLI:
44
42
 
45
43
  ```bash
46
- node .agents/myco-cli.cjs tool list --json
47
- node .agents/myco-cli.cjs tool call <tool-name> --json --input '<json>'
48
- node .agents/myco-cli.cjs tool call <tool-name> --json --input @payload.json
44
+ myco tool list --json
45
+ myco tool call <tool-name> --json --input '<json>'
46
+ myco tool call <tool-name> --json --input @payload.json
49
47
  ```
50
48
 
51
49
  **Use `--input @file.json` whenever the payload contains backticks, code fences, multi-line strings, or markdown.** Agent shells often re-wrap commands through an outer `eval`, and backticks inside the inner single-quoted JSON get command-substituted before the CLI sees them — what you intended as literal `` `foo.ts` `` in spore content becomes the shell trying to execute `foo.ts`. The `@file` form sidesteps this entirely because the JSON never travels through shell escape resolution. Reserve the inline form for short single-line payloads with no special characters (e.g. `{"op":"get","id":"..."}`).
@@ -55,7 +53,7 @@ node .agents/myco-cli.cjs tool call <tool-name> --json --input @payload.json
55
53
  cat > /tmp/payload.json <<'EOF'
56
54
  { "op": "save", "type": "gotcha", "content": "Use `npm test`, not `bun test <subset>`..." }
57
55
  EOF
58
- node .agents/myco-cli.cjs tool call myco_spores --json --input @/tmp/payload.json
56
+ myco tool call myco_spores --json --input @/tmp/payload.json
59
57
  ```
60
58
 
61
59
  If the CLI is genuinely unavailable or both inline and `@file` forms fail repeatedly for the same payload, the host's MCP tool call (when Myco MCP is loaded — look for `myco_*` or `mcp__*myco*` entries in the available-tools list) is the fallback. Don't reach for MCP first — the CLI is the deliberate primary path; this skill is written around it.
@@ -64,26 +62,7 @@ Successful calls return `{ "ok": true, "tool": "<name>", "result": ... }`; failu
64
62
 
65
63
  The local Myco tool surface registers 7 core tools. When the project is connected to a Myco Collective, 4 additional `collective_*` tools are also available. Tools are defined in `packages/myco/src/tools/definitions.ts` — that file is the source of truth. MCP registers the same names when available.
66
64
 
67
- Use direct SQLite reads only as an expert, read-only fallback for complex analysis that cannot be answered through the project-resolved CLI or MCP.
68
-
69
- ## Myco Development Worktrees
70
-
71
- When developing Myco itself inside a git worktree, do not run `make dev-link`. That target rewrites shared `~/.local/bin/myco-*` symlinks and can redirect other active agents to the worktree binary.
72
-
73
- Use the worktree-scoped pattern instead:
74
-
75
- ```bash
76
- make dev-link-worktree
77
- ```
78
-
79
- This builds the worktree binary and writes the worktree's `.myco/runtime.command` directly to `packages/myco-<target>/bin/myco`. That file is local runtime state and is not inherited when a worktree is created, so run the command from each worktree that needs project-scoped CLI/tool testing.
80
-
81
- Runtime scopes stay separate:
82
-
83
- - `.agents/myco-run.cjs` is the capture launcher for hooks; in git worktrees it can resolve through the main checkout runtime so session capture stays attached to the main vault.
84
- - `.agents/myco-cli.cjs` is the project launcher for CLI/tool calls; in git worktrees it prefers the worktree-local `.myco/runtime.command`, then falls back to the main checkout pin.
85
-
86
- Remove only the worktree pin with `make dev-unlink-worktree`. Use `make dev-unlink` only when intentionally removing the shared dev symlinks from the main checkout.
65
+ Use direct SQLite reads only as an expert, read-only fallback for complex analysis that cannot be answered through the `myco` CLI or MCP.
87
66
 
88
67
  ### myco_cortex — Get Cortex intelligence
89
68
 
@@ -96,7 +75,7 @@ Retrieve Cortex-produced project intelligence: the pre-computed project digest,
96
75
  CLI:
97
76
 
98
77
  ```bash
99
- node .agents/myco-cli.cjs tool call myco_cortex --json --input '{"op":"digest","tier":5000}'
78
+ myco tool call myco_cortex --json --input '{"op":"digest","tier":5000}'
100
79
  ```
101
80
 
102
81
  Tiers: `1500` (executive briefing), `5000` (default), `10000` (comprehensive). Prefer this over `myco_search` for broad project orientation; use `myco_search` when you need specific prior decisions or bug fixes.
@@ -104,13 +83,13 @@ Tiers: `1500` (executive briefing), `5000` (default), `10000` (comprehensive). P
104
83
  Canopy map:
105
84
 
106
85
  ```bash
107
- node .agents/myco-cli.cjs tool call myco_cortex --json --input '{"op":"canopy_map"}'
86
+ myco tool call myco_cortex --json --input '{"op":"canopy_map"}'
108
87
  ```
109
88
 
110
89
  Current generated instructions:
111
90
 
112
91
  ```bash
113
- node .agents/myco-cli.cjs tool call myco_cortex --json --input '{"op":"instructions"}'
92
+ myco tool call myco_cortex --json --input '{"op":"instructions"}'
114
93
  ```
115
94
 
116
95
  When delegating work, include the returned instructions verbatim in the delegated prompt alongside the task-specific instructions. Do not assume the returned instructions have a particular heading or section name; they are generated project guidance and may change over time.
@@ -132,7 +111,7 @@ Search across sessions, plans, spores, skills, and Canopy file summaries.
132
111
  CLI:
133
112
 
134
113
  ```bash
135
- node .agents/myco-cli.cjs tool call myco_search --json --input '{"query":"why did we choose JWT over session cookies","type":"spore","limit":5}'
114
+ myco tool call myco_search --json --input '{"query":"why did we choose JWT over session cookies","type":"spore","limit":5}'
136
115
  ```
137
116
 
138
117
  **When to use**: searching for prior decisions, debugging context, understanding rationale, or finding source files by what they do. The `type` filter narrows results — use `"spore"` for decisions/gotchas, `"session"` for session history, `"plan"` for plans, `"skill"` for skills, `"canopy"` for file summaries, or omit for all. Each result includes a stable `id` and, when the entity is retrievable, a `retrieve` object with the exact tool input to fetch it.
@@ -340,20 +319,20 @@ To change embedding settings or Cortex injection behavior on an existing vault,
340
319
 
341
320
  For the full CLI reference with all flags, see `references/cli-usage.md`.
342
321
 
343
- Prefer the project-resolved launcher from the initialized project root:
322
+ Prefer the `myco` CLI from the initialized project root:
344
323
 
345
324
  ```
346
- node .agents/myco-cli.cjs <command> [args]
325
+ myco <command> [args]
347
326
  ```
348
327
 
349
- That launcher honors project and worktree runtime pins. Use a plugin-root `dist/src/cli.js` path only when you are deliberately operating inside an installed plugin bundle and `.agents/myco-cli.cjs` is unavailable.
328
+ The binary honors project and worktree runtime pins — it walks up from the working directory for `.myco/runtime.command`. When `myco` is not on PATH, use the absolute global launcher `node ~/.myco/launcher.cjs <command> [args]`, which resolves the same pins.
350
329
 
351
330
  ### Reprocessing sessions
352
331
 
353
332
  If observations were lost due to a bug, or if you want to re-extract observations with a different LLM, run the `reprocess` command:
354
333
 
355
334
  ```
356
- node .agents/myco-cli.cjs reprocess
335
+ myco reprocess
357
336
  ```
358
337
 
359
338
  This re-reads all session transcripts, re-extracts observations, and re-indexes everything. Existing spores are preserved — new observations are additive.
@@ -365,9 +344,9 @@ Options:
365
344
  ### Digest management
366
345
 
367
346
  ```
368
- node .agents/myco-cli.cjs digest # Run incremental digest cycle
369
- node .agents/myco-cli.cjs digest --tier 3000 # Reprocess a specific tier (clean slate)
370
- node .agents/myco-cli.cjs digest --full # Reprocess all tiers from scratch
347
+ myco digest # Run incremental digest cycle
348
+ myco digest --tier 3000 # Reprocess a specific tier (clean slate)
349
+ myco digest --full # Reprocess all tiers from scratch
371
350
  ```
372
351
 
373
352
  ### Vault intelligence
@@ -375,8 +354,8 @@ node .agents/myco-cli.cjs digest --full # Reprocess all tiers from scratch
375
354
  Supersession happens automatically on every spore write. For vault-wide cleanup, see `references/cli-usage.md` for full flags:
376
355
 
377
356
  ```
378
- node .agents/myco-cli.cjs agent # Run the intelligence agent
379
- node .agents/myco-cli.cjs agent --dry-run # Preview without writing
357
+ myco agent # Run the intelligence agent
358
+ myco agent --dry-run # Preview without writing
380
359
  ```
381
360
 
382
361
  For patterns on when to manually supersede or consolidate, see `references/wisdom.md`.
@@ -384,10 +363,10 @@ For patterns on when to manually supersede or consolidate, see `references/wisdo
384
363
  ### Other maintenance commands
385
364
 
386
365
  ```
387
- node .agents/myco-cli.cjs version # Check plugin version
388
- node .agents/myco-cli.cjs rebuild # Re-index all records
389
- node .agents/myco-cli.cjs stats # Check vault health
390
- node .agents/myco-cli.cjs verify # Test embedding/provider connectivity
391
- node .agents/myco-cli.cjs setup-llm --show
392
- node .agents/myco-cli.cjs setup-llm --embedding-provider ollama --embedding-model bge-m3
366
+ myco version # Check plugin version
367
+ myco rebuild # Re-index all records
368
+ myco stats # Check vault health
369
+ myco verify # Test embedding/provider connectivity
370
+ myco setup-llm --show
371
+ myco setup-llm --embedding-provider ollama --embedding-model bge-m3
393
372
  ```
package/skills/myco/references/cli-usage.md CHANGED
@@ -1,10 +1,10 @@
1
1
  # Myco CLI Reference
2
2
 
3
- In an initialized project, prefer the project-resolved launcher:
3
+ In an initialized project, prefer the `myco` CLI:
4
4
 
5
- node .agents/myco-cli.cjs <command> [flags]
5
+ myco <command> [flags]
6
6
 
7
- It honors project and worktree runtime pins. Use a plugin-root `dist/src/cli.js` path only when `.agents/myco-cli.cjs` is unavailable and you are deliberately operating inside an installed plugin bundle.
7
+ It honors project and worktree runtime pins — the binary walks up from the working directory for `.myco/runtime.command`. When `myco` is not on PATH (e.g. GUI- or launchd-spawned agents), use the absolute global launcher `node ~/.myco/launcher.cjs <command> [flags]`, which resolves the same pins.
8
8
 
9
9
  ---
10
10
 
@@ -27,7 +27,7 @@ Initializes a new Myco vault. Skipped automatically if the vault is already init
27
27
  **Example:**
28
28
 
29
29
  ```sh
30
- node .agents/myco-cli.cjs init \
30
+ myco init \
31
31
  --embedding-provider ollama \
32
32
  --embedding-model bge-m3
33
33
  ```
@@ -51,10 +51,10 @@ Note: changing the embedding model requires running `rebuild` afterward to re-em
51
51
 
52
52
  ```sh
53
53
  # Show current settings
54
- node .agents/myco-cli.cjs setup-llm --show
54
+ myco setup-llm --show
55
55
 
56
56
  # Change embedding model
57
- node .agents/myco-cli.cjs setup-llm \
57
+ myco setup-llm \
58
58
  --embedding-provider ollama \
59
59
  --embedding-model bge-m3
60
60
  ```
@@ -75,16 +75,16 @@ Direct access to vault config via dot-path notation. Values are parsed as JSON f
75
75
 
76
76
  ```sh
77
77
  # Read a value
78
- node .agents/myco-cli.cjs config get cortex.instructions.inject_on_session_start
78
+ myco config get cortex.instructions.inject_on_session_start
79
79
 
80
80
  # Write a value
81
- node .agents/myco-cli.cjs config set cortex.instructions.inject_on_session_start true
81
+ myco config set cortex.instructions.inject_on_session_start true
82
82
 
83
83
  # Write a non-string value (parsed as JSON)
84
- node .agents/myco-cli.cjs config set cortex.spores.max_per_prompt 3
84
+ myco config set cortex.spores.max_per_prompt 3
85
85
  ```
86
86
 
87
- Restart the daemon after changes that affect runtime behavior: `node .agents/myco-cli.cjs restart`
87
+ Restart the daemon after changes that affect runtime behavior: `myco restart`
88
88
 
89
89
  ---
90
90
 
@@ -115,7 +115,7 @@ Sends a test embed to the configured embedding provider. Exits 0 if it passes, 1
115
115
  No flags.
116
116
 
117
117
  ```sh
118
- node .agents/myco-cli.cjs verify
118
+ myco verify
119
119
  ```
120
120
 
121
121
  ---
@@ -127,7 +127,7 @@ Shows session/spore/plan counts, spore type breakdown, vector count, and daemon
127
127
  No flags.
128
128
 
129
129
  ```sh
130
- node .agents/myco-cli.cjs stats
130
+ myco stats
131
131
  ```
132
132
 
133
133
  Typical output:
@@ -160,13 +160,13 @@ Components: `processor`, `embeddings`, `hooks`, `lifecycle`, `daemon`, `lineage`
160
160
 
161
161
  ```sh
162
162
  # Show last 20 lines
163
- node .agents/myco-cli.cjs logs -n 20
163
+ myco logs -n 20
164
164
 
165
165
  # Follow errors from the processor
166
- node .agents/myco-cli.cjs logs -f -l error -c processor
166
+ myco logs -f -l error -c processor
167
167
 
168
168
  # Show logs from a specific window
169
- node .agents/myco-cli.cjs logs \
169
+ myco logs \
170
170
  --since 2025-01-01T10:00:00Z \
171
171
  --until 2025-01-01T11:00:00Z
172
172
  ```
@@ -180,7 +180,7 @@ node .agents/myco-cli.cjs logs \
180
180
  Runs semantic search (primary) with FTS fallback across sessions, spores, and plans.
181
181
 
182
182
  ```sh
183
- node .agents/myco-cli.cjs search "why did we choose sqlite over postgres"
183
+ myco search "why did we choose sqlite over postgres"
184
184
  ```
185
185
 
186
186
  ---
@@ -190,7 +190,7 @@ node .agents/myco-cli.cjs search "why did we choose sqlite over postgres"
190
190
  Shows all results with similarity scores and no threshold filtering. Useful for tuning embedding thresholds.
191
191
 
192
192
  ```sh
193
- node .agents/myco-cli.cjs vectors "session lifecycle hooks"
193
+ myco vectors "session lifecycle hooks"
194
194
  ```
195
195
 
196
196
  ---
@@ -204,10 +204,10 @@ node .agents/myco-cli.cjs vectors "session lifecycle hooks"
204
204
 
205
205
  ```sh
206
206
  # Show latest session
207
- node .agents/myco-cli.cjs session
207
+ myco session
208
208
 
209
209
  # Show a specific session by partial ID
210
- node .agents/myco-cli.cjs session ac5220
210
+ myco session ac5220
211
211
  ```
212
212
 
213
213
  ---
@@ -221,7 +221,7 @@ Sends SIGTERM to the running daemon, waits for it to exit, and spawns a fresh in
221
221
  No flags.
222
222
 
223
223
  ```sh
224
- node .agents/myco-cli.cjs restart
224
+ myco restart
225
225
  ```
226
226
 
227
227
  Run this after any daemon code changes to pick up new behavior.
@@ -235,7 +235,7 @@ Re-indexes all records. Superseded and archived spores are skipped.
235
235
  No flags.
236
236
 
237
237
  ```sh
238
- node .agents/myco-cli.cjs rebuild
238
+ myco rebuild
239
239
  ```
240
240
 
241
241
  Run this after changing the embedding model (via `setup-llm`) to regenerate all embeddings with the new model.
@@ -257,13 +257,13 @@ When `--tier` or `--full` is used, the cycle reads all records (ignoring the las
257
257
 
258
258
  ```sh
259
259
  # Run an incremental cycle (same as what the metabolism timer does)
260
- node .agents/myco-cli.cjs digest
260
+ myco digest
261
261
 
262
262
  # Reprocess tier 3000 from scratch
263
- node .agents/myco-cli.cjs digest --tier 3000
263
+ myco digest --tier 3000
264
264
 
265
265
  # Full rebuild of all tiers
266
- node .agents/myco-cli.cjs digest --full
266
+ myco digest --full
267
267
  ```
268
268
 
269
269
  ---
@@ -282,10 +282,10 @@ Runs the intelligence agent to process unprocessed session data, extract observa
282
282
 
283
283
  ```sh
284
284
  # Run the default intelligence task
285
- node .agents/myco-cli.cjs agent
285
+ myco agent
286
286
 
287
287
  # Preview what would be changed
288
- node .agents/myco-cli.cjs agent --dry-run
288
+ myco agent --dry-run
289
289
  ```
290
290
 
291
291
  Note: `--dry-run` still runs LLM calls (to evaluate) — it just skips the writes. Use it to review before running on a vault for the first time.
@@ -305,13 +305,13 @@ Re-reads session transcripts, re-extracts observations with the current LLM, and
305
305
 
306
306
  ```sh
307
307
  # Reprocess all sessions
308
- node .agents/myco-cli.cjs reprocess
308
+ myco reprocess
309
309
 
310
310
  # Reprocess one session
311
- node .agents/myco-cli.cjs reprocess --session ac5220
311
+ myco reprocess --session ac5220
312
312
 
313
313
  # Re-index without re-extracting
314
- node .agents/myco-cli.cjs reprocess --index-only
314
+ myco reprocess --index-only
315
315
  ```
316
316
 
317
317
  ---
@@ -321,7 +321,7 @@ node .agents/myco-cli.cjs reprocess --index-only
321
321
  ### `version` — Show plugin version
322
322
 
323
323
  ```sh
324
- node .agents/myco-cli.cjs version
324
+ myco version
325
325
  ```
326
326
 
327
327
  Also available as `--version` or `-v`.
package/skills/myco/references/reconfiguration.md CHANGED
@@ -15,24 +15,24 @@ Follow this order:
15
15
 
16
16
  ```bash
17
17
  # 1. Detect local providers when choosing a local embedding backend
18
- node .agents/myco-cli.cjs detect-providers
18
+ myco detect-providers
19
19
 
20
20
  # 2. Show current Grove-tier embedding settings
21
- node .agents/myco-cli.cjs setup-llm --show
21
+ myco setup-llm --show
22
22
 
23
23
  # 3. Apply only the requested embedding changes
24
- node .agents/myco-cli.cjs setup-llm \
24
+ myco setup-llm \
25
25
  --embedding-provider <provider> \
26
26
  --embedding-model <model>
27
27
 
28
28
  # 4. Restart daemon so runtime reads the new config
29
- node .agents/myco-cli.cjs restart
29
+ myco restart
30
30
 
31
31
  # 5. Rebuild vectors if the embedding model changed
32
- node .agents/myco-cli.cjs rebuild
32
+ myco rebuild
33
33
 
34
34
  # 6. Verify embedding connectivity
35
- node .agents/myco-cli.cjs verify
35
+ myco verify
36
36
  ```
37
37
 
38
38
  If only the embedding URL changed and the provider/model stayed the same, restart and verify are enough. If the embedding model changed, tell the user: "Changing the embedding model requires a full vector index rebuild. This may take a few minutes."
@@ -40,9 +40,9 @@ If only the embedding URL changed and the provider/model stayed the same, restar
40
40
  ## Viewing Current Settings
41
41
 
42
42
  ```bash
43
- node .agents/myco-cli.cjs setup-llm --show
44
- node .agents/myco-cli.cjs config get cortex.instructions.inject_on_session_start
45
- node .agents/myco-cli.cjs config get cortex.digest.inject_on_session_start
43
+ myco setup-llm --show
44
+ myco config get cortex.instructions.inject_on_session_start
45
+ myco config get cortex.digest.inject_on_session_start
46
46
  ```
47
47
 
48
48
  Prefer `setup-llm --show` for embedding settings instead of raw config reads; it resolves the Grove tier correctly.
@@ -52,29 +52,29 @@ Prefer `setup-llm --show` for embedding settings instead of raw config reads; it
52
52
  ### "Change my embedding model"
53
53
 
54
54
  ```bash
55
- node .agents/myco-cli.cjs setup-llm --embedding-model bge-m3
56
- node .agents/myco-cli.cjs restart
57
- node .agents/myco-cli.cjs rebuild
58
- node .agents/myco-cli.cjs verify
55
+ myco setup-llm --embedding-model bge-m3
56
+ myco restart
57
+ myco rebuild
58
+ myco verify
59
59
  ```
60
60
 
61
61
  ### "Switch embedding provider"
62
62
 
63
63
  ```bash
64
- node .agents/myco-cli.cjs detect-providers
65
- node .agents/myco-cli.cjs setup-llm \
64
+ myco detect-providers
65
+ myco setup-llm \
66
66
  --embedding-provider ollama \
67
67
  --embedding-model bge-m3
68
- node .agents/myco-cli.cjs restart
69
- node .agents/myco-cli.cjs rebuild
70
- node .agents/myco-cli.cjs verify
68
+ myco restart
69
+ myco rebuild
70
+ myco verify
71
71
  ```
72
72
 
73
73
  ### "Enable or disable Cortex instruction injection"
74
74
 
75
75
  ```bash
76
- node .agents/myco-cli.cjs config set cortex.instructions.inject_on_session_start true
77
- node .agents/myco-cli.cjs restart
76
+ myco config set cortex.instructions.inject_on_session_start true
77
+ myco restart
78
78
  ```
79
79
 
80
80
  Use the Settings UI when possible for scoped config edits; it shows whether a value is machine, Grove, project, or local.
package/skills/myco/references/vault-status.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  This reference guides vault health assessment. Use it whenever you need to inspect the state of the Myco vault — whether debugging a problem, responding to a user's question about their vault, or running a routine check.
4
4
 
5
- **Primary data source:** `node .agents/myco-cli.cjs stats`
5
+ **Primary data source:** `myco stats`
6
6
 
7
7
  Supplement with `logs` for recent daemon activity and `myco_cortex` for Cortex/digest status.
8
8
 
@@ -13,7 +13,7 @@ Supplement with `logs` for recent daemon activity and `myco_cortex` for Cortex/d
13
13
  Run the stats command to get a snapshot of vault state:
14
14
 
15
15
  ```sh
16
- node .agents/myco-cli.cjs stats
16
+ myco stats
17
17
  ```
18
18
 
19
19
  The output includes:
@@ -55,7 +55,7 @@ The daemon runs as a background HTTP process. Its state is persisted in `<vault>
55
55
  You can also restart it manually:
56
56
 
57
57
  ```sh
58
- node .agents/myco-cli.cjs restart
58
+ myco restart
59
59
  ```
60
60
 
61
61
  Do not treat a stopped daemon as a vault error — it is normal between sessions. The daemon starts on demand when a session begins.
@@ -75,8 +75,8 @@ Read scoped Cortex config through the UI or config surface. The session-start to
75
75
  Use `myco_cortex` to request the tier you care about:
76
76
 
77
77
  ```sh
78
- node .agents/myco-cli.cjs tool call myco_cortex --json --input '{"op":"digest","tier":1500}'
79
- node .agents/myco-cli.cjs tool call myco_cortex --json --input '{"op":"digest","tier":5000}'
78
+ myco tool call myco_cortex --json --input '{"op":"digest","tier":1500}'
79
+ myco tool call myco_cortex --json --input '{"op":"digest","tier":5000}'
80
80
  ```
81
81
 
82
82
  Missing or not-ready responses mean the digest has not been generated for that tier yet or Cortex is disabled for the project.
@@ -88,13 +88,13 @@ Missing or not-ready responses mean the digest has not been generated for that t
88
88
  Test connectivity to the configured embedding provider:
89
89
 
90
90
  ```sh
91
- node .agents/myco-cli.cjs verify
91
+ myco verify
92
92
  ```
93
93
 
94
94
  This reports whether the embedding provider is reachable. The Myco agent LLM is managed by the agent harness. If embedding verification fails:
95
95
 
96
96
  - Check that the provider process is running (Ollama, LM Studio, etc.)
97
- - Review Grove-tier embedding settings with `node .agents/myco-cli.cjs setup-llm --show`
97
+ - Review Grove-tier embedding settings with `myco setup-llm --show`
98
98
  - Re-run configuration with `setup-llm`
99
99
 
100
100
  ---
@@ -106,9 +106,9 @@ Check for these problems when assessing vault health:
106
106
  | Issue | How to detect | Meaning |
107
107
  |-------|--------------|---------|
108
108
  | **Stale buffers** | `.jsonl` files in `<vault>/buffer/` older than 24 hours | Events were captured but never processed — LLM may have been unavailable |
109
- | **Missing vault DB** | `<vault>/myco.db` does not exist | The vault database is missing or the project is not initialized; suggest `myco init` or check vault resolution |
109
+ | **Missing vault DB** | `<vault>/myco.db` does not exist | The Grove database is missing or the project hasn't been auto-registered yet; check daemon status and that an agent has fired a hook from this project |
110
110
  | **Missing vectors** | `<vault>/vectors.db` does not exist | Semantic search disabled; embeddings may be unconfigured |
111
- | **Old config version** | `version` in `myco.yaml` is stale | Vault may need migration; suggest running `myco init` or `myco update` |
111
+ | **Old config version** | `version` in `myco.yaml` is stale | Vault may need migration; suggest running `myco update` |
112
112
 
113
113
  Report all issues found, or "None found." if the vault is clean.
114
114
 
@@ -119,7 +119,7 @@ Report all issues found, or "None found." if the vault is clean.
119
119
  View recent daemon log output:
120
120
 
121
121
  ```sh
122
- node .agents/myco-cli.cjs logs -n 20
122
+ myco logs -n 20
123
123
  ```
124
124
 
125
125
  This shows the last 20 lines of daemon logs — useful for spotting errors, slow processing, or repeated failures.
@@ -198,8 +198,8 @@ Lineage tracks parent-child relationships between sessions. A high count of `sem
198
198
 
199
199
  | Issue | Action |
200
200
  |-------|--------|
201
- | Daemon not running | Will auto-start on next session; or run `node .agents/myco-cli.cjs restart` |
201
+ | Daemon not running | Will auto-start on next session; or run `myco restart` |
202
202
  | Stale buffers | Check if LLM provider was down during those sessions; events will process on next daemon start |
203
- | Missing index | Run `node .agents/myco-cli.cjs rebuild` to regenerate FTS and vector indexes |
203
+ | Missing index | Run `myco rebuild` to regenerate FTS and vector indexes |
204
204
  | Provider unreachable | Ensure the provider is running (e.g., `ollama serve`); verify model name in `myco.yaml`; reconfigure with CLI commands |
205
- | Config version < 2 | Run `myco init` to migrate the vault configuration |
205
+ | Config version < 2 | Run `myco update` to migrate the vault configuration |
package/skills/myco/references/wisdom.md CHANGED
@@ -8,8 +8,8 @@ Myco automatically checks for supersession every time a new spore is written. Af
8
8
 
9
9
  For vault-wide cleanup (e.g., after a large refactor), use the CLI:
10
10
  ```sh
11
- node .agents/myco-cli.cjs agent --dry-run # preview
12
- node .agents/myco-cli.cjs agent # execute
11
+ myco agent --dry-run # preview
12
+ myco agent # execute
13
13
  ```
14
14
 
15
15
  ## Supersede