Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature] Observability for in-flight gateway sessions: agent.log silence + no live attach [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#18127•Fetched 2026-05-01 05:53:43
View on GitHub
Comments
2
Participants
1
Timeline
6
Reactions
0
Author
MillsAirCodeMillsAirCode
Participants
MillsAirCodeMillsAirCode
Timeline (top)
labeled ×4commented ×2

In Hermes 0.12.0 (commit bbbce926), there's no way to observe what an in-flight gateway agent session is doing. This makes it hard to know whether the agent is making progress, stuck, or burning the iteration budget on the wrong path.

Root Cause

  • User can't tell if the agent is stuck, looping, or making real progress.
  • Killing the gateway to "see what it was doing" loses 30+ min of context — the only debug move is destructive.
  • Hard to file good bug reports when mid-run state is invisible.
RAW_BUFFERClick to expand / collapse

Summary

In Hermes 0.12.0 (commit bbbce926), there's no way to observe what an in-flight gateway agent session is doing. This makes it hard to know whether the agent is making progress, stuck, or burning the iteration budget on the wrong path.

Repro

  1. Run hermes gateway run --replace (systemd user unit).
  2. Trigger a long-running agent task (e.g. via the claude-bridge webhook or api_server endpoint) that takes 30+ minutes.
  3. While the run is in flight, observe:
    • hermes sessions list shows nothing for the in-flight session — only finalized ones. state.db's messages table has zero rows from the active run.
    • hermes logs agent --since 1h shows only the startup line (Loaded environment variables) and is silent for every subsequent turn.
    • hermes logs gateway --since 30m is also silent.
    • Only journalctl --user -u llama-server proves the agent is alive (steady POST /v1/chat/completions traffic).
  4. No way to attach a CLI to the in-flight session — hermes --resume only takes finalized session IDs.

Why this matters

  • User can't tell if the agent is stuck, looping, or making real progress.
  • Killing the gateway to "see what it was doing" loses 30+ min of context — the only debug move is destructive.
  • Hard to file good bug reports when mid-run state is invisible.

Suggested fixes (any/all would help)

  1. agent.log per-turn writes for in-flight sessions — currently only the startup line lands. Possibly quiet_mode on a fork is suppressing per-turn logs; the file should still get them.
  2. Live transcript stream — e.g. hermes sessions tail --active subscribing to in-flight session events.
  3. List active sessions before they finalize — hermes sessions list --include-active flag, for ended_at IS NULL rows that the gateway flushes incrementally.
  4. --attach <session_id> — read-only attach to an in-flight session for live observability.

Environment

  • Hermes Agent v0.12.0 (2026.4.30), commit bbbce9265
  • Python 3.12.3, Linux (Ubuntu)
  • Backend: local llama-server (Qwen3.6-35B-A3B Q8_0, 262K ctx)
  • Gateway running as systemd user unit, in-process agent runs

extent analysis

TL;DR

To improve observability of in-flight gateway agent sessions in Hermes 0.12.0, consider implementing per-turn log writes, a live transcript stream, or listing active sessions before they finalize.

Guidance

  • Implement per-turn log writes for in-flight sessions to agent.log, potentially by disabling quiet_mode on the forked process.
  • Develop a live transcript stream feature, such as hermes sessions tail --active, to subscribe to in-flight session events.
  • Introduce a --include-active flag for hermes sessions list to display active sessions before they finalize, by querying ended_at IS NULL rows.
  • Consider adding a --attach <session_id> option for read-only attachment to in-flight sessions, enabling live observability.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The suggested fixes aim to address the lack of observability for in-flight sessions, but the actual implementation may vary depending on the internal workings of the Hermes gateway and agent.

Recommendation

Apply a workaround by implementing one of the suggested fixes, such as per-turn log writes or a live transcript stream, to improve observability of in-flight sessions. This will help users monitor progress and identify potential issues without relying on destructive debugging methods.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature] Observability for in-flight gateway sessions: agent.log silence + no live attach [2 comments, 1 participants]