claude-flow 3.7.0-alpha.21 → 3.7.0-alpha.22

package/v3/@claude-flow/cli/dist/src/mcp-tools/transfer-tools.js

@@ -29,7 +29,7 @@ export const transferTools = [
     // ═══════════════════════════════════════════════════════════════
     {
         name: 'transfer_detect-pii',
-        description: 'Detect PII in content without redacting',
+        description: 'Detect PII in content without redacting Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -63,7 +63,7 @@ export const transferTools = [
     // ═══════════════════════════════════════════════════════════════
     {
         name: 'transfer_ipfs-resolve',
-        description: 'Resolve IPNS name to CID',
+        description: 'Resolve IPNS name to CID Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -97,7 +97,7 @@ export const transferTools = [
     // ═══════════════════════════════════════════════════════════════
     {
         name: 'transfer_store-search',
-        description: 'Search the pattern store',
+        description: 'Search the pattern store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -150,7 +150,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_store-info',
-        description: 'Get detailed info about a pattern',
+        description: 'Get detailed info about a pattern Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -186,7 +186,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_store-download',
-        description: 'Download a pattern from the store',
+        description: 'Download a pattern from the store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -223,7 +223,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_store-featured',
-        description: 'Get featured patterns from the store',
+        description: 'Get featured patterns from the store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -251,7 +251,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_store-trending',
-        description: 'Get trending patterns from the store',
+        description: 'Get trending patterns from the store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -282,7 +282,7 @@ export const transferTools = [
     // ═══════════════════════════════════════════════════════════════
     {
         name: 'transfer_plugin-search',
-        description: 'Search the plugin store',
+        description: 'Search the plugin store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -348,7 +348,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_plugin-info',
-        description: 'Get detailed info about a plugin',
+        description: 'Get detailed info about a plugin Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -388,7 +388,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_plugin-featured',
-        description: 'Get featured plugins from the store',
+        description: 'Get featured plugins from the store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {
@@ -419,7 +419,7 @@ export const transferTools = [
     },
     {
         name: 'transfer_plugin-official',
-        description: 'Get official plugins from the store',
+        description: 'Get official plugins from the store Use when native package install (`npm i`, `pip install`) is wrong because the artifact lives on IPFS (plugins, witness chains, learned patterns). For npm-registry deps, native npm is fine.',
         category: 'transfer',
         version: '1.0.0',
         inputSchema: {

package/v3/@claude-flow/cli/dist/src/mcp-tools/wasm-agent-tools.js

@@ -12,7 +12,7 @@ async function loadAgentWasm() {
 export const wasmAgentTools = [
     {
         name: 'wasm_agent_create',
-        description: 'Create a sandboxed WASM agent with virtual filesystem (no OS access). Optionally use a gallery template.',
+        description: 'Create a sandboxed WASM agent with virtual filesystem (no OS access). Optionally use a gallery template. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -58,7 +58,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_prompt',
-        description: 'Send a prompt to a WASM agent and get a response.',
+        description: 'Send a prompt to a WASM agent and get a response. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -90,7 +90,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_tool',
-        description: 'Execute a tool on a WASM agent sandbox. Tools: read_file, write_file, edit_file, write_todos, list_files. Use flat format: {tool, path, content, ...}.',
+        description: 'Execute a tool on a WASM agent sandbox. Tools: read_file, write_file, edit_file, write_todos, list_files. Use flat format: {tool, path, content, ...}. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -128,7 +128,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_list',
-        description: 'List all active WASM agents.',
+        description: 'List all active WASM agents. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: { type: 'object', properties: {} },
         handler: async () => {
             try {
@@ -143,7 +143,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_terminate',
-        description: 'Terminate a WASM agent and free resources.',
+        description: 'Terminate a WASM agent and free resources. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -169,7 +169,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_files',
-        description: 'Get a WASM agent\'s available tools and info.',
+        description: 'Get a WASM agent\'s available tools and info. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -196,7 +196,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_agent_export',
-        description: 'Export a WASM agent\'s full state (config, filesystem, conversation) as JSON.',
+        description: 'Export a WASM agent\'s full state (config, filesystem, conversation) as JSON. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -222,7 +222,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_gallery_list',
-        description: 'List all available WASM agent gallery templates (Coder, Researcher, Tester, Reviewer, Security, Swarm).',
+        description: 'List all available WASM agent gallery templates (Coder, Researcher, Tester, Reviewer, Security, Swarm). Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: { type: 'object', properties: {} },
         handler: async () => {
             try {
@@ -237,7 +237,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_gallery_search',
-        description: 'Search WASM agent gallery templates by query.',
+        description: 'Search WASM agent gallery templates by query. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {
@@ -263,7 +263,7 @@ export const wasmAgentTools = [
     },
     {
         name: 'wasm_gallery_create',
-        description: 'Create a WASM agent from a gallery template.',
+        description: 'Create a WASM agent from a gallery template. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine.',
         inputSchema: {
             type: 'object',
             properties: {

package/v3/@claude-flow/cli/dist/src/mcp-tools/workflow-tools.js

@@ -44,7 +44,7 @@ function saveWorkflowStore(store) {
 export const workflowTools = [
     {
         name: 'workflow_run',
-        description: 'Run a workflow from a template or file',
+        description: 'Run a workflow from a template or file Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -151,7 +151,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_create',
-        description: 'Create a new workflow',
+        description: 'Create a new workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -216,7 +216,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_execute',
-        description: 'Execute a workflow',
+        description: 'Execute a workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -403,7 +403,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_status',
-        description: 'Get workflow status',
+        description: 'Get workflow status Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -459,7 +459,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_list',
-        description: 'List all workflows',
+        description: 'List all workflows Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -502,7 +502,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_pause',
-        description: 'Pause a running workflow',
+        description: 'Pause a running workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -537,7 +537,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_resume',
-        description: 'Resume a paused workflow',
+        description: 'Resume a paused workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -582,7 +582,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_cancel',
-        description: 'Cancel a workflow',
+        description: 'Cancel a workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -630,7 +630,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_delete',
-        description: 'Delete a workflow',
+        description: 'Delete a workflow Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',
@@ -664,7 +664,7 @@ export const workflowTools = [
     },
     {
         name: 'workflow_template',
-        description: 'Save workflow as template or create from template',
+        description: 'Save workflow as template or create from template Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite is fine.',
         category: 'workflow',
         inputSchema: {
             type: 'object',

package/v3/@claude-flow/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claude-flow/cli",
-  "version": "3.7.0-alpha.21",
+  "version": "3.7.0-alpha.22",
   "type": "module",
   "description": "Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code",
   "main": "dist/src/index.js",