Bug Description
Summary
On Linux, Hermes Agent v0.12.0 crashes immediately after the welcome banner with:
Error: Invalid key: c-S-c
The TUI never reaches the prompt. Reproduces with both bare hermes and hermes -s
Reproduce: Everytime I startup hermes. Just started with today when I updated
Steps to Reproduce
Run hermes
Crash
Expected Behavior
It should boot normally
Actual Behavior
Crashes instead
Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
N/A (CLI only)
Debug Report
============================================================
FULL gateway.log
============================================================
[hermes debug share: log content redacted at upload time. run with --no-redact to disable]
--- hermes dump ---
version: 0.12.0 (2026.4.30) [8fabef9d]
os: Linux 6.17.0-22-generic x86_64
python: 3.11.15
openai_sdk: 2.32.0
profile: default
hermes_home: ~/.hermes
model: inclusionai/ling-2.6-1t:free
provider: openrouter
terminal: local
api_keys:
openrouter set
openai not set
anthropic not set
anthropic_token not set
nous not set
google/gemini not set
gemini not set
glm/zai not set
zai not set
kimi not set
minimax not set
deepseek not set
dashscope not set
huggingface not set
nvidia not set
ai_gateway not set
opencode_zen not set
opencode_go not set
kilocode not set
firecrawl not set
tavily not set
browserbase not set
fal not set
elevenlabs not set
github not set
features:
toolsets: hermes-cli
mcp_servers: 0
memory_provider: built-in
gateway: stopped (systemd (user))
platforms: none
cron_jobs: 0
skills: 134
config_overrides:
display.streaming: True
--- end dump ---
--- full gateway.log ---
2026-05-01 13:49:57,986 INFO gateway.run: Starting Hermes Gateway...
2026-05-01 13:49:57,987 INFO gateway.run: Session storage: /home/jt/.hermes/sessions
2026-05-01 13:49:57,994 WARNING gateway.run: No user allowlists configured. All unauthorized users will be denied. Set GATEWAY_ALLOW_ALL_USERS=true in ~/.hermes/.env to allow open access, or configure platform allowlists (e.g., TELEGRAM_ALLOWED_USERS=your_id).
2026-05-01 13:49:57,998 WARNING gateway.run: No messaging platforms enabled.
2026-05-01 13:49:57,999 INFO gateway.run: Gateway will continue running for cron job execution.
2026-05-01 13:49:58,052 INFO gateway.run: Channel directory built: 0 target(s)
2026-05-01 13:49:58,054 INFO gateway.run: Press Ctrl+C to stop
2026-05-01 13:49:58,273 INFO gateway.run: Cron ticker started (interval=60s)
2026-05-01 13:50:03,061 INFO gateway.run: kanban dispatcher: embedded in gateway (interval=60.0s)
2026-05-01 14:28:30,464 INFO gateway.run: Received SIGTERM/SIGINT — initiating shutdown
2026-05-01 14:28:30,535 INFO gateway.run: Shutdown diagnostic — no other hermes processes found
2026-05-01 14:28:30,536 INFO gateway.run: Stopping gateway...
2026-05-01 14:28:31,442 INFO gateway.run: Gateway stopped
2026-05-01 14:28:31,443 INFO gateway.run: Cron ticker stopped
2026-05-01 14:28:31,443 INFO gateway.run: Exiting with code 1 (signal-initiated shutdown without restart request) so systemd Restart=on-failure can revive the gateway.
2026-05-01 15:33:39,649 INFO gateway.run: Starting Hermes Gateway...
2026-05-01 15:33:39,650 INFO gateway.run: Session storage: /home/jt/.hermes/sessions
2026-05-01 15:33:39,653 WARNING gateway.run: No user allowlists configured. All unauthorized users will be denied. Set GATEWAY_ALLOW_ALL_USERS=true in ~/.hermes/.env to allow open access, or configure platform allowlists (e.g., TELEGRAM_ALLOWED_USERS=your_id).
2026-05-01 15:33:39,656 INFO gateway.run: Previous gateway exited cleanly — skipping session suspension
2026-05-01 15:33:39,656 WARNING gateway.run: No messaging platforms enabled.
2026-05-01 15:33:39,657 INFO gateway.run: Gateway will continue running for cron job execution.
2026-05-01 15:33:39,722 INFO gateway.run: Channel directory built: 0 target(s)
2026-05-01 15:33:39,724 INFO gateway.run: Press Ctrl+C to stop
2026-05-01 15:33:39,767 INFO gateway.run: Cron ticker started (interval=60s)
2026-05-01 15:33:44,732 INFO gateway.run: kanban dispatcher: embedded in gateway (interval=60.0s)
2026-05-01 16:13:52,079 INFO gateway.run: Received SIGTERM/SIGINT — initiating shutdown
2026-05-01 16:13:52,692 WARNING gateway.run: Shutdown diagnostic — other hermes processes running:
jt 35997 5.3 3.7 864460 294708 pts/2 Sl+ 15:56 0:54 /home/jt/.hermes/hermes-agent/venv/bin/python3 /home/jt/.local/bin/hermes
2026-05-01 16:13:52,772 INFO gateway.run: Stopping gateway...
2026-05-01 16:13:57,105 INFO gateway.run: Gateway stopped
2026-05-01 16:13:57,183 INFO gateway.run: Cron ticker stopped
2026-05-01 16:13:57,189 INFO gateway.run: Exiting with code 1 (signal-initiated shutdown without restart request) so systemd Restart=on-failure can revive the gateway.
2026-05-01 16:13:57,200 INFO gateway.run: Received SIGTERM/SIGINT — initiating shutdown
2026-05-01 16:13:57,235 WARNING gateway.run: Shutdown diagnostic — other hermes processes running:
jt 35997 5.2 3.7 864460 294708 pts/2 Sl+ 15:56 0:54 /home/jt/.hermes/hermes-agent/venv/bin/python3 /home/jt/.local/bin/hermes
Operating System
Linux Mint 22.3
Python Version
No response
Hermes Version
No response
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
Summary
On Linux, Hermes Agent v0.12.0 crashes immediately after the welcome banner with:
Error: Invalid key: c-S-c
The TUI never reaches the prompt. Reproduces with both bare hermes and hermes -s
Reproduce: Everytime I startup hermes. Just started with today when I updated
Steps to Reproduce
Run hermes
Crash
Expected Behavior
It should boot normally
Actual Behavior
Crashes instead
Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
N/A (CLI only)
Debug Report
Operating System
Linux Mint 22.3
Python Version
No response
Hermes Version
No response
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?