Skip to content

Tags: trycua/cua

Tags

cua-driver-v0.2.0

Toggle cua-driver-v0.2.0's commit message
Bump cua-driver to v0.2.0

cua-driver-rs-v0.2.1

Toggle cua-driver-rs-v0.2.1's commit message
Bump cua-driver-rs to v0.2.1

cua-driver-rs-v0.2.0

Toggle cua-driver-rs-v0.2.0's commit message
Bump cua-driver-rs to v0.2.0

cua-driver-rs-v0.1.4

Toggle cua-driver-rs-v0.1.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(cua-driver-rs): macOS install 404 + config set not persisting to …

…MCP sessions (#1518)

* 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>

cua-driver-rs-v0.1.3

Toggle cua-driver-rs-v0.1.3's commit message
Bump version: 0.1.2 → 0.1.3

cua-driver-v0.1.9

Toggle cua-driver-v0.1.9's commit message
Bump cua-driver to v0.1.9

cua-driver-v0.1.8

Toggle cua-driver-v0.1.8's commit message
fix(cd): rename .release-upload → release-upload (hidden dir excluded)

upload-artifact@v4 defaults to include-hidden-files: false, which
skips all directories starting with '.'. The staging dir
'.release-upload/' is a dotfile directory so @actions/glob silently
excluded every file inside it. Rename to 'release-upload' (no dot).

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

cua-driver-v0.1.7

Toggle cua-driver-v0.1.7's commit message
Bump cua-driver to v0.1.7

cua-driver-v0.1.6

Toggle cua-driver-v0.1.6's commit message
Bump cua-driver to v0.1.6

cua-driver-v0.1.5

Toggle cua-driver-v0.1.5's commit message
Bump cua-driver to v0.1.5