Rust / Python Tool Parity

Overview

This document tracks parity between:

• Rust: @hanzo/dev (hanzo-dev crate) - npm package
• Python: hanzo-mcp (via hanzo-tools-* packages) - PyPI packages

Tool Comparison Matrix

Core Execution Tools

Agent & Planning Tools

Memory & State Tools

Reasoning Tools

Code Intelligence Tools

Browser & UI Tools

Network & API Tools

Integration Tools

Configuration Tools

Database Tools

Schema Alignment Needed

{
  "command": ["array", "of", "strings"],
  "workdir": "string",
  "timeout": "number"
}

{
  "command": "string",  // Single string, shell parses
  "cwd": "string",
  "timeout": "number",
  "env": {"key": "value"}
}

*** Begin Patch
*** Update File: path
@@ context
-old
+new
*** End Patch

{
  "file_path": "string",
  "old_string": "string",
  "new_string": "string"
}

Implementation Plan

Phase 1: Add Missing Python Tools (Priority) - ✅ COMPLETED

1. ✅ plan.update - Plan tracking with step status (added to hanzo-tools-plan)
2. ✅ proc.wait - Background command polling (added to hanzo-tools-shell)
3. ✅ fs.patch - Rust-style patch format (added to hanzo-tools-fs)
4. ✅ proc.exec - Array command format support (Rust parity)
5. 🔲 gh_actions_run_wait tool - GitHub Actions monitoring
6. 🔲 bridge tool - Client-side integration
7. 🔲 view_image tool - Image viewing with alt text
8. 🔲 web_search tool - Web search integration

Phase 2: Full Browser & Computer Control (Via MCP) - ✅ AVAILABLE

Rust dev connects to hanzo-mcp Python server, providing access to:

Browser Tool (90+ actions):

• Navigation: navigate, reload, go_back, go_forward, close
• Input: click, dblclick, type, fill, clear, press, select_option
• Forms: check, uncheck, upload
• Mouse: hover, drag, mouse_move, mouse_down, mouse_up, scroll
• Touch: tap, swipe, pinch
• Locators: get_by_role, get_by_text, get_by_label, get_by_test_id, etc.
• State: is_visible, is_enabled, is_checked, expect_* assertions
• Network: route, unroute (mock/block requests)
• Storage: cookies, clear_cookies, storage, storage_state
• Context: new_page, new_context, tabs, connect

Extension Integration (ports 9223/9224):

• CDP bridge for browser extensions
• Multi-client routing with namespaced targets
• Real-time WebSocket communication
• Falls back to Playwright if extension unavailable

Computer Tool (40+ actions):

• Mouse: click, double_click, right_click, move, drag, scroll
• Keyboard: type, write, press, key_down, key_up, hotkey
• Screen: screenshot, screenshot_region, get_screens
• Windows: get_active_window, list_windows, focus_window
• Batch: Execute multiple actions atomically

Screen Tool:

• session: Record screen → analyze → extract keyframes
• record/stop: Manual recording control
• Native backends: Quartz (macOS), xdotool (Linux), win32 (Windows)

Other MCP Tools:

• Memory: recall/create/update/delete memories, facts, knowledge bases
• Reasoning: think, critic, review, iching
• LSP/Refactor: semantic code analysis
• Database: SQL and graph operations
• Config/Mode: tool configuration

Phase 3: Schema Alignment

1. Unify shell command format (support both array and string)
2. Add apply_patch format to Python edit tool
3. Consolidate agent tool actions
4. Align browser tool action names

MCP Server Integration

Rust dev connects to hanzo-mcp via mcp_servers.hanzo config:

[mcp_servers.hanzo]
command = "hanzo-mcp"
args = []
startup_timeout_sec = 15
tool_timeout_sec = 60

This provides Rust access to all Python tools via MCP protocol.

Version Tracking

Testing Strategy

1. Unit Tests: Each tool has matching test coverage
2. Integration Tests: Cross-language tool invocation
3. Snapshot Tests: Output format consistency
4. E2E Tests: Full workflow validation

Notes

• Rust provides core low-latency tools (shell, patch, agent)
• Python provides extended tool ecosystem (memory, reasoning, LSP)
• MCP protocol bridges both ecosystems
• Focus on schema alignment for interoperability