## System details

- Omarchy `4.0.4-1`
- Linux kernel `7.2.5-3-omarchy`
- `hermes-desktop 2026.8.31-3` from the Omarchy repository
- The repository currently reports the same version as latest (`pacman -Si hermes-desktop`)
- Package build date: September 7, 2026
- Hermes backend after the Desktop self-update: `v0.21.3 (2026.9.14)`, upstream `3917c7dd`

## What's wrong?

The Omarchy `hermes-desktop` package is old enough that it predates Hermes' server→client JSON-RPC request support, while the packaged app allows its backend to self-update independently to a version that requires that protocol.

After using the built-in Hermes update, Desktop displayed:

```text
Backend updated, but the desktop app package (AppImage/deb/rpm) was not changed. Update or reinstall it to match.
```

The application then restarted with the new backend and the old packaged shell. This breaks all user-interaction requests that depend on the newer protocol, including smart command approvals and `clarify` questions.

### Steps to reproduce

1. Install the Omarchy `hermes-desktop 2026.8.31-3` package.
2. Launch Hermes Desktop and use its built-in updater.
3. Let it update the backend and restart.
4. Confirm the backend is now Hermes Agent `v0.21.3` while `pacman -Q hermes-desktop` is still `2026.8.31-3`.
5. With `approvals.mode: smart`, run a command that escalates for approval.
6. The approval dialog cannot be sent to the client, so the command is blocked with:

```text
server request approval ... not sent: the attached client predates server→client requests (update the Hermes app)
BLOCKED: Command approval was withdrawn before the user answered (the attached client cannot answer approval requests (update the Hermes app)).
```

`clarify` calls fail in the same way and return empty responses.

### Expected

The Omarchy package and Hermes backend should remain protocol-compatible. Possible packaging safeguards:

- update `hermes-desktop` to a build supporting server→client requests;
- coordinate Desktop package upgrades with backend upgrades;
- patch/configure the packaged app so it cannot self-update the backend beyond the installed shell's compatibility level;
- or declare/enforce a compatible backend constraint and provide a clear `pacman` repair path.

A user should never be left with a desktop app that looks operational but cannot display approvals, because the workaround is disabling approval protections entirely.

### Upstream report

NousResearch/hermes-agent#118070 tracks the upstream updater/compatibility side of the same failure.