@axiom-lattice/core 2.1.69 → 2.1.70

package/dist/index.js

@@ -19069,8 +19069,9 @@ Use this when the task follows a standard BPO (Business Process Orchestration) p
 
 **Step 2: Topology design.** Design the agent topology and use \`show_widget\` to render an interactive diagram showing the flow: Orchestrator \u2192 Stage 1 \u2192 Stage 2 \u2192 ... \u2192 Output. Each edge should be labeled with its business purpose.
 
-**Step 3: Design each sub-agent** (one at a time). For each:
+**Step 3: Design each sub-agent** as a **deep_agent** type (one at a time). For each:
 - Responsibility, system prompt, middleware, input/output contract
+- Deep agents have built-in file capabilities (ls, read, write, edit, glob, grep), so do NOT add filesystem middleware.
 - **Ask for confirmation before moving to the next sub-agent.**
 
 **Step 4: Design the orchestrator.** Responsibility, system prompt, topology edges, sub-agent list.
@@ -19101,7 +19102,7 @@ Use this when the task follows a standard BPO (Business Process Orchestration) p
  - Be detailed but concise \u2014 each section should be 1-5 lines
  - Avoid placeholder text like "TODO" or "TBD"
 
- **Example structure:**
+  **Example structure** (\u5B50 Agent \u5747\u4E3A deep_agent \u7C7B\u578B\uFF0C\u65E0\u9700 filesystem \u4E2D\u95F4\u4EF6):
 
  \`\`\`markdown
  ## Overview
@@ -19110,7 +19111,7 @@ Use this when the task follows a standard BPO (Business Process Orchestration) p
  ## Steps
  1. **\u6570\u636E\u91C7\u96C6 (data-collector)** \u2014 \u4F7F\u7528 browser \u5DE5\u5177\u722C\u53D6\u6307\u5B9AURL\u7684\u7ADE\u54C1\u4EF7\u683C\u6570\u636E\uFF0C\u8C03\u7528 metrics API \u62C9\u53D6\u5386\u53F2\u4EF7\u683C\u3002\u8F93\u51FA\u539F\u59CB\u4EF7\u683C\u6570\u636E\u96C6 JSON\u3002
  2. **\u6570\u636E\u6E05\u6D17 (data-cleaner)** \u2014 \u4F7F\u7528 code_eval \u6267\u884C Python \u811A\u672C\u6E05\u6D17\u5F02\u5E38\u503C\u548C\u7F3A\u5931\u503C\uFF0C\u7EDF\u4E00\u8D27\u5E01\u5355\u4F4D\u3002\u8F93\u51FA\u6807\u51C6\u5316\u6570\u636E\u96C6\u3002
- 3. **\u62A5\u544A\u751F\u6210 (report-generator)** \u2014 \u4F7F\u7528 filesystem \u8BFB\u53D6\u6A21\u677F\uFF0Ccode_eval \u8BA1\u7B97\u6DA8\u8DCC\u5E45\u548C\u8D8B\u52BF\uFF0C\u751F\u6210 Markdown \u5BF9\u6BD4\u62A5\u544A\u3002\u8F93\u51FA\u62A5\u544A\u6587\u4EF6\u8DEF\u5F84\u3002
+  3. **\u62A5\u544A\u751F\u6210 (report-generator)** \u2014 \u8BFB\u53D6\u6A21\u677F\u6587\u4EF6\uFF0Ccode_eval \u8BA1\u7B97\u6DA8\u8DCC\u5E45\u548C\u8D8B\u52BF\uFF0C\u751F\u6210 Markdown \u5BF9\u6BD4\u62A5\u544A\u3002\u8F93\u51FA\u62A5\u544A\u6587\u4EF6\u8DEF\u5F84\u3002
  4. **\u901A\u77E5\u63A8\u9001 (notifier)** \u2014 \u8C03\u7528 scheduler \u5B89\u6392\u5B9A\u65F6\u53D1\u9001\uFF0C\u4F7F\u7528 ask_user_to_clarify \u8BF7\u6C42\u53D1\u9001\u786E\u8BA4\u3002\u8F93\u51FA\u53D1\u9001\u7ED3\u679C\u3002
 
  ## Data Flow
@@ -19126,8 +19127,8 @@ Use this when the task follows a standard BPO (Business Process Orchestration) p
  | \u5B50Agent | \u5DE5\u5177 |
  |---------|------|
  | data-collector | browser, metrics |
- | data-cleaner | code_eval, filesystem |
- | report-generator | code_eval, filesystem |
+| data-cleaner | code_eval |
+| report-generator | code_eval |
  | notifier | scheduler, ask_user_to_clarify |
 
  ## Expected Input
@@ -19151,9 +19152,9 @@ Use this when the task follows a standard BPO (Business Process Orchestration) p
 Create sub-agents FIRST, then the orchestrator:
 
 \`\`\`
-1. create_agent(name: "stage-1", type: "react", ...)
-2. create_agent(name: "stage-2", type: "react", ...)
-3. create_agent(name: "stage-3", type: "react", ...)
+1. create_agent(name: "stage-1", type: "deep_agent", ...)
+2. create_agent(name: "stage-2", type: "deep_agent", ...)
+3. create_agent(name: "stage-3", type: "deep_agent", ...)
 4. create_processing_agent(
      name: "orchestrator",
      prompt: "...",
@@ -19190,7 +19191,7 @@ Use this for complex, open-ended tasks where the execution path cannot be fully
    - Work through todos one at a time
    - Refine the list as understanding deepens
    - Self-correct based on intermediate findings
-2. **Middleware** \u2014 filesystem, code_eval, browser, skill, widget, ask_user_to_clarify as needed
+2. **Middleware** \u2014 code_eval, browser, skill, widget, ask_user_to_clarify as needed (deep_agent already has built-in file capabilities, so filesystem middleware is NOT needed)
 3. **Sub-agents** (optional) \u2014 Specialized delegates for specific capabilities
 
 **Step 4: Self-review.** Verify: autonomy, tool coverage, guardrails.
@@ -19258,29 +19259,7 @@ All fields except name, type, and prompt are optional.
 
 ### create_processing_agent (PROCESSING)
 
-Creates a PROCESSING agent with a business-defined workflow topology. Sub-agents must already exist.
-
-\`\`\`typescript
-{
-  name: string,              // Required. Display name for the orchestrator
-  description?: string,      // Required for good UX. Comprehensive workflow spec in Markdown (Chinese if user speaks Chinese). Must cover: Overview, Steps (with tools per step), Data Flow, Logic & Conditions, Tools Used, Expected Input, Expected Output. This is the single source of truth displayed in the automation view info popover.
-  prompt: string,            // Required. System prompt \u2014 how to route through the topology
-  edges: [{                  // Required. At least 1 edge defining the workflow
-    from: string,            // Orchestrator's ID (use placeholder name; tool auto-replaces)
-    to: string,              // Sub-agent ID to delegate to
-    purpose: string,         // Business purpose \u2014 what this step accomplishes
-  }],
-  tools?: string[],          // Optional. Tool keys from list_tools
-  subAgents: string[],       // Required. IDs of sub-agents in the pipeline
-  internalSubAgents?: AgentConfig[],  // Optional. Inline sub-agent configs
-  middleware?: MiddlewareConfig[],    // Optional. Additional middleware (topology is auto-added)
-  modelKey?: string,         // Optional. Model to use
-}
-\`\`\`
-
-### create_processing_agent (PROCESSING)
-
-Creates a PROCESSING agent with a business-defined workflow topology. Sub-agents must already exist.
+Creates a PROCESSING agent with a business-defined workflow topology. Sub-agents must already exist (created as **deep_agent** type).
 
 \`\`\`typescript
 {
@@ -19292,6 +19271,7 @@ Creates a PROCESSING agent with a business-defined workflow topology. Sub-agents
     to: string,              // Sub-agent ID to delegate to
     purpose: string,         // Business purpose \u2014 what this step accomplishes
   }],
+  tools?: string[],          // Optional. Tool keys from list_tools
   subAgents: string[],       // Required. IDs of sub-agents in the pipeline
   internalSubAgents?: AgentConfig[],  // Optional. Inline sub-agent configs
   middleware?: MiddlewareConfig[],    // Optional. Additional middleware (topology is auto-added)
@@ -19422,13 +19402,13 @@ Provides: \`read_topo_progress\` \u2014 enforces multi-agent workflow topology.
 
 | Agent Role | Recommended Middleware |
 |-----------|----------------------|
-| Code assistant | filesystem, code_eval, widget |
-| Data analyst | filesystem, sql, code_eval, widget |
-| Web researcher | browser, filesystem, widget |
+| Code assistant | code_eval, widget |
+| Data analyst | sql, code_eval, widget |
+| Web researcher | browser, widget |
 | Operations / SRE | metrics, sql, widget |
 | Process orchestrator | skill, date, scheduler, widget |
-| General assistant | filesystem, date, widget |
-| Approval-gated operations | ask_user_to_clarify, filesystem, widget |
+| General assistant | date, widget |
+| Approval-gated operations | ask_user_to_clarify, widget |
 | Interactive Q&A | ask_user_to_clarify, date, widget |
 
 ### update_processing_agent