terminator-mcp-agent 0.16.1 → 0.16.4

package/README.md

@@ -95,6 +95,9 @@ terminator mcp run workflow.yml --start-from "step_12" --end-at "step_13"
 
 # Run single step
 terminator mcp run workflow.yml --start-from "read_json" --end-at "read_json"
+
+# Execute jumps at end boundary (by default jumps are skipped at --end-at-step)
+terminator mcp run workflow.yml --end-at "step_5" --execute-jumps-at-end
 ```
 
 **Workflow File Formats:**
@@ -233,9 +236,9 @@ The Terminator MCP agent offers two primary workflows for automating desktop tas
 This is the most powerful and flexible method. You build a workflow step-by-step, using MCP tools to inspect the UI and refine your actions.
 
 1.  **Inspect the UI**: Start by using `get_focused_window_tree` to understand the structure of your target application. This gives you the roles, names, and IDs of all elements. For performance optimization:
-    - Use `include_tree: { max_depth: 2 }` to limit tree depth when you only need shallow inspection
-    - Use `include_tree: { from_selector: "role:Dialog" }` to get subtree from a specific element
-    - Use `include_tree: { from_selector: "true" }` to start from the currently focused element
+    - Use `tree_max_depth: 2` to limit tree depth when you only need shallow inspection
+    - Use `tree_from_selector: "role:Dialog"` to get subtree from a specific element
+    - Use `tree_from_selector: "true"` to start from the currently focused element
 2.  **Build a Sequence**: Create an `execute_sequence` tool call with a series of actions (`click_element`, `type_into_element`, etc.). Use robust selectors (like `role|name` or stable `properties:AutomationId:value` selectors) whenever possible.
 3.  **Capture the Final State**: Ensure the last step in your sequence is an action that returns a UI tree. The `wait_for_element` tool with `include_tree: true` is perfect for this, as it captures the application's state after your automation has run.
 4.  **Extract Structured Data with `output_parser`**: Add the `output_parser` argument to your `execute_sequence` call. Write JavaScript code to parse the final UI tree and extract structured data. If successful, the tool result will contain a `parsed_output` field with your clean JSON data.
@@ -717,9 +720,9 @@ The virtual display manager creates a memory-based display context that satisfie
 - Implement delays between rapid operations
 - Consider using `include_tree: false` for intermediate steps
 - For tree extraction tools, optimize with:
-  - `include_tree: { max_depth: 2 }` - Limit depth for large trees
-  - `include_tree: { from_selector: "role:List" }` - Get subtree from specific element
-  - `include_tree: { from_selector: "true" }` - Start from focused element
+  - `tree_max_depth: 2` - Limit depth for large trees
+  - `tree_from_selector: "role:List"` - Get subtree from specific element
+  - `tree_from_selector: "true"` - Start from focused element
 
 **JavaScript Performance**:
 
@@ -856,7 +859,8 @@ You can run specific portions of a workflow using `start_from_step` and `end_at_
     "url": "file://path/to/workflow.yml",
     "start_from_step": "read_json_file",    // Start from this step ID
     "end_at_step": "fill_journal_entries",  // Stop after this step (inclusive)
-    "follow_fallback": false                // Don't follow fallback_id beyond end_at_step (default: false)
+    "follow_fallback": false,               // Don't follow fallback_id beyond end_at_step (default: false)
+    "execute_jumps_at_end": false          // Don't execute jumps at end_at_step boundary (default: false)
   }
 }
 ```
@@ -867,6 +871,7 @@ You can run specific portions of a workflow using `start_from_step` and `end_at_
 - Run from step to end: Only set `start_from_step`
 - Run from beginning to step: Only set `end_at_step`
 - Debug without fallback: Use `follow_fallback: false` to prevent jumping to troubleshooting steps when a bounded step fails
+- Allow jumps at boundary: Use `execute_jumps_at_end: true` to execute jump conditions even at the `end_at_step` boundary (by default, jumps are skipped at the boundary for predictable execution)
 
 #### Automatic State Persistence
 
@@ -907,19 +912,16 @@ steps:
 - tool_name: get_window_tree
   arguments:
     pid: 1234
-    include_tree:
-      max_depth: 2  # Only get 2 levels deep
+    tree_max_depth: 2  # Only get 2 levels deep
 
 - tool_name: get_focused_window_tree
   arguments:
-    include_tree:
-      from_selector: "role:Dialog"  # Start tree from first dialog
-      max_depth: 3  # Limit depth from that point
+    tree_from_selector: "role:Dialog"  # Start tree from first dialog
+    tree_max_depth: 3  # Limit depth from that point
 
 - tool_name: get_focused_window_tree
   arguments:
-    include_tree:
-      from_selector: "true"  # Start from focused element
+    tree_from_selector: "true"  # Start from focused element
 
 # Backward compatible - still works
 - tool_name: get_window_tree

package/package.json

@@ -3,7 +3,8 @@
     "terminator-mcp-agent": "index.js"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.17.3"
+    "@modelcontextprotocol/sdk": "^1.17.3",
+    "node-fetch": "^2.7.0"
   },
   "description": "Cross-platform Model Context Protocol (MCP) agent for Terminator",
   "engines": {
@@ -15,10 +16,10 @@
   ],
   "name": "terminator-mcp-agent",
   "optionalDependencies": {
-    "terminator-mcp-darwin-arm64": "0.16.1",
-    "terminator-mcp-darwin-x64": "0.16.1",
-    "terminator-mcp-linux-x64-gnu": "0.16.1",
-    "terminator-mcp-win32-x64-msvc": "0.16.1"
+    "terminator-mcp-darwin-arm64": "0.16.4",
+    "terminator-mcp-darwin-x64": "0.16.4",
+    "terminator-mcp-linux-x64-gnu": "0.16.4",
+    "terminator-mcp-win32-x64-msvc": "0.16.4"
   },
   "repository": {
     "type": "git",
@@ -30,5 +31,5 @@
     "sync-version": "node ./utils/sync-version.js",
     "update-badges": "node ./utils/update-badges.js"
   },
-  "version": "0.16.1"
+  "version": "0.16.4"
 }