发布

  • fix(cua-driver-rs): macOS install 404 + config set not persisting to MCP sessions (#1518)

    frostbyte_neo 发布于 2026-05-14 17:19:18 +00:00

    • fix(cua-driver-rs): macOS install 404 + config not persisting to MCP sessions

    Install script 404 on Apple Silicon / Intel
    The script built the tarball URL as darwin-arm64-binary.tar.gz but the
    release only publishes a single darwin-universal-binary.tar.gz (lipo'd
    arm64 + x86_64). Fix: collapse all darwin-* LABEL values to the universal
    binary name; Linux per-arch tarballs (linux-x86_64-binary) are unchanged.

    config set not visible in MCP sessions
    cua-driver config set capture_mode vision wrote to ~/.cua-driver/config.json
    but MCP sessions always initialised DriverConfig from defaults, so every
    fresh mcp invocation reverted to capture_mode=som. Two changes:

    1. ToolState::default() now calls load_driver_config() which reads
      ~/.cua-driver/config.json at startup, so CLI config set changes
      carry over automatically into every subsequent MCP session.

    2. The set_config MCP tool now also writes through to disk via
      write_driver_config_key(), so config changes made inside an MCP session
      (e.g. via tools/call set_config) are likewise persisted for future sessions.

    Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com

    • fix(cua-driver-rs): address CodeRabbit review on config persistence
    • Use u32::try_from instead of as u32 cast in both load_driver_config
      and set_config invoke to prevent silent truncation of oversized
      max_image_dimension values; return an error to the caller when out-of-range
    • write_driver_config_key now returns Result<(), String> instead of
      swallowing I/O and JSON errors; callers log warnings on failure via
      tracing::warn! rather than silently succeeding

    Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com


    Co-authored-by: Claude Sonnet 4.6 noreply@anthropic.com

    下载附件