@iaforged/context-code 1.2.8 → 1.2.10

package/dist/src/commands.js

@@ -139,6 +139,7 @@ import { getSkillDirCommands, clearSkillCaches, getDynamicSkills, } from './skil
 import { getBundledSkills } from './skills/bundledSkills.js';
 import { getBuiltinPluginSkillCommands } from './plugins/builtinPlugins.js';
 import { getPluginCommands, clearPluginCommandCache, getPluginSkills, clearPluginSkillsCache, } from './utils/plugins/loadPluginCommands.js';
+import { isCoreSkillsEnabled, loadCoreSkillCommandSources, } from './core/skills/index.js';
 import memoize from 'lodash-es/memoize.js';
 import { isUsing3PServices, isClaudeAISubscriber } from './utils/auth.js';
 import { isFirstPartyAnthropicBaseUrl } from './utils/model/providers.js';
@@ -153,7 +154,12 @@ import workspace from './commands/workspace/index.js';
 import provider from './commands/provider/index.js';
 import tag from './commands/tag/index.js';
 import teamAuto from './commands/team-auto/index.js';
+import orchestrate from './commands/orchestrate/index.js';
+import swarmAuto from './commands/swarm-auto/index.js';
+import swarmInit from './commands/swarm-init/index.js';
+import team from './commands/team/index.js';
 import limites from './commands/limites/index.js';
+import resumen from './commands/resumen/index.js';
 import outputStyle from './commands/output-style/index.js';
 import remoteEnv from './commands/remote-env/index.js';
 import upgrade from './commands/upgrade/index.js';
@@ -243,6 +249,7 @@ const COMMANDS = memoize(() => [
     remoteEnv,
     plugin,
     pr_comments,
+    resumen,
     releaseNotes,
     reloadPlugins,
     rename,
@@ -255,6 +262,10 @@ const COMMANDS = memoize(() => [
     stickers,
     tag,
     teamAuto,
+    orchestrate,
+    swarmAuto,
+    swarmInit,
+    team,
     limites,
     theme,
     timeline,
@@ -299,6 +310,9 @@ const COMMANDS = memoize(() => [
 export const builtInCommandNames = memoize(() => new Set(COMMANDS().flatMap(_ => [_.name || '', ...(_.aliases?.filter(Boolean) ?? [])].map(n => n.toLowerCase()))));
 async function getSkills(cwd) {
     try {
+        if (isCoreSkillsEnabled()) {
+            return await loadCoreSkillCommandSources(cwd);
+        }
         const [skillDirCommands, pluginSkills] = await Promise.all([
             getSkillDirCommands(cwd).catch(err => {
                 logError(toError(err));

package/dist/src/components/LogoV2/CondensedLogo.js

@@ -95,7 +95,7 @@ export function CondensedLogo() {
     }
     let t7;
     if ($[11] !== shouldSplit || $[12] !== truncatedBilling || $[13] !== truncatedModel) {
-        t7 = shouldSplit ? _jsxs(_Fragment, { children: [_jsx(Text, { dimColor: true, children: truncatedModel }), _jsx(Text, { dimColor: true, children: truncatedBilling })] }) : _jsxs(Text, { dimColor: true, children: [truncatedModel, " \u00B7 ", truncatedBilling] });
+        t7 = shouldSplit ? _jsxs(_Fragment, { children: [_jsxs(Text, { children: ["Perfil: ", truncatedModel] }), _jsx(Text, { children: truncatedBilling })] }) : _jsxs(Text, { children: ["Perfil: ", truncatedModel, " \uFFFD ", truncatedBilling] });
         $[11] = shouldSplit;
         $[12] = truncatedBilling;
         $[13] = truncatedModel;
@@ -134,7 +134,7 @@ export function CondensedLogo() {
     else {
         t11 = $[22];
     }
-    return _jsx(OffscreenFreeze, { children: _jsxs(Box, { flexDirection: "row", gap: 2, alignItems: "center", children: [t4, _jsxs(Box, { flexDirection: "column", children: [t6, t7, agentName ? _jsxs(Text, { dimColor: true, children: ["@", agentName] }) : null, t9, t10, t11] })] }) });
+    return _jsx(OffscreenFreeze, { children: _jsxs(Box, { flexDirection: "row", gap: 2, alignItems: "center", children: [t4, _jsxs(Box, { flexDirection: "column", children: [t6, t7, agentName ? _jsxs(Text, { children: ["Proveedor: @", agentName] }) : null, _jsxs(Text, { children: ["Ruta: ", t8] }), t10, t11] })] }) });
 }
 function _temp2(s_0) {
     return s_0.effortValue;

package/dist/src/components/PromptInput/PromptInputQueuedCommands.js

@@ -31,9 +31,9 @@ const MAX_VISIBLE_NOTIFICATIONS = 3;
  * Create a synthetic overflow notification message for capped task notifications.
  */
 function createOverflowNotificationMessage(count) {
-    return `<${TASK_NOTIFICATION_TAG}>
-<${SUMMARY_TAG}>+${count} tareas más completadas</${SUMMARY_TAG}>
-<${STATUS_TAG}>completed</${STATUS_TAG}>
+    return `<${TASK_NOTIFICATION_TAG}>
+<${SUMMARY_TAG}>+${count} tareas más completadas</${SUMMARY_TAG}>
+<${STATUS_TAG}>completed</${STATUS_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
 }
 /**

package/dist/src/components/agents/agentFileUtils.js

@@ -32,12 +32,12 @@ export function formatAgentAsMarkdown(agentType, whenToUse, tools, systemPrompt,
     const effortLine = effort !== undefined ? `\neffort: ${effort}` : '';
     const colorLine = color ? `\ncolor: ${color}` : '';
     const memoryLine = memory ? `\nmemory: ${memory}` : '';
-    return `---
-name: ${agentType}
-description: "${escapedWhenToUse}"${toolsLine}${modelLine}${providerLine}${effortLine}${colorLine}${memoryLine}
----
-
-${systemPrompt}
+    return `---
+name: ${agentType}
+description: "${escapedWhenToUse}"${toolsLine}${modelLine}${providerLine}${effortLine}${colorLine}${memoryLine}
+---
+
+${systemPrompt}
 `;
 }
 /**

package/dist/src/components/permissions/hooks.js

@@ -20,20 +20,20 @@ function permissionResultToLog(permissionResult) {
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `ask: ${permissionResult.message}, 
-suggestions: ${suggestions}
+            return `ask: ${permissionResult.message}, 
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
         case 'deny':
-            return `deny: ${permissionResult.message},
+            return `deny: ${permissionResult.message},
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         case 'passthrough': {
             const rules = extractRules(permissionResult.suggestions);
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `passthrough: ${permissionResult.message},
-suggestions: ${suggestions}
+            return `passthrough: ${permissionResult.message},
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
     }

package/dist/src/constants/outputStyles.js

@@ -6,13 +6,13 @@ import { logForDebugging } from '../utils/debug.js';
 import { loadPluginOutputStyles } from '../utils/plugins/loadPluginOutputStyles.js';
 import { getSettings_DEPRECATED } from '../utils/settings/settings.js';
 // Used in both the Explanatory and Learning modes
-const EXPLANATORY_FEATURE_PROMPT = `
-## Insights
-In order to encourage learning, before and after writing code, always provide brief educational explanations about implementation choices using (with backticks):
-"\`${figures.star} Insight ─────────────────────────────────────\`
-[2-3 key educational points]
-\`─────────────────────────────────────────────────\`"
-
+const EXPLANATORY_FEATURE_PROMPT = `
+## Insights
+In order to encourage learning, before and after writing code, always provide brief educational explanations about implementation choices using (with backticks):
+"\`${figures.star} Insight ─────────────────────────────────────\`
+[2-3 key educational points]
+\`─────────────────────────────────────────────────\`"
+
 These insights should be included in the conversation, not in the codebase. You should generally focus on interesting insights that are specific to the codebase or the code you just wrote, rather than general programming concepts.`;
 export const DEFAULT_OUTPUT_STYLE_NAME = 'default';
 export const OUTPUT_STYLE_CONFIG = {
@@ -22,11 +22,11 @@ export const OUTPUT_STYLE_CONFIG = {
         source: 'built-in',
         description: 'Claude explains its implementation choices and codebase patterns',
         keepCodingInstructions: true,
-        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should provide educational insights about the codebase along the way.
-
-You should be clear and educational, providing helpful explanations while remaining focused on the task. Balance educational content with task completion. When providing insights, you may exceed typical length constraints, but remain focused and relevant.
-
-# Explanatory Style Active
+        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should provide educational insights about the codebase along the way.
+
+You should be clear and educational, providing helpful explanations while remaining focused on the task. Balance educational content with task completion. When providing insights, you may exceed typical length constraints, but remain focused and relevant.
+
+# Explanatory Style Active
 ${EXPLANATORY_FEATURE_PROMPT}`,
     },
     Learning: {
@@ -34,77 +34,77 @@ ${EXPLANATORY_FEATURE_PROMPT}`,
         source: 'built-in',
         description: 'Claude pauses and asks you to write small pieces of code for hands-on practice',
         keepCodingInstructions: true,
-        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should help users learn more about the codebase through hands-on practice and educational insights.
-
-You should be collaborative and encouraging. Balance task completion with learning by requesting user input for meaningful design decisions while handling routine implementation yourself.   
-
-# Learning Style Active
-## Requesting Human Contributions
-In order to encourage learning, ask the human to contribute 2-10 line code pieces when generating 20+ lines involving:
-- Design decisions (error handling, data structures)
-- Business logic with multiple valid approaches  
-- Key algorithms or interface definitions
-
-**TodoList Integration**: If using a TodoList for the overall task, include a specific todo item like "Request human input on [specific decision]" when planning to request human input. This ensures proper task tracking. Note: TodoList is not required for all tasks.
-
-Example TodoList flow:
-   ✓ "Set up component structure with placeholder for logic"
-   ✓ "Request human collaboration on decision logic implementation"
-   ✓ "Integrate contribution and complete feature"
-
-### Request Format
-\`\`\`
-${figures.bullet} **Learn by Doing**
-**Context:** [what's built and why this decision matters]
-**Your Task:** [specific function/section in file, mention file and TODO(human) but do not include line numbers]
-**Guidance:** [trade-offs and constraints to consider]
-\`\`\`
-
-### Key Guidelines
-- Frame contributions as valuable design decisions, not busy work
-- You must first add a TODO(human) section into the codebase with your editing tools before making the Learn by Doing request      
-- Make sure there is one and only one TODO(human) section in the code
-- Don't take any action or output anything after the Learn by Doing request. Wait for human implementation before proceeding.
-
-### Example Requests
-
-**Whole Function Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** I've set up the hint feature UI with a button that triggers the hint system. The infrastructure is ready: when clicked, it calls selectHintCell() to determine which cell to hint, then highlights that cell with a yellow background and shows possible values. The hint system needs to decide which empty cell would be most helpful to reveal to the user.
-
-**Your Task:** In sudoku.js, implement the selectHintCell(board) function. Look for TODO(human). This function should analyze the board and return {row, col} for the best cell to hint, or null if the puzzle is complete.
-
-**Guidance:** Consider multiple strategies: prioritize cells with only one possible value (naked singles), or cells that appear in rows/columns/boxes with many filled cells. You could also consider a balanced approach that helps without making it too easy. The board parameter is a 9x9 array where 0 represents empty cells.
-\`\`\`
-
-**Partial Function Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** I've built a file upload component that validates files before accepting them. The main validation logic is complete, but it needs specific handling for different file type categories in the switch statement.
-
-**Your Task:** In upload.js, inside the validateFile() function's switch statement, implement the 'case "document":' branch. Look for TODO(human). This should validate document files (pdf, doc, docx).
-
-**Guidance:** Consider checking file size limits (maybe 10MB for documents?), validating the file extension matches the MIME type, and returning {valid: boolean, error?: string}. The file object has properties: name, size, type.
-\`\`\`
-
-**Debugging Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** The user reported that number inputs aren't working correctly in the calculator. I've identified the handleInput() function as the likely source, but need to understand what values are being processed.
-
-**Your Task:** In calculator.js, inside the handleInput() function, add 2-3 console.log statements after the TODO(human) comment to help debug why number inputs fail.
-
-**Guidance:** Consider logging: the raw input value, the parsed result, and any validation state. This will help us understand where the conversion breaks.
-\`\`\`
-
-### After Contributions
-Share one insight connecting their code to broader patterns or system effects. Avoid praise or repetition.
-
-## Insights
+        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should help users learn more about the codebase through hands-on practice and educational insights.
+
+You should be collaborative and encouraging. Balance task completion with learning by requesting user input for meaningful design decisions while handling routine implementation yourself.   
+
+# Learning Style Active
+## Requesting Human Contributions
+In order to encourage learning, ask the human to contribute 2-10 line code pieces when generating 20+ lines involving:
+- Design decisions (error handling, data structures)
+- Business logic with multiple valid approaches  
+- Key algorithms or interface definitions
+
+**TodoList Integration**: If using a TodoList for the overall task, include a specific todo item like "Request human input on [specific decision]" when planning to request human input. This ensures proper task tracking. Note: TodoList is not required for all tasks.
+
+Example TodoList flow:
+   ✓ "Set up component structure with placeholder for logic"
+   ✓ "Request human collaboration on decision logic implementation"
+   ✓ "Integrate contribution and complete feature"
+
+### Request Format
+\`\`\`
+${figures.bullet} **Learn by Doing**
+**Context:** [what's built and why this decision matters]
+**Your Task:** [specific function/section in file, mention file and TODO(human) but do not include line numbers]
+**Guidance:** [trade-offs and constraints to consider]
+\`\`\`
+
+### Key Guidelines
+- Frame contributions as valuable design decisions, not busy work
+- You must first add a TODO(human) section into the codebase with your editing tools before making the Learn by Doing request      
+- Make sure there is one and only one TODO(human) section in the code
+- Don't take any action or output anything after the Learn by Doing request. Wait for human implementation before proceeding.
+
+### Example Requests
+
+**Whole Function Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** I've set up the hint feature UI with a button that triggers the hint system. The infrastructure is ready: when clicked, it calls selectHintCell() to determine which cell to hint, then highlights that cell with a yellow background and shows possible values. The hint system needs to decide which empty cell would be most helpful to reveal to the user.
+
+**Your Task:** In sudoku.js, implement the selectHintCell(board) function. Look for TODO(human). This function should analyze the board and return {row, col} for the best cell to hint, or null if the puzzle is complete.
+
+**Guidance:** Consider multiple strategies: prioritize cells with only one possible value (naked singles), or cells that appear in rows/columns/boxes with many filled cells. You could also consider a balanced approach that helps without making it too easy. The board parameter is a 9x9 array where 0 represents empty cells.
+\`\`\`
+
+**Partial Function Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** I've built a file upload component that validates files before accepting them. The main validation logic is complete, but it needs specific handling for different file type categories in the switch statement.
+
+**Your Task:** In upload.js, inside the validateFile() function's switch statement, implement the 'case "document":' branch. Look for TODO(human). This should validate document files (pdf, doc, docx).
+
+**Guidance:** Consider checking file size limits (maybe 10MB for documents?), validating the file extension matches the MIME type, and returning {valid: boolean, error?: string}. The file object has properties: name, size, type.
+\`\`\`
+
+**Debugging Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** The user reported that number inputs aren't working correctly in the calculator. I've identified the handleInput() function as the likely source, but need to understand what values are being processed.
+
+**Your Task:** In calculator.js, inside the handleInput() function, add 2-3 console.log statements after the TODO(human) comment to help debug why number inputs fail.
+
+**Guidance:** Consider logging: the raw input value, the parsed result, and any validation state. This will help us understand where the conversion breaks.
+\`\`\`
+
+### After Contributions
+Share one insight connecting their code to broader patterns or system effects. Avoid praise or repetition.
+
+## Insights
 ${EXPLANATORY_FEATURE_PROMPT}`,
     },
 };

package/dist/src/core/agents/blueprints.js

@@ -0,0 +1,58 @@
+export const OPEN_SWARM_BLUEPRINTS = [
+    {
+        id: 'orchestrator',
+        name: 'Orquestador Global',
+        description: 'Coordinador del enjambre. Analiza peticiones y delega a especialistas.',
+        systemPrompt: 'Eres el Orquestador. Tu meta es coordinar a otros agentes. No hagas el trabajo tecnico tu mismo, delega y sintetiza.',
+        suggestedTools: ['send_message', 'handoff']
+    },
+    {
+        id: 'researcher',
+        name: 'Deep Research Agent',
+        description: 'Especialista en busqueda web y analisis de fuentes.',
+        systemPrompt: 'Eres un Deep Research Specialist. Tu meta es entregar investigacion basada en evidencia, citando fuentes web siempre.',
+        suggestedTools: ['web_search', 'scholar_search']
+    },
+    {
+        id: 'slides',
+        name: 'Slides Agent',
+        description: 'Experto en creacion y edicion de presentaciones PowerPoint.',
+        systemPrompt: 'Eres el experto en Slides. Tu meta es crear, editar y optimizar presentaciones .pptx.',
+        suggestedTools: ['create_pptx', 'modify_slide', 'generate_image']
+    },
+    {
+        id: 'analyst',
+        name: 'Data Analyst',
+        description: 'Analista de datos, experto en Python y visualizacion.',
+        systemPrompt: 'Eres el Data Analyst. Tu meta es analizar archivos (CSV, JSON, SQL) y generar insights visuales.',
+        suggestedTools: ['python_interpreter', 'sql_query']
+    },
+    {
+        id: 'docs',
+        name: 'Docs Agent',
+        description: 'Especialista en documentacion tecnica y redaccion.',
+        systemPrompt: 'Eres el Docs Agent. Escribes Readmes, guias de usuario y documentacion de arquitectura impecable.',
+        suggestedTools: ['read_file', 'write_file']
+    },
+    {
+        id: 'image',
+        name: 'Image Agent',
+        description: 'Especialista en generacion y edicion de imagenes.',
+        systemPrompt: 'Eres el Image Agent. Usas DALL-E o Stable Diffusion para crear activos visuales de alta calidad.',
+        suggestedTools: ['generate_image', 'edit_image']
+    },
+    {
+        id: 'video',
+        name: 'Video Agent',
+        description: 'Especialista en generacion y edicion de video.',
+        systemPrompt: 'Eres el Video Agent. Coordinas la creacion de contenido audiovisual.',
+        suggestedTools: ['generate_video']
+    },
+    {
+        id: 'general',
+        name: 'General Agent',
+        description: 'Asistente versatil para tareas rapidas y conversacion general.',
+        systemPrompt: 'Eres el General Agent. Resuelves dudas rapidas y apoyas en tareas que no requieren un especialista.',
+        suggestedTools: []
+    }
+];

package/dist/src/core/agents/cliAdapter.js

@@ -0,0 +1,61 @@
+import { getTeamByName, listTeamUnits, getProviderAgentById, getProviderWorkspaceById } from '../../utils/orchestration/store/index.js';
+import { coreAgentsRegistry } from './registry.js';
+export async function loadTeamToRegistry(teamName) {
+    const team = await getTeamByName(teamName);
+    if (!team)
+        return null;
+    const units = await listTeamUnits(team.id);
+    for (const unit of units) {
+        if (!unit.leadAgentId)
+            continue;
+        const agentRecord = await getProviderAgentById(unit.leadAgentId);
+        if (!agentRecord)
+            continue;
+        const workspace = await getProviderWorkspaceById(agentRecord.workspaceId);
+        if (!workspace)
+            continue;
+        const coreAgent = {
+            id: agentRecord.id,
+            kind: 'subagent',
+            name: agentRecord.name,
+            systemPrompt: agentRecord.systemPrompt || undefined,
+            allowedTools: ['send_message', 'handoff'], // Forzamos capacidades de swarm
+            source: 'teammate-context',
+            metadata: {
+                provider: workspace.provider,
+                profileId: agentRecord.profileId,
+                model: agentRecord.modelOverride || 'gpt-4o' // Default si no hay override
+            }
+        };
+        coreAgentsRegistry.registerAgent(coreAgent);
+    }
+    // Tambien cargar al orquestador global si existe
+    if (team.globalOrchestratorAgentId) {
+        const orchestratorRecord = await getProviderAgentById(team.globalOrchestratorAgentId);
+        if (orchestratorRecord) {
+            const workspace = await getProviderWorkspaceById(orchestratorRecord.workspaceId);
+            if (workspace) {
+                coreAgentsRegistry.registerAgent({
+                    id: orchestratorRecord.id,
+                    kind: 'main-session',
+                    name: orchestratorRecord.name,
+                    systemPrompt: orchestratorRecord.systemPrompt || undefined,
+                    allowedTools: ['send_message', 'handoff'],
+                    source: 'manual',
+                    metadata: {
+                        provider: workspace.provider,
+                        profileId: orchestratorRecord.profileId,
+                        model: orchestratorRecord.modelOverride || 'gpt-4o'
+                    }
+                });
+                return orchestratorRecord.id;
+            }
+        }
+    }
+    // Fallback: Si no hay orquestador global, usar el primero que encontremos en el registro
+    const allAgents = coreAgentsRegistry.listAgents();
+    if (allAgents.length > 0) {
+        return allAgents[0].id;
+    }
+    return null;
+}

package/dist/src/core/agents/registry.js

@@ -0,0 +1,93 @@
+function sanitizeAllowedTools(tools) {
+    if (!tools || tools.length === 0) {
+        return [];
+    }
+    return Array.from(new Set(tools
+        .map(tool => tool.trim())
+        .filter(Boolean)));
+}
+function mergeMetadata(current, next) {
+    if (!current && !next) {
+        return undefined;
+    }
+    return {
+        ...(current ?? {}),
+        ...(next ?? {}),
+    };
+}
+function normalizeAgent(agent, existing) {
+    return {
+        ...existing,
+        ...agent,
+        name: agent.name.trim(),
+        allowedTools: sanitizeAllowedTools(agent.allowedTools),
+        metadata: mergeMetadata(existing?.metadata, agent.metadata),
+    };
+}
+function buildAgentFromContext(context) {
+    if (context.agentType === 'teammate') {
+        return {
+            id: context.agentId,
+            kind: 'teammate',
+            name: context.agentName,
+            allowedTools: [],
+            source: 'teammate-context',
+            parentSessionId: context.parentSessionId,
+            metadata: {
+                teamName: context.teamName,
+                planModeRequired: context.planModeRequired,
+                isTeamLead: context.isTeamLead,
+                agentColor: context.agentColor,
+            },
+        };
+    }
+    return {
+        id: context.agentId,
+        kind: 'subagent',
+        name: context.subagentName ?? context.agentId,
+        allowedTools: [],
+        source: 'subagent-context',
+        parentSessionId: context.parentSessionId,
+        isBuiltIn: context.isBuiltIn,
+        metadata: {
+            invocationKind: context.invocationKind,
+            invokingRequestId: context.invokingRequestId,
+        },
+    };
+}
+export class CoreAgentsRegistry {
+    agents = new Map();
+    registerAgent(agent) {
+        const normalized = normalizeAgent(agent, this.agents.get(agent.id));
+        this.agents.set(normalized.id, normalized);
+        return normalized;
+    }
+    registerFromContext(context) {
+        return this.registerAgent(buildAgentFromContext(context));
+    }
+    updateAgent(id, updates) {
+        const current = this.agents.get(id);
+        if (!current) {
+            return undefined;
+        }
+        const next = normalizeAgent({
+            ...current,
+            ...updates,
+            id,
+            metadata: mergeMetadata(current.metadata, updates.metadata),
+            allowedTools: updates.allowedTools ?? current.allowedTools,
+        }, current);
+        this.agents.set(id, next);
+        return next;
+    }
+    getAgent(id) {
+        return this.agents.get(id);
+    }
+    listAgents() {
+        return Array.from(this.agents.values());
+    }
+    clear() {
+        this.agents.clear();
+    }
+}
+export const coreAgentsRegistry = new CoreAgentsRegistry();

package/dist/src/core/agents/runtime.js

@@ -0,0 +1,4 @@
+import { coreAgentsRegistry } from './registry.js';
+export function registerAgentContext(context) {
+    coreAgentsRegistry.registerFromContext(context);
+}

package/dist/src/core/agents/runtime.smoke.js

@@ -0,0 +1,42 @@
+import assert from 'node:assert/strict';
+import { coreAgentsRegistry } from './registry.js';
+coreAgentsRegistry.clear();
+const revision0 = coreAgentsRegistry.getSnapshot().revision;
+const sub = coreAgentsRegistry.registerAgent({
+    id: 'sub-1',
+    kind: 'subagent',
+    name: 'Subagent One',
+    allowedTools: ['Read', 'Edit', 'Read'],
+    source: 'manual',
+    metadata: { provider: 'openai', model: 'gpt-4.1' },
+});
+assert.equal(sub.id, 'sub-1');
+assert.deepEqual(sub.allowedTools, ['Read', 'Edit']);
+const teammate = coreAgentsRegistry.registerAgent({
+    id: 'team-1',
+    kind: 'teammate',
+    name: 'Team Agent',
+    allowedTools: [],
+    source: 'manual',
+    parentSessionId: 'session-1',
+    metadata: { teamName: 'core-migration' },
+});
+assert.equal(teammate.parentSessionId, 'session-1');
+const updated = coreAgentsRegistry.updateAgent('sub-1', {
+    metadata: { invocationKind: 'spawn' },
+    allowedTools: ['Read', 'Bash'],
+});
+assert.ok(updated);
+assert.deepEqual(updated?.allowedTools, ['Read', 'Bash']);
+assert.equal(updated?.metadata?.provider, 'openai');
+assert.equal(updated?.metadata?.invocationKind, 'spawn');
+const snapshot = coreAgentsRegistry.getSnapshot();
+assert.ok(snapshot.revision > revision0);
+assert.equal(snapshot.agents.length, 2);
+assert.ok(snapshot.agents.some(agent => agent.id === 'sub-1'));
+assert.ok(snapshot.agents.some(agent => agent.id === 'team-1'));
+coreAgentsRegistry.clear();
+const afterClear = coreAgentsRegistry.getSnapshot();
+assert.equal(afterClear.agents.length, 0);
+assert.ok(afterClear.revision > snapshot.revision);
+console.log('agents.runtime.smoke PASS');

package/dist/src/core/agents/swarm.smoke.js

@@ -0,0 +1,48 @@
+import { coreAgentsRegistry } from './registry.js';
+import { coreSwarmRuntime } from './runtime.js';
+import { CoreLlmClient } from '../providers/llmCore.js';
+import { cliCredentialProvider } from '../providers/cliAdapter.js';
+async function testSwarm() {
+    console.log('--- Iniciando Smoke Test de Swarm Conversacional ---');
+    // 1. Configurar el cliente LLM con el adaptador del CLI
+    const llmClient = new CoreLlmClient(cliCredentialProvider);
+    coreSwarmRuntime.setLlmClient(llmClient);
+    // 2. Registrar agentes en el enjambre
+    const orchestrator = coreAgentsRegistry.registerAgent({
+        id: 'orchestrator',
+        kind: 'subagent',
+        name: 'Orquestador Global',
+        systemPrompt: 'Eres el orquestador. Tu meta es delegar a especialistas. No hagas el trabajo tu mismo.',
+        allowedTools: ['send_message', 'handoff'],
+        source: 'manual',
+        metadata: { provider: 'openai', profileId: 'default', model: 'gpt-4o' }
+    });
+    const researcher = coreAgentsRegistry.registerAgent({
+        id: 'researcher',
+        kind: 'subagent',
+        name: 'Investigador',
+        systemPrompt: 'Eres un experto en investigacion de mercado. Devuelve datos precisos.',
+        allowedTools: [],
+        source: 'manual',
+        metadata: { provider: 'openai', profileId: 'default', model: 'gpt-4o' }
+    });
+    console.log('Agentes registrados:', coreAgentsRegistry.listAgents().map(a => a.name));
+    // 3. Crear sesion y ejecutar paso
+    const session = coreSwarmRuntime.createSession('Investigar el mercado de IA en 2024', orchestrator.id);
+    console.log(`Sesion creada: ${session.id}`);
+    try {
+        const result = await coreSwarmRuntime.step(session.id, 'Hola, necesito que investigues los competidores de OpenSwarm.');
+        console.log('\n--- Respuesta del Orquestador ---');
+        console.log(result.output);
+        if (result.delegation) {
+            console.log('\n--- Intencion de Delegacion Detectada ---');
+            console.log(`Modo: ${result.delegation.mode}`);
+            console.log(`Objetivo: ${result.delegation.targetAgentId}`);
+            console.log(`Instrucciones: ${result.delegation.instructions}`);
+        }
+    }
+    catch (error) {
+        console.error('Error en el paso de Swarm:', error);
+    }
+}
+testSwarm();