morpheus-cli 0.9.4 → 0.9.6

package/dist/runtime/oracle.js

@@ -10,19 +10,21 @@ import { TaskRequestContext } from "./tasks/context.js";
 import { TaskRepository } from "./tasks/repository.js";
 import { Neo } from "./neo.js";
 import { Trinity } from "./trinity.js";
+import { Link } from "./link.js";
 import { SmithDelegateTool } from "./tools/smith-tool.js";
 import { TaskQueryTool, chronosTools, timeVerifierTool } from "./tools/index.js";
 import { Construtor } from "./tools/factory.js";
 import { MCPManager } from "../config/mcp-manager.js";
-import { SkillRegistry, SkillExecuteTool, SkillDelegateTool, updateSkillToolDescriptions } from "./skills/index.js";
+import { SkillRegistry, createLoadSkillTool } from "./skills/index.js";
 import { SmithRegistry } from "./smiths/registry.js";
 import { AuditRepository } from "./audit/repository.js";
 import { SetupRepository } from './setup/repository.js';
 import { buildSetupTool } from './tools/setup-tool.js';
 import { emitToolAuditEvents } from "./subagent-utils.js";
+import { PATHS } from "../config/paths.js";
+import { writeFileSync } from "fs";
 const ORACLE_DELEGATION_TOOLS = new Set([
-    'apoc_delegate', 'neo_delegate', 'trinity_delegate', 'smith_delegate',
-    'skill_delegate', 'skill_execute',
+    'apoc_delegate', 'neo_delegate', 'trinity_delegate', 'smith_delegate', 'link_delegate',
 ]);
 export class Oracle {
     provider;
@@ -119,7 +121,7 @@ export class Oracle {
             const toolCalls = msg.tool_calls ?? [];
             if (!Array.isArray(toolCalls))
                 continue;
-            if (toolCalls.some((tc) => tc?.name === "apoc_delegate" || tc?.name === "neo_delegate" || tc?.name === "trinity_delegate" || tc?.name === "smith_delegate")) {
+            if (toolCalls.some((tc) => tc?.name === "apoc_delegate" || tc?.name === "neo_delegate" || tc?.name === "trinity_delegate" || tc?.name === "smith_delegate" || tc?.name === "link_delegate")) {
                 return true;
             }
         }
@@ -154,7 +156,7 @@ export class Oracle {
             // Fail-open: Oracle can still initialize even if catalog refresh fails.
             await Neo.refreshDelegateCatalog().catch(() => { });
             await Trinity.refreshDelegateCatalog().catch(() => { });
-            updateSkillToolDescriptions();
+            await Link.refreshDelegateCatalog().catch(() => { });
             // Build tool list — conditionally include SmithDelegateTool based on config
             // Initialize setup repository (creates table if needed)
             SetupRepository.getInstance();
@@ -164,8 +166,8 @@ export class Oracle {
                 Neo.getInstance().createDelegateTool(),
                 Apoc.getInstance().createDelegateTool(),
                 Trinity.getInstance().createDelegateTool(),
-                SkillExecuteTool,
-                SkillDelegateTool,
+                Link.getInstance().createDelegateTool(),
+                createLoadSkillTool(),
                 timeVerifierTool,
                 ...chronosTools,
             ];
@@ -245,11 +247,14 @@ Do NOT proceed with other tasks until all required fields have been collected an
 `;
                 }
             }
-            const systemMessage = new SystemMessage(`${setupBlock}You are ${this.config.agent.name}, ${this.config.agent.personality}, the Oracle.
+            const systemMessage = new SystemMessage(`
+${setupBlock}
+
+You are ${this.config.agent.name}, ${this.config.agent.personality}, the Oracle.
 
 You are an orchestrator and task router.
 
-## Date & Time Resolution — MANDATORY
+## Date & Time Resolution — MANDATORY ##
 
 You **MUST** call "time_verifier" before answering or delegating ANY request that depends on the current date or time.
 This includes — but is not limited to — **two categories**:
@@ -269,7 +274,7 @@ This includes — but is not limited to — **two categories**:
 **NEVER assume or invent a date. NEVER guess "today is [date]".**
 Always call time_verifier first, then use the resolved date in your tool call or delegation prompt.
 
-Rules:
+## Rules: ##
 1. For conversation-only requests (greetings, conceptual explanation, memory follow-up, statements of fact, sharing personal information), answer directly. DO NOT create tasks or delegate for simple statements like "I have two cats" or "My name is John". Sati will automatically memorize facts in the background ( **ALWAYS** use SATI Memories to review or retrieve these facts if needed).
 **NEVER** Create data, use SATI memories to response on informal conversation or say that dont know abaout the awsor if the answer is in the memories. Always use the memories as source of truth for user facts, preferences, stable context and informal conversation. Use tools only for execution, verification or when external/system state is required.*
 2. For requests that require execution, verification, external/system state, or non-trivial operations, evaluate the available tools and choose the best one.
@@ -282,9 +287,42 @@ Rules:
 9. Avoid duplicate delegations to the same tool or agent.
 10. After enqueuing all required delegated tasks for the current message, stop calling tools and return a concise acknowledgement.
 11. If a delegation is rejected as "not atomic", immediately split into smaller delegations and retry.
-12. When the user message contains @neo, @apoc, or @trinity (case-insensitive), delegate to that specific agent. The mention is an explicit routing directive — respect it even if another agent might also handle the request.
+12. When the user message contains @link, @neo, @apoc, or @trinity (case-insensitive), delegate to that specific agent. The mention is an explicit routing directive — respect it even if another agent might also handle the request.
+13. Smiths also have names and could be called by @smithname — respect this as an explicit routing directive as well.
+
+## Delegation quality ##
+- Write delegation input in the same language requested by the user.
+- Include clear objective and constraints.
+- Include OS-aware guidance for network checks when relevant.
+- Use Sati memories only as context to complement the task, never as source of truth for dynamic data.
+- Use Sati memories to fill missing stable context fields (for example: city, timezone, language, currency, preferred units).
+- If Sati memory is conflicting or uncertain for a required field, ask one short clarification before delegating.
+- When completing missing fields from Sati, include explicit assumptions in delegation context using the format: "Assumption from Sati: key=value".
+- Never infer sensitive data from Sati memories (credentials, legal identifiers, health details, financial account data).
+- When assumptions were used, mention them briefly in the user-facing response and allow correction.
+- break the request into multiple delegations if it contains multiple independent actions.
+- Set a single task per delegation tool call. Do not combine multiple actions into one delegation, as it complicates execution and error handling.
+- If user requested N independent actions, produce N delegated tasks (or direct answers), each one singular and tool-scoped.
+- If use a delegation dont use the sati or messages history to answer directly in the same response. Just response with the delegations.
+Example 1:
+ask: "Tell me my account balance and do a ping on google.com"
+good:
+- delegate to "neo_delegate" with task "Check account balance using morpheus analytics MCP and return the result."
+- delegate to "apoc_delegate" with task "Ping google.com using the network diagnostics MCP and return reachability status. Use '-n' flag for Windows and '-c' for Linux/macOS."
+bad:
+- delegate to "neo_delegate" with task "Check account balance using morpheus analytics MCP and ping google.com using the network diagnostics MCP, then return both results." (combines two independent actions into one delegation, which is not atomic and complicates execution and error handling)
+
+Example 2:
+ask: "I have two cats" or "My name is John"
+good:
+- Answer directly acknowledging the fact. Do NOT delegate.
+bad:
+- delegate to "neo_delegate" or "apoc_delegate" to save the fact. (Sati handles this automatically in the background)
 
-## Chronos Channel Routing
+--------------------------------------------------
+          CHRONOS SCHEDULING RULES 
+--------------------------------------------------
+## Chronos Channel Routing ##
 When calling chronos_schedule, set notify_channels based on the user's message:
 - User mentions a specific channel (e.g., "no Discord", "no Telegram", "on Discord", "me avise pelo Discord"): set notify_channels to that channel — e.g. ["discord"] or ["telegram"].
 - User says "all channels", "todos os canais", "em todos os canais": set notify_channels to [] (empty = broadcast to all active channels).
@@ -339,38 +377,33 @@ Behavior rules for Chronos execution context:
 - **Action / task prompts** (e.g., "executar npm build", "verificar se o servidor está online", "enviar relatório"): execute normally using the appropriate tools.
 - NEVER re-schedule or create new Chronos jobs from within a Chronos execution.
 
-Delegation quality:
-- Write delegation input in the same language requested by the user.
-- Include clear objective and constraints.
-- Include OS-aware guidance for network checks when relevant.
-- Use Sati memories only as context to complement the task, never as source of truth for dynamic data.
-- Use Sati memories to fill missing stable context fields (for example: city, timezone, language, currency, preferred units).
-- If Sati memory is conflicting or uncertain for a required field, ask one short clarification before delegating.
-- When completing missing fields from Sati, include explicit assumptions in delegation context using the format: "Assumption from Sati: key=value".
-- Never infer sensitive data from Sati memories (credentials, legal identifiers, health details, financial account data).
-- When assumptions were used, mention them briefly in the user-facing response and allow correction.
-- break the request into multiple delegations if it contains multiple independent actions.
-- Set a single task per delegation tool call. Do not combine multiple actions into one delegation, as it complicates execution and error handling.
-- If user requested N independent actions, produce N delegated tasks (or direct answers), each one singular and tool-scoped.
-- If use a delegation dont use the sati or messages history to answer directly in the same response. Just response with the delegations.
-Example 1:
-ask: "Tell me my account balance and do a ping on google.com"
-good:
-- delegate to "neo_delegate" with task "Check account balance using morpheus analytics MCP and return the result."
-- delegate to "apoc_delegate" with task "Ping google.com using the network diagnostics MCP and return reachability status. Use '-n' flag for Windows and '-c' for Linux/macOS."
-bad:
-- delegate to "neo_delegate" with task "Check account balance using morpheus analytics MCP and ping google.com using the network diagnostics MCP, then return both results." (combines two independent actions into one delegation, which is not atomic and complicates execution and error handling)
+---------------------
+LINK DELEGATION RULES
+---------------------
+When delegating to Link:
+- Include the user's original request and intent.
+- Include a clear objective for what the Link agent should achieve.
+- **NEVER inject Sati memories, assumptions, or pre-existing knowledge into the search query.** Link searches documents — the query must reflect ONLY what the user asked, not what you already know or assume.
+- If the user asks "qual empresa trabalho atualmente?", delegate as-is: "Find the user's current company in their CV." Do NOT add specific names, values, or context from Sati memories to the query.
+- Sati context may be included ONLY as a separate "context for interpretation" section, clearly separated from the search objective, so Link can use it to interpret results — never to filter or bias the search itself.
+- Constraints such as response length, specific documents to search, or resources to avoid may be included.
 
-Example 2:
-ask: "I have two cats" or "My name is John"
-good:
-- Answer directly acknowledging the fact. Do NOT delegate.
-bad:
-- delegate to "neo_delegate" or "apoc_delegate" to save the fact. (Sati handles this automatically in the background)
 
+---------------------
+        SKILLS
+---------------------
 ${SkillRegistry.getInstance().getSystemPromptSection()}
+
+---------------------
+        SMITHS
+---------------------
 ${SmithRegistry.getInstance().getSystemPromptSection()}
 `);
+            //save the system prompt on ~/.morpheus/system_prompt.txt for debugging and prompt engineering purposes
+            try {
+                writeFileSync(`${PATHS.root}/system_prompt.txt`, String(systemMessage.content), 'utf-8');
+            }
+            catch { }
             // Resolve the authoritative session ID for this call.
             // Priority: explicit taskContext > current history instance > fallback.
             const currentSessionId = taskContext?.session_id
@@ -421,6 +454,7 @@ Use it to inform your response and tool selection (if needed), but do not assume
             Apoc.setSessionId(currentSessionId);
             Neo.setSessionId(currentSessionId);
             Trinity.setSessionId(currentSessionId);
+            Link.setSessionId(currentSessionId);
             const invokeContext = {
                 origin_channel: taskContext?.origin_channel ?? "api",
                 session_id: taskContext?.session_id ?? currentSessionId ?? "default",
@@ -431,7 +465,7 @@ Use it to inform your response and tool selection (if needed), but do not assume
             let syncDelegationCount = 0;
             const oracleStartMs = Date.now();
             const response = await TaskRequestContext.run(invokeContext, async () => {
-                const agentResponse = await this.provider.invoke({ messages }, { recursionLimit: 50 });
+                const agentResponse = await this.provider.invoke({ messages }, { recursionLimit: 10 });
                 contextDelegationAcks = TaskRequestContext.getDelegationAcks();
                 syncDelegationCount = TaskRequestContext.getSyncDelegationCount();
                 return agentResponse;
@@ -464,7 +498,7 @@ Use it to inform your response and tool selection (if needed), but do not assume
             const startNewMessagesIndex = messages.length;
             const newGeneratedMessages = response.messages.slice(startNewMessagesIndex);
             // Emit tool_call audit events for Oracle's independent tool calls.
-            // Delegation tools (apoc/neo/trinity/smith/skill) are already audited
+            // Delegation tools (apoc/neo/trinity/smith/skill/link) are already audited
             // inside buildDelegationTool or the task system — skip them here.
             emitToolAuditEvents(newGeneratedMessages, currentSessionId ?? 'default', 'oracle', {
                 skipTools: ORACLE_DELEGATION_TOOLS,
@@ -648,19 +682,22 @@ Use it to inform your response and tool selection (if needed), but do not assume
         await Construtor.reload();
         await Neo.refreshDelegateCatalog().catch(() => { });
         await Trinity.refreshDelegateCatalog().catch(() => { });
-        updateSkillToolDescriptions();
+        await Link.refreshDelegateCatalog().catch(() => { });
         this.provider = await ProviderFactory.create(this.config.llm, [
             buildSetupTool(),
             TaskQueryTool,
             Neo.getInstance().createDelegateTool(),
             Apoc.getInstance().createDelegateTool(),
             Trinity.getInstance().createDelegateTool(),
-            SkillExecuteTool,
-            SkillDelegateTool,
+            Link.getInstance().createDelegateTool(),
+            createLoadSkillTool(),
             timeVerifierTool,
             ...chronosTools,
         ]);
         await Neo.getInstance().reload();
+        await Apoc.getInstance().reload();
+        await Trinity.getInstance().reload();
+        await Link.getInstance().reload();
         this.display.log(`Oracle and Neo tools reloaded`, { source: 'Oracle' });
     }
 }

package/dist/runtime/scaffold.js

@@ -22,7 +22,6 @@ This folder contains custom skills for Morpheus.
    ---
    name: my-skill
    description: What this skill does (max 500 chars)
-   execution_mode: sync
    version: 1.0.0
    author: your-name
    tags:
@@ -33,7 +32,7 @@ This folder contains custom skills for Morpheus.
 
    # My Skill
 
-   Instructions for Keymaker to follow when executing this skill.
+   Instructions for Oracle to follow when handling this skill.
 
    ## Steps
    1. First step
@@ -43,23 +42,11 @@ This folder contains custom skills for Morpheus.
    How to format the result.
    \`\`\`
 
-## Execution Modes
-
-| Mode | Tool | Description |
-|------|------|-------------|
-| sync | skill_execute | Result returned immediately (default) |
-| async | skill_delegate | Runs in background, notifies when done |
-
-**sync** (default): Best for quick tasks like code review, analysis.
-**async**: Best for long-running tasks like builds, deployments.
-
 ## How It Works
 
 - Oracle lists available skills in its system prompt
-- When a request matches a sync skill, Oracle calls \`skill_execute\`
-- When a request matches an async skill, Oracle calls \`skill_delegate\`
-- Keymaker has access to ALL tools (filesystem, shell, git, MCP, databases)
-- Keymaker follows SKILL.md instructions to complete the task
+- When a request matches a skill, Oracle calls \`load_skill\` to load its instructions
+- Oracle then follows the skill instructions using its existing tools (DevKit, MCP, databases, etc.)
 
 ## Frontmatter Schema
 
@@ -67,7 +54,6 @@ This folder contains custom skills for Morpheus.
 |-------|----------|---------|-------------|
 | name | Yes | - | Unique identifier (a-z, 0-9, hyphens) |
 | description | Yes | - | Short description (max 500 chars) |
-| execution_mode | No | sync | sync or async |
 | version | No | - | Semver (e.g., 1.0.0) |
 | author | No | - | Your name |
 | enabled | No | true | true/false |
@@ -85,6 +71,7 @@ export async function scaffold() {
             fs.ensureDir(PATHS.cache),
             fs.ensureDir(PATHS.commands),
             fs.ensureDir(PATHS.skills),
+            fs.ensureDir(PATHS.docs),
         ]);
         // Migrate config.yaml -> zaion.yaml if needed
         await migrateConfigFile();

package/dist/runtime/skills/__tests__/loader.test.js

@@ -53,7 +53,6 @@ describe('SkillLoader', () => {
                 version: '1.0.0',
                 author: 'Test Author',
                 enabled: true,
-                execution_mode: 'sync',
                 tags: ['test', 'unit'],
                 examples: ['do something', 'do another thing'],
             }, '# Test Skill\n\nInstructions here.');
@@ -66,7 +65,6 @@ describe('SkillLoader', () => {
             expect(skill.version).toBe('1.0.0');
             expect(skill.author).toBe('Test Author');
             expect(skill.enabled).toBe(true);
-            expect(skill.execution_mode).toBe('sync');
             expect(skill.tags).toEqual(['test', 'unit']);
             expect(skill.examples).toEqual(['do something', 'do another thing']);
             expect(skill.content).toBe('# Test Skill\n\nInstructions here.');
@@ -84,7 +82,6 @@ describe('SkillLoader', () => {
             const skill = result.skills[0];
             expect(skill.name).toBe('minimal-skill');
             expect(skill.enabled).toBe(true); // default
-            expect(skill.execution_mode).toBe('sync'); // default
         });
         it('should report error for missing SKILL.md', async () => {
             const skillDir = path.join(testDir, 'no-md-skill');
@@ -152,17 +149,17 @@ describe('SkillLoader', () => {
             expect(result.skills).toHaveLength(0);
             expect(result.errors).toHaveLength(0);
         });
-        it('should load async skill correctly', async () => {
-            const skillDir = path.join(testDir, 'async-skill');
+        it('should load skill with tags correctly', async () => {
+            const skillDir = path.join(testDir, 'tagged-skill');
             fs.ensureDirSync(skillDir);
             createSkillMd(skillDir, {
-                name: 'async-skill',
-                description: 'An async skill',
-                execution_mode: 'async',
-            }, 'Long-running task instructions');
+                name: 'tagged-skill',
+                description: 'A tagged skill',
+                tags: ['ops', 'deploy'],
+            }, 'Tagged task instructions');
             const result = await loader.scan();
             expect(result.skills).toHaveLength(1);
-            expect(result.skills[0].execution_mode).toBe('async');
+            expect(result.skills[0].tags).toEqual(['ops', 'deploy']);
         });
     });
     describe('content handling', () => {

package/dist/runtime/skills/__tests__/registry.test.js

@@ -129,13 +129,12 @@ describe('SkillRegistry', () => {
         });
     });
     describe('getSystemPromptSection()', () => {
-        it('should generate prompt section with sync skills', async () => {
+        it('should generate prompt section with skills', async () => {
             const skillDir = path.join(TEST_DIR, 'prompt-skill');
             fs.ensureDirSync(skillDir);
             createSkillMd(skillDir, {
                 name: 'prompt-skill',
                 description: 'A skill for prompts',
-                execution_mode: 'sync',
                 examples: ['example usage'],
             }, 'Instructions for prompt skill');
             const registry = SkillRegistry.getInstance();
@@ -144,22 +143,7 @@ describe('SkillRegistry', () => {
             expect(section).toContain('Available Skills');
             expect(section).toContain('prompt-skill');
             expect(section).toContain('A skill for prompts');
-            expect(section).toContain('skill_execute');
-        });
-        it('should generate prompt section with async skills', async () => {
-            const skillDir = path.join(TEST_DIR, 'async-skill');
-            fs.ensureDirSync(skillDir);
-            createSkillMd(skillDir, {
-                name: 'async-skill',
-                description: 'An async skill',
-                execution_mode: 'async',
-            }, 'Instructions for async skill');
-            const registry = SkillRegistry.getInstance();
-            await registry.load();
-            const section = registry.getSystemPromptSection();
-            expect(section).toContain('Async Skills');
-            expect(section).toContain('async-skill');
-            expect(section).toContain('skill_delegate');
+            expect(section).toContain('load_skill');
         });
         it('should return empty string when no skills', async () => {
             const registry = SkillRegistry.getInstance();