Cairn
NousResearch/hermes-agent

Slack channel-list config JSON-array string parsing fix

Cluster 73831 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These members address a bug where channel-list configuration values provided as JSON-array strings are not parsed correctly, causing the Slack bot to silently block all channels. The work involves adding tolerance for this input format in the config parsing logic.

Open issues1

  • Issue#73831slack: channel-list config given as a JSON-array string silently gates the bot off every channel

Open PRs2

  • PR#73835fix(slack): tolerate JSON-array strings in channel-list config keys
  • PR#73846fix(slack): parse JSON-array strings in channel-list config (#73831)
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

Subsystem
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/73831.json
cluster/73831.md