@kl-c/matrixos 0.1.15 → 0.1.17

package/.agents/command/adopt.md

@@ -16,7 +16,15 @@ Check whether `/root/MOS_Vault/04-Areas/user-context.md` exists and is filled.
 - If filled: tell the user "Tu as déjà un contexte d'adoption. Je relance le rituel pour le mettre à jour." and proceed to step 2 (re-adoption mode — EDIT sections, do NOT rewrite from scratch).
 - If missing/template: adoption mode — you will CREATE the file.
 
-### 2. Ask the adoption questions (in conversation, French, interactive `question` tool)
+### 2. Inform the user of base capabilities (DO THIS EARLY)
+Before or right after the questions, tell the user what MaTrixOS already gives them out of the box — so they know what they have at their disposal without having to ask:
+- **Mission Control (Dashboard)** — real-time web UI (agents, sessions, tasks, cost, incidents). Launch anytime with `matrixos dashboard --daemon` (http://127.0.0.1:9123; `--host <tailscale-ip>` for remote).
+- **16-agent team** — Morpheus + specialists (Neo, Tank, Oracle, Trinity, Cypher, Sentinel, etc.). Delegate, don't do it all yourself.
+- **Messaging Gateway** (opt-in) — drive Morpheus from Telegram/Discord/WhatsApp.
+- **Learning Loop** + **Team Mode** (opt-in).
+Keep it to one short paragraph — this is awareness, not the opt-in checklist (that's step 3).
+
+### 3. Ask the adoption questions (in conversation, French, interactive `question` tool)
 Pose ~5 targeted questions:
 1. **Qui es-tu ?** (nom/alias, rôle, ce que tu fais)
 2. **Pour quel projet / besoin m'as-tu déployé ?** (objectif, stack, périmètre)
@@ -36,6 +44,7 @@ Ask the user which they want activated. Confirm specifically the **Dashboard (Mi
 Write/edit `/root/MOS_Vault/04-Areas/user-context.md`:
 - Adoption mode: fill sections 1–4, set `last_verified` to today, add a line in section 5 (Mises à jour) with today's date.
 - Re-adoption mode: edit only the sections the user changed; update `last_verified`; append a line in section 5.
+- **ALWAYS add a `## Features` section** (even in re-adoption) listing which opt-in features the user chose to activate (e.g. `Dashboard: activé`, `Kanban: non`, etc.). This marker tells the auto-adoption trigger that the feature checklist was presented — without it, the ritual will re-run on next launch.
 Never rewrite the whole file from scratch — preserve existing context.
 
 Also update `/root/MOS_Vault/MEMORY.md` routing if the user-context file was just created.

package/.opencode/command/adopt.md

@@ -16,7 +16,15 @@ Check whether `/root/MOS_Vault/04-Areas/user-context.md` exists and is filled.
 - If filled: tell the user "Tu as déjà un contexte d'adoption. Je relance le rituel pour le mettre à jour." and proceed to step 2 (re-adoption mode — EDIT sections, do NOT rewrite from scratch).
 - If missing/template: adoption mode — you will CREATE the file.
 
-### 2. Ask the adoption questions (in conversation, French, interactive `question` tool)
+### 2. Inform the user of base capabilities (DO THIS EARLY)
+Before or right after the questions, tell the user what MaTrixOS already gives them out of the box — so they know what they have at their disposal without having to ask:
+- **Mission Control (Dashboard)** — real-time web UI (agents, sessions, tasks, cost, incidents). Launch anytime with `matrixos dashboard --daemon` (http://127.0.0.1:9123; `--host <tailscale-ip>` for remote).
+- **16-agent team** — Morpheus + specialists (Neo, Tank, Oracle, Trinity, Cypher, Sentinel, etc.). Delegate, don't do it all yourself.
+- **Messaging Gateway** (opt-in) — drive Morpheus from Telegram/Discord/WhatsApp.
+- **Learning Loop** + **Team Mode** (opt-in).
+Keep it to one short paragraph — this is awareness, not the opt-in checklist (that's step 3).
+
+### 3. Ask the adoption questions (in conversation, French, interactive `question` tool)
 Pose ~5 targeted questions:
 1. **Qui es-tu ?** (nom/alias, rôle, ce que tu fais)
 2. **Pour quel projet / besoin m'as-tu déployé ?** (objectif, stack, périmètre)
@@ -36,6 +44,7 @@ Ask the user which they want activated. Confirm specifically the **Dashboard (Mi
 Write/edit `/root/MOS_Vault/04-Areas/user-context.md`:
 - Adoption mode: fill sections 1–4, set `last_verified` to today, add a line in section 5 (Mises à jour) with today's date.
 - Re-adoption mode: edit only the sections the user changed; update `last_verified`; append a line in section 5.
+- **ALWAYS add a `## Features` section** (even in re-adoption) listing which opt-in features the user chose to activate (e.g. `Dashboard: activé`, `Kanban: non`, etc.). This marker tells the auto-adoption trigger that the feature checklist was presented — without it, the ritual will re-run on next launch.
 Never rewrite the whole file from scratch — preserve existing context.
 
 Also update `/root/MOS_Vault/MEMORY.md` routing if the user-context file was just created.

package/dist/agents/dynamic-agent-core-sections.d.ts

@@ -22,3 +22,12 @@ export declare function buildOracleSection(agents: AvailableAgent[]): string;
 export declare function buildFrontendGuidanceSection(categories: AvailableCategory[]): string;
 export declare function buildNonClaudePlannerSection(model: string): string;
 export declare function buildParallelDelegationSection(model: string, categories: AvailableCategory[]): string;
+/**
+ * Base capabilities awareness — what Morpheus knows about out of the box,
+ * without needing to read features.ts or run /features. The Dashboard
+ * (Mission Control) backend is always bundled; the user can launch it
+ * immediately. Listed here so Morpheus is never "lost" when the user
+ * mentions these features in conversation (VPS cantabo bug: Morpheus had
+ * to grep the codebase to discover the dashboard existed).
+ */
+export declare function buildBaseCapabilitiesSection(): string;

package/dist/agents/morpheus-dynamic-prompt-sections.d.ts

@@ -2,6 +2,7 @@ import type { AvailableAgent, AvailableCategory, AvailableSkill, AvailableTool }
 export interface MorpheusDynamicPromptSections {
     readonly agentIdentity: string;
     readonly agentTeam: string;
+    readonly baseCapabilities: string;
     readonly antiPatterns: string;
     readonly categorySkillsGuide: string;
     readonly delegationTable: string;

package/dist/cli/index.js

@@ -2145,7 +2145,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@kl-c/matrixos",
-    version: "0.1.15",
+    version: "0.1.17",
     description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
     main: "./dist/index.js",
     types: "dist/index.d.ts",

package/dist/cli-node/index.js

@@ -2145,7 +2145,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@kl-c/matrixos",
-    version: "0.1.15",
+    version: "0.1.17",
     description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
     main: "./dist/index.js",
     types: "dist/index.d.ts",

package/dist/features/matrix-inventory/features.js

@@ -5,8 +5,8 @@ var MATRIX_FEATURES = [
     id: "dashboard",
     name: "Mission Control (Dashboard)",
     description: "Web UI to supervise agents, sessions, tasks, cost and incidents in real time.",
-    enabledByDefault: false,
-    status: "cli-only",
+    enabledByDefault: true,
+    status: "native",
     userBenefit: "Open a browser page (default http://127.0.0.1:9123) showing live agent/session/task state, cost, kanban and incidents.",
     provisioning: {
       activation: "Launch the bundled server: `matrixos dashboard --daemon` (listens on 127.0.0.1:9123 by default). For remote access over Tailscale, rebind with `--host <tailscale-ip>` (e.g. 100.96.138.13).",

package/dist/index.js

@@ -196791,7 +196791,7 @@ var require_filesystem = __commonJS((exports, module) => {
   var LDD_PATH = "/usr/bin/ldd";
   var SELF_PATH = "/proc/self/exe";
   var MAX_LENGTH = 2048;
-  var readFileSync77 = (path28) => {
+  var readFileSync78 = (path28) => {
     const fd = fs26.openSync(path28, "r");
     const buffer = Buffer.alloc(MAX_LENGTH);
     const bytesRead = fs26.readSync(fd, buffer, 0, MAX_LENGTH, 0);
@@ -196814,7 +196814,7 @@ var require_filesystem = __commonJS((exports, module) => {
   module.exports = {
     LDD_PATH,
     SELF_PATH,
-    readFileSync: readFileSync77,
+    readFileSync: readFileSync78,
     readFile: readFile14
   };
 });
@@ -196857,7 +196857,7 @@ var require_elf = __commonJS((exports, module) => {
 var require_detect_libc = __commonJS((exports, module) => {
   var childProcess3 = __require("child_process");
   var { isLinux, getReport } = require_process();
-  var { LDD_PATH, SELF_PATH, readFile: readFile14, readFileSync: readFileSync77 } = require_filesystem();
+  var { LDD_PATH, SELF_PATH, readFile: readFile14, readFileSync: readFileSync78 } = require_filesystem();
   var { interpreterPath } = require_elf();
   var cachedFamilyInterpreter;
   var cachedFamilyFilesystem;
@@ -196948,7 +196948,7 @@ var require_detect_libc = __commonJS((exports, module) => {
     }
     cachedFamilyFilesystem = null;
     try {
-      const lddContent = readFileSync77(LDD_PATH);
+      const lddContent = readFileSync78(LDD_PATH);
       cachedFamilyFilesystem = getFamilyFromLddContent(lddContent);
     } catch (e) {}
     return cachedFamilyFilesystem;
@@ -196971,7 +196971,7 @@ var require_detect_libc = __commonJS((exports, module) => {
     }
     cachedFamilyInterpreter = null;
     try {
-      const selfContent = readFileSync77(SELF_PATH);
+      const selfContent = readFileSync78(SELF_PATH);
       const path28 = interpreterPath(selfContent);
       cachedFamilyInterpreter = familyFromInterpreterPath(path28);
     } catch (e) {}
@@ -197033,7 +197033,7 @@ var require_detect_libc = __commonJS((exports, module) => {
     }
     cachedVersionFilesystem = null;
     try {
-      const lddContent = readFileSync77(LDD_PATH);
+      const lddContent = readFileSync78(LDD_PATH);
       const versionMatch = lddContent.match(RE_GLIBC_VERSION);
       if (versionMatch) {
         cachedVersionFilesystem = versionMatch[1];
@@ -297183,13 +297183,13 @@ var init_merge = __esm(() => {
 });
 
 // packages/omo-config-core/src/loader/types.ts
-import { existsSync as existsSync115, lstatSync as lstatSync5, readFileSync as readFileSync77 } from "fs";
+import { existsSync as existsSync115, lstatSync as lstatSync5, readFileSync as readFileSync78 } from "fs";
 var DEFAULT_READ_FILE_SYSTEM;
 var init_types7 = __esm(() => {
   DEFAULT_READ_FILE_SYSTEM = {
     existsSync: existsSync115,
     lstatSync: lstatSync5,
-    readFileSync: readFileSync77
+    readFileSync: readFileSync78
   };
 });
 
@@ -297507,7 +297507,7 @@ import {
   existsSync as existsSync116,
   lstatSync as lstatSync6,
   mkdirSync as mkdirSync25,
-  readFileSync as readFileSync78,
+  readFileSync as readFileSync79,
   readdirSync as readdirSync29,
   renameSync as renameSync10,
   unlinkSync as unlinkSync17,
@@ -297520,7 +297520,7 @@ var init_types8 = __esm(() => {
     existsSync: existsSync116,
     lstatSync: lstatSync6,
     mkdirSync: mkdirSync25,
-    readFileSync: readFileSync78,
+    readFileSync: readFileSync79,
     readdirSync: readdirSync29,
     renameSync: renameSync10,
     unlinkSync: unlinkSync17,
@@ -367932,7 +367932,7 @@ function getCachedVersion(options = {}) {
 // package.json
 var package_default = {
   name: "@kl-c/matrixos",
-  version: "0.1.15",
+  version: "0.1.17",
   description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
   main: "./dist/index.js",
   types: "dist/index.d.ts",
@@ -421414,6 +421414,21 @@ function buildParallelDelegationSection(model, categories) {
 
 **Your value is orchestration, decomposition, and quality control. Delegating with crystal-clear prompts IS your work.**`;
 }
+function buildBaseCapabilitiesSection() {
+  return `### Base Capabilities (you already have these)
+
+These ship with MaTrixOS and are part of your baseline awareness \u2014 you do
+NOT need to discover them by searching the code. When the user mentions one,
+you already know what it is and how to activate it:
+
+- **Mission Control (Dashboard)** \u2014 real-time web UI to supervise agents, sessions, tasks, cost and incidents. Backend is always bundled. Launch with \`matrixos dashboard --daemon\` (serves on http://127.0.0.1:9123). For remote access over Tailscale, rebind with \`--host <tailscale-ip>\`.
+- **Messaging Gateway** \u2014 drive Morpheus from Telegram / Discord / WhatsApp. Opt-in: set \`gateway.enabled: true\` in matrixos.json + a channel entry with the bot token via ENV (never inline). See \`/features gateway\` for the full recipe.
+- **Learning Loop** \u2014 L1\u2192L2 self-improvement; MaTrixOS proposes learnings from your session history.
+- **Team Mode** \u2014 spawn parallel sub-agent teams (up to 8 members). Opt-in via \`team_mode.enabled\`.
+- **16-agent team** \u2014 listed above. Delegate, do not implement yourself when a specialist exists.
+
+For the full, on-demand inventory (including opt-in features like Kanban, Cron, Goal Mode), use \`/features\`. To (re)run the adoption ritual and choose opt-in features, use \`/adopt\`.`;
+}
 // packages/omo-opencode/src/agents/dynamic-agent-category-skills-guide.ts
 function buildSkillsSection(skills) {
   const builtinSkills = skills.filter((skill2) => skill2.location === "plugin");
@@ -421905,6 +421920,8 @@ You are "Morpheus" - the orchestrator of MaTrixOS, an agentic OS built as a fork
 
 ${sections.agentTeam}
 
+${sections.baseCapabilities}
+
 </Role>
 <Behavior_Instructions>
 
@@ -422135,6 +422152,7 @@ function buildMorpheusDynamicPromptSections(model, availableAgents, availableToo
   return {
     agentIdentity: buildAgentIdentitySection("Morpheus", "Powerful AI Agent with orchestration capabilities from MaTrixOS \u2014 a fork of OMO improved with Hermes, OpenClaw and Goose strengths, model-agnostic (open/standard models, never locked to a proprietary provider)"),
     agentTeam: buildMatrixOSAgentTeamSection(),
+    baseCapabilities: buildBaseCapabilitiesSection(),
     antiPatterns: buildAntiPatternsSection(),
     categorySkillsGuide: buildCategorySkillsDelegationGuide(availableCategories, availableSkills),
     delegationTable: buildDelegationTable(availableAgents),
@@ -438539,7 +438557,7 @@ function createChatHeadersHandler(args) {
 }
 
 // packages/omo-opencode/src/plugin/auto-adoption.ts
-import { existsSync as existsSync111 } from "fs";
+import { existsSync as existsSync111, readFileSync as readFileSync76 } from "fs";
 import { join as join133 } from "path";
 import { homedir as homedir35 } from "os";
 var ADOPTION_CONTEXT_RELATIVE = join133("MOS_Vault", "04-Areas", "user-context.md");
@@ -438548,9 +438566,17 @@ function resolveUserContextPath() {
   return join133(base, "04-Areas", "user-context.md");
 }
 function isAdoptionNeeded() {
-  return !existsSync111(resolveUserContextPath());
+  const path26 = resolveUserContextPath();
+  if (!existsSync111(path26))
+    return true;
+  try {
+    const content = readFileSync76(path26, "utf8");
+    return !/features/i.test(content);
+  } catch {
+    return true;
+  }
 }
-var ADOPTION_TRIGGER_INSTRUCTION = `SYST\xC8ME \u2014 Rituel d'adoption automatique : aucun contexte utilisateur (user-context.md) n'est configur\xE9. Lance imm\xE9diatement le rituel d'adoption comme si l'utilisateur avait tap\xE9 /adopt : pose les 5 questions (identit\xE9, projet, contraintes, style de collaboration, reporting), puis propose les fonctionnalit\xE9s opt-in (\u5C24\u5176 Dashboard Mission Control sur 127.0.0.1:9123). Utilise l'outil question pour les questions. Ne r\xE9ponds pas encore \xE0 la demande de l'utilisateur \u2014 l'adoption prime.`;
+var ADOPTION_TRIGGER_INSTRUCTION = `SYST\xC8ME \u2014 Rituel d'adoption automatique : lance imm\xE9diatement le rituel d'adoption comme si l'utilisateur avait tap\xE9 /adopt. M\xEAme si un contexte utilisateur (user-context.md) existe d\xE9j\xE0, tu DOIS proposer les fonctionnalit\xE9s opt-in (especially Dashboard Mission Control sur 127.0.0.1:9123) \u2014 ne saute jamais cette \xE9tape. Pose les 5 questions (identit\xE9, projet, contraintes, style de collaboration, reporting), puis pr\xE9sente la checklist des fonctionnalit\xE9s opt-in depuis l'inventaire (OPT_IN_FEATURES). Utilise l'outil question pour les questions. Ne r\xE9ponds pas encore \xE0 la demande de l'utilisateur \u2014 l'adoption prime.`;
 
 // packages/omo-opencode/src/plugin/ultrawork-db-model-override.ts
 import { join as join134 } from "path";
@@ -444362,7 +444388,7 @@ init_plugin_identity();
 // packages/telemetry-core/src/activity-state.ts
 init_atomic_write();
 init_xdg_data_dir();
-import { existsSync as existsSync120, mkdirSync as mkdirSync27, readFileSync as readFileSync80 } from "fs";
+import { existsSync as existsSync120, mkdirSync as mkdirSync27, readFileSync as readFileSync81 } from "fs";
 import { basename as basename26, join as join144 } from "path";
 var POSTHOG_ACTIVITY_STATE_FILE = "posthog-activity.json";
 function resolveTelemetryStateDir(product, options = {}) {
@@ -444406,7 +444432,7 @@ function readPostHogActivityState(stateDir, diagnostics) {
     return {};
   }
   try {
-    const stateContent = readFileSync80(stateFilePath, "utf-8");
+    const stateContent = readFileSync81(stateFilePath, "utf-8");
     const stateJson = JSON.parse(stateContent);
     if (!isPostHogActivityState(stateJson)) {
       return {};

package/dist/plugin/auto-adoption.d.ts

@@ -1,3 +1,10 @@
-/** True when adoption context is missing (no user-context.md yet). */
+/**
+ * True when adoption is incomplete and the ritual should (re)run:
+ * - no user-context.md yet, OR
+ * - user-context.md exists but the opt-in features were never presented
+ *   (a user who already has context but never saw the feature checklist
+ *   would otherwise treat the truncated state as truth — see VPS cantabo,
+ *   where user-context.md existed but Dashboard/features were never offered).
+ */
 export declare function isAdoptionNeeded(): boolean;
-export declare const ADOPTION_TRIGGER_INSTRUCTION = "SYST\u00C8ME \u2014 Rituel d'adoption automatique : aucun contexte utilisateur (user-context.md) n'est configur\u00E9. Lance imm\u00E9diatement le rituel d'adoption comme si l'utilisateur avait tap\u00E9 /adopt : pose les 5 questions (identit\u00E9, projet, contraintes, style de collaboration, reporting), puis propose les fonctionnalit\u00E9s opt-in (\u5C24\u5176 Dashboard Mission Control sur 127.0.0.1:9123). Utilise l'outil question pour les questions. Ne r\u00E9ponds pas encore \u00E0 la demande de l'utilisateur \u2014 l'adoption prime.";
+export declare const ADOPTION_TRIGGER_INSTRUCTION = "SYST\u00C8ME \u2014 Rituel d'adoption automatique : lance imm\u00E9diatement le rituel d'adoption comme si l'utilisateur avait tap\u00E9 /adopt. M\u00EAme si un contexte utilisateur (user-context.md) existe d\u00E9j\u00E0, tu DOIS proposer les fonctionnalit\u00E9s opt-in (especially Dashboard Mission Control sur 127.0.0.1:9123) \u2014 ne saute jamais cette \u00E9tape. Pose les 5 questions (identit\u00E9, projet, contraintes, style de collaboration, reporting), puis pr\u00E9sente la checklist des fonctionnalit\u00E9s opt-in depuis l'inventaire (OPT_IN_FEATURES). Utilise l'outil question pour les questions. Ne r\u00E9ponds pas encore \u00E0 la demande de l'utilisateur \u2014 l'adoption prime.";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kl-c/matrixos",
-  "version": "0.1.15",
+  "version": "0.1.17",
   "description": "MaTrixOS — Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
   "main": "./dist/index.js",
   "types": "dist/index.d.ts",