Hermes works best when it stays connected to real work
Hermes felt fast and useful when it ran directly on a MacBook. It was used every day for real tasks because it fit into the flow, could work from the , touch files, and run on the machine. A cleanup attempt used Codex to return the setup to something close to a fresh install, which removed most of the custom pieces that had been built around it.
Only the connection was kept. After that, Hermes felt slower, less capable, and less worth using for real tasks. A new attempt is running Hermes on a reached through SSH, but using it mainly through feels very limited.
The missing piece is the old -based setup, where Hermes could act more like part of the computer rather than only a chat .
Key points
- The local MacBook setup felt faster and more useful for daily work.
- Resetting to a fresh install removed the custom setup that made Hermes valuable.
- alone makes Hermes feel limited because it cannot easily work with and .
- Running Hermes on a through SSH may help with hosting, but it does not automatically restore the old workflow.
- Before cleaning up a Hermes setup, document or back up the parts that connect it to real tasks.