|
1 | 1 | # Hermes Desktop v1.2.0 |
2 | 2 |
|
3 | | -Hermes Desktop 1.2.0 adds first-class support for Hermes Agent running directly |
4 | | -on the same Mac. |
| 3 | +Hermes Desktop 1.2.0 is the local Hermes release. |
5 | 4 |
|
6 | | -Choose `This Mac` when Hermes is installed locally and use the full Desktop |
7 | | -workspace without configuring SSH to localhost. Sessions, Chat, Workflows, |
8 | | -Files, Skills, Usage, Cron, Kanban, discovery, and Terminal all operate against |
9 | | -your current macOS account's real Hermes data. |
| 5 | +If Hermes Agent runs on your Mac, you can now choose `This Mac` and use the |
| 6 | +whole Desktop workspace without setting up SSH to localhost. Sessions, Chat, |
| 7 | +Workflows, Files, Skills, Usage, Cron, Kanban, and Terminal work directly |
| 8 | +against your current macOS account's real Hermes installation. |
10 | 9 |
|
11 | | -Remote workflows remain fully supported. Existing connections still decode as |
12 | | -`SSH Host`, retain their exact workspace identities, and use the same SSH |
13 | | -arguments, ControlMaster behavior, retries, errors, terminal environment, and |
14 | | -profile scoping as before. |
| 10 | +The idea stays the same: Hermes Desktop does not create a second copy of your |
| 11 | +Hermes state. It now meets Hermes where it already runs, whether that is this |
| 12 | +Mac, a Raspberry Pi on your network, another Mac, a VPS, or a remote server. |
15 | 13 |
|
16 | | -## Direct-Local Hermes |
| 14 | +## What Changed |
17 | 15 |
|
18 | | -- Add a connection and choose `This Mac` or `SSH Host`. |
19 | | -- Local connections need only a name; SSH host, user, alias, and port fields are |
20 | | - hidden because they are not used. |
21 | | -- Named Hermes profiles and custom `HERMES_HOME` paths work in both modes. |
22 | | -- The embedded terminal launches a real local shell with the current user's |
23 | | - environment and the same Hermes bootstrap used for SSH terminals. |
24 | | -- Local mutations are clearly identified as changes to this Mac's real Hermes |
25 | | - files, sessions, scheduler, skills, and Kanban data. |
26 | | -- Direct-local mode is distinct from an SSH connection targeting `localhost`, |
27 | | - so saved workflows, bookmarks, pins, and profile preferences do not collide. |
| 16 | +- Connections now have an explicit `This Mac` or `SSH Host` mode. |
| 17 | +- `This Mac` needs only a connection name. There is no SSH alias, hostname, |
| 18 | + user, port, host-key setup, or passwordless SSH requirement. |
| 19 | +- Every main workspace surface supports local Hermes: Sessions and transcripts, |
| 20 | + the real Hermes TUI in Chat, Workflows, Files, Skills, Usage, Cron Jobs, |
| 21 | + Kanban, discovery, and Terminal. |
| 22 | +- The embedded Terminal opens a real local shell and uses the same Hermes |
| 23 | + profile, custom home, PATH preparation, and launch rules as the rest of the |
| 24 | + app. |
| 25 | +- Named profiles and custom `HERMES_HOME` paths work in both local and SSH |
| 26 | + mode. |
| 27 | +- Actions that edit files, skills, scheduler state, sessions, or Kanban make it |
| 28 | + clear when they are changing this Mac's real Hermes data. |
28 | 29 |
|
29 | | -## Compatibility And Safety |
| 30 | +## Existing SSH Connections |
30 | 31 |
|
31 | | -- Existing saved connection profiles without a connection type continue to load |
32 | | - as SSH connections. |
33 | | -- SSH fingerprints and workspace scope remain unchanged for existing users. |
34 | | -- Invalid future or malformed connection entries no longer prevent valid saved |
35 | | - connections from loading. |
36 | | -- English, Simplified Chinese, and Russian UI copy now describes local and SSH |
37 | | - operation accurately. |
| 32 | +Nothing about the remote workflow is being replaced. Existing saved |
| 33 | +connections continue to load as `SSH Host`, keep the same workspace identities, |
| 34 | +and retain the established SSH arguments, multiplexing behavior, retry path, |
| 35 | +terminal environment, and profile scoping. |
| 36 | + |
| 37 | +Direct-local mode is also intentionally separate from an SSH connection aimed |
| 38 | +at `localhost`, so workflows, bookmarks, pinned sessions, and preferences do |
| 39 | +not collide between the two. |
38 | 40 |
|
39 | | -## Additional Hardening |
| 41 | +## Also Included |
40 | 42 |
|
41 | | -- LAN SSH failures now point users to the macOS Local Network permission when |
42 | | - appropriate. |
43 | | -- Release packaging refuses dirty working trees. |
44 | | -- Release verification checks that the shipped bundle contains the Local |
45 | | - Network usage description required for LAN SSH hosts. |
| 43 | +- Saved connection loading is more resilient: malformed or future connection |
| 44 | + entries no longer prevent valid profiles from loading. |
| 45 | +- LAN SSH failures now point to the macOS Local Network permission when that is |
| 46 | + the likely blocker. |
| 47 | +- English, Simplified Chinese, and Russian copy now describes local and SSH |
| 48 | + operation accurately. |
46 | 49 |
|
47 | 50 | ## Requirements |
48 | 51 |
|
|
0 commit comments