2026.03.16 Updates

[handstandsam]

Summary

• MCP Proxy with daemon reconnection: New STDIO-to-HTTP proxy (McpProxy) enables transparent daemon reconnection — MCP clients stay connected while the daemon restarts, with automatic session replay and exponential backoff
• MCP Resources: Added dynamic resource endpoints (trailblaze://about, config, devices, devices/connected, trails, tools/categories) so LLM clients can query system state via standard MCP protocol
• CLI transport modes: trailblaze mcp now defaults to proxy mode; added --direct/--no-daemon for in-process STDIO and --http for standalone HTTP
• Playwright driver management: Automated driver download and caching for production uber JARs (excludes ~194 MB driver-bundle JAR, fetches from Maven Central on first use)
• ProGuard shrinking: Production build optimization for desktop with rules preserving all critical libraries
• Config tool enhancements: New targetApp config key for dynamic app target selection; ConfigTrailblazeTool interface for tools that modify agent config rather than interact with devices
• On-device driver improvements: Better RPC-based screen state capture, driver type switch detection to clean up stale instrumentation processes, and on-device agent verification tracking
• MCP Bridge expansion: Comprehensive on-device driver support with ACCESSIBILITY and INSTRUMENTATION modes, driver creation timeout and latching
• Bridge UI action executor: New executor bridging Koog agent tool calls to TrailblazeTool infrastructure with dynamic tool repository support
• Direct MCP Agent updates: Support for config-modifying tools that change available tools mid-session
• .mcp.json: Standard MCP server config file for client integration

Test plan

• Verify trailblaze mcp launches proxy mode and connects to daemon
• Verify trailblaze mcp --direct runs in-process MCP server
• Verify MCP resources return correct data (trailblaze://devices, trailblaze://config, etc.)
• Verify daemon restart reconnection via proxy without client disconnection
• Verify Playwright driver auto-download on first production build run
• Verify ProGuard-shrunk desktop build launches correctly
• Run McpRealDeviceIntegrationTest and DeviceManagerToolSetTest