NousResearch/hermes-agent

Gateway log clarity for session keys and Slack errors

Cluster 111931. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #112214 on 16 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #112214. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #112214. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #112214, then check it covers your case.

Read #112214 Pick up a Lab task

These items address two specific observability gaps in gateway logging: the 'response ready' line missing thread/session key context, and Slack API-level failures being logged in a way that resembles transport errors. The work involves improving log output to carry session keys and surface Slack API error codes distinctly.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#112214 fix(gateway): response-ready log carries the session key; Slack edit failures log the API error code (#111931, salvage #111938)

merged to main

files: gateway/run_turn.py, plugins/platforms/slack/adapter.py, tests/gateway/test_empty_sentinel_rewrite_copy.py, tests/gateway/test_slack_send_retry.py

1 PR closed without merging

From the close comments: merged via another change 1

#111938 fix(gateway): improve response and Slack error logs · merged via another change → fb975fb, #112214

Closed issues · 1

Closed#111931Gateway log observability: "response ready" line lacks thread/session key; Slack API-level failures logged with HTTP status look like transport errors

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #112214
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/111931.json
cluster/111931.md