mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-05-18 04:41:56 +00:00
feat(computer-use): refresh cua-driver on hermes update + add install --upgrade (#24063)
cua-driver was only installed once on toolset enable: `_run_post_setup` early-returns when the binary is already on PATH, so upstream fixes (e.g. v0.1.6 Safari window-focus fix) never reached existing users without manual reinstall. Two refresh points now: - `hermes update` re-runs the upstream installer at the end of the update if cua-driver is on PATH (macOS-only, no-op otherwise). Ties driver freshness to the user-controlled update cadence — no startup latency, no per-launch GitHub API call. - `hermes computer-use install --upgrade` for manual force-refresh. The upstream `install.sh` always pulls the latest release, so re-running is the canonical upgrade path. No version-comparison logic needed. `hermes computer-use status` now shows the installed version, and points at `--upgrade` for refreshing.
This commit is contained in:
parent
97a0e69df0
commit
ced1990c1c
5 changed files with 308 additions and 50 deletions
|
|
@ -976,7 +976,8 @@ Subcommands:
|
|||
| Subcommand | Description |
|
||||
|------------|-------------|
|
||||
| `install` | Run the upstream cua-driver installer (macOS only). |
|
||||
| `status` | Print whether `cua-driver` is on `$PATH`. |
|
||||
| `install --upgrade` | Re-run the installer even if cua-driver is already on PATH. The upstream script always pulls the latest release, so this performs an in-place upgrade. |
|
||||
| `status` | Print whether `cua-driver` is on `$PATH` and which version is installed. |
|
||||
|
||||
`hermes computer-use install` is the stable entry point for installing the
|
||||
[cua-driver](https://github.com/trycua/cua) binary used by the
|
||||
|
|
@ -985,6 +986,11 @@ Subcommands:
|
|||
to use for re-running the install if the toolset toggle didn't trigger
|
||||
it (for example, on returning-user setups).
|
||||
|
||||
`hermes update` automatically re-runs the upstream installer at the end
|
||||
of the update if cua-driver is on PATH, so most users will not need to
|
||||
call `--upgrade` manually. Use it when upstream ships a fix you want
|
||||
right now without waiting for the next Hermes update.
|
||||
|
||||
## `hermes sessions`
|
||||
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -57,6 +57,23 @@ After installing, regardless of which path you took:
|
|||
```
|
||||
or add `computer_use` to your enabled toolsets in `~/.hermes/config.yaml`.
|
||||
|
||||
## Keeping cua-driver up to date
|
||||
|
||||
The cua-driver project ships fixes regularly (e.g. v0.1.6 fixed a Safari
|
||||
window-focus bug for UTM workflows). Hermes refreshes the binary in two
|
||||
places so you don't get stuck on a stale release:
|
||||
|
||||
- **`hermes update`** — when you update Hermes itself, if `cua-driver` is
|
||||
on PATH the upstream installer re-runs at the end of the update.
|
||||
No-op for non-macOS users and for users without cua-driver installed.
|
||||
- **`hermes computer-use install --upgrade`** — manual force-refresh.
|
||||
Re-runs the upstream installer regardless of whether cua-driver is
|
||||
already installed. Use this when you want the latest fix without
|
||||
waiting for the next agent update.
|
||||
|
||||
`hermes computer-use status` shows the installed version next to the
|
||||
binary path.
|
||||
|
||||
## Quick example
|
||||
|
||||
User prompt: *"Find my latest email from Stripe and summarise what they want me to do."*
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue