Omnigent 0.16.0 + Hermes on macOS: "hermes did not accept the message" and .env/auth.json copied into every session. Anyone fixed this?
I'm new to this, so apologies if I'm missing something obvious.
Setup: macOS (Apple Silicon), Omnigent 0.16.0 installed with uv tool install omnigent (Python 3.12), Node 22, tmux 3.7, Hermes Agent installed via git (up to date). Running fully local on 127.0.0.1:6767.
Problem 1: first message gets dropped. When I start a new Hermes session from the Omnigent desktop app, it fails with:inner executor error: hermes did not accept the message (the TUI may still be initializing); no new transcript row appeared after two delivery attempts
then Required terminal exited unexpectedly; the session runtime is no longer available.
The logs show Hermes is still starting up (installing dependencies, browser tool checks) when Omnigent pastes the message, and then Hermes exits with a KeyboardInterrupt. Running omnigent hermes in one-shot mode from the terminal works fine.
Problem 2: credentials copied per session. Every Hermes session creates a new folder under the macOS temp dir (.../T/omnigent-501/hermes-native/<id>/hermes_home/) with a copy of my Hermes .env and auth.json, plus about 1–2 GB of runtime. After one afternoon I had 19 folders (22 GB) and about 30 copies of my keys sitting in temp.
Questions:
- Has anyone gotten the Omnigent desktop app to reliably start Hermes sessions? Is there a setting to give Hermes more startup time?
- Is there a way to make Omnigent use an existing Hermes profile without copying its
.env/auth.jsoneach session (for example, a shared HERMES_HOME or a secrets manager)? - Is either issue fixed in a newer version, or is there a GitHub issue I should follow?
I'd like to eventually run a dedicated Hermes profile (one with sensitive API keys) through Omnigent, so the credential copying is the big blocker for me. Thanks!