hermes - 💡(How to fix) Fix computer-use install fails on Intel macOS when CUA x86_64 release asset is missing

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

hermes computer-use install fails on Intel macOS because it resolves the latest CUA Driver release, then attempts to download an Intel-specific asset that is not published for the current CUA release.

This appears to be caused by an upstream CUA release packaging issue, but Hermes currently surfaces it as a raw 404 and leaves the user without a clear path forward.

Upstream issue: https://github.com/trycua/cua/issues/1493

Error Message

Installing cua-driver (macOS background computer-use)... ==> resolving latest cua-driver-v* release via GitHub API ==> latest release: cua-driver-v0.1.6 ==> downloading https://github.com/trycua/cua/releases/download/cua-driver-v0.1.6/cua-driver-0.1.6-darwin-x86_64.tar.gz curl: (56) The requested URL returned error: 404 error: download failed; try CUA_DRIVER_VERSION=<version> to pin a specific release ⚠ cua-driver installing did not complete.

Root Cause

hermes computer-use install fails on Intel macOS because it resolves the latest CUA Driver release, then attempts to download an Intel-specific asset that is not published for the current CUA release.

Fix Action

Fix / Workaround

  • Mac: Intel MacBook Pro
  • Architecture: x86_64
  • macOS: 15.7.5
  • CUA Driver release resolved by installer: cua-driver-v0.1.6

The generic cua-driver.tar.gz from cua-driver-v0.1.6 is not a workaround on Intel. It contains an arm64-only binary:

Code Example

hermes computer-use install

---

Installing cua-driver (macOS background computer-use)...
==> resolving latest cua-driver-v* release via GitHub API
==> latest release: cua-driver-v0.1.6
==> downloading https://github.com/trycua/cua/releases/download/cua-driver-v0.1.6/cua-driver-0.1.6-darwin-x86_64.tar.gz
curl: (56) The requested URL returned error: 404
error: download failed; try CUA_DRIVER_VERSION=<version> to pin a specific release
⚠     cua-driver installing did not complete.

---

CuaDriver.app/Contents/MacOS/cua-driver: Mach-O 64-bit executable arm64

---

Non-fat file ... is architecture: arm64
RAW_BUFFERClick to expand / collapse

Summary

hermes computer-use install fails on Intel macOS because it resolves the latest CUA Driver release, then attempts to download an Intel-specific asset that is not published for the current CUA release.

This appears to be caused by an upstream CUA release packaging issue, but Hermes currently surfaces it as a raw 404 and leaves the user without a clear path forward.

Upstream issue: https://github.com/trycua/cua/issues/1493

Environment

  • Mac: Intel MacBook Pro
  • Architecture: x86_64
  • macOS: 15.7.5
  • CUA Driver release resolved by installer: cua-driver-v0.1.6

Steps to reproduce

On an Intel Mac, run:

hermes computer-use install

Actual behavior

Installing cua-driver (macOS background computer-use)...
==> resolving latest cua-driver-v* release via GitHub API
==> latest release: cua-driver-v0.1.6
==> downloading https://github.com/trycua/cua/releases/download/cua-driver-v0.1.6/cua-driver-0.1.6-darwin-x86_64.tar.gz
curl: (56) The requested URL returned error: 404
error: download failed; try CUA_DRIVER_VERSION=<version> to pin a specific release
⚠     cua-driver installing did not complete.

Expected behavior

Hermes should handle this more clearly, for example by:

  • detecting that the latest CUA release lacks an Intel macOS asset before attempting download,
  • suggesting/pinning a known compatible CUA Driver version if one exists,
  • falling back to the official CUA installer only if it will actually resolve the architecture issue, or
  • showing a clear message that the current upstream CUA Driver release does not provide an Intel-compatible macOS build.

Additional verification

The expected Intel asset does not exist:

https://github.com/trycua/cua/releases/download/cua-driver-v0.1.6/cua-driver-0.1.6-darwin-x86_64.tar.gz

The generic cua-driver.tar.gz from cua-driver-v0.1.6 is not a workaround on Intel. It contains an arm64-only binary:

CuaDriver.app/Contents/MacOS/cua-driver: Mach-O 64-bit executable arm64

lipo reports:

Non-fat file ... is architecture: arm64

Notes

CUA Driver docs currently say Intel Macs are supported, so this may resolve upstream. Still, Hermes could provide a clearer diagnostic or compatibility check for Intel macOS users.

Related issues checked

I searched for duplicates before filing. I did not find an exact duplicate.

  • #24170 is related to computer_use / cua-driver-v0.1.6 on macOS, but it covers wrapper/runtime bugs after installation on arm64-compatible CUA Driver, not Intel macOS installation failure due to a missing x86_64 release asset.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Hermes should handle this more clearly, for example by:

  • detecting that the latest CUA release lacks an Intel macOS asset before attempting download,
  • suggesting/pinning a known compatible CUA Driver version if one exists,
  • falling back to the official CUA installer only if it will actually resolve the architecture issue, or
  • showing a clear message that the current upstream CUA Driver release does not provide an Intel-compatible macOS build.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING