Cairn
NousResearch/hermes-agent

Slack peer bot identity enforcement and authorization fixes

Cluster 85614 · 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 issues and pull requests address a gap in Slack sender authorization where identified peer bots could bypass or be ignored during final authorization checks. The work focuses on enforcing exact peer-bot identities to close this security gap.

Open issues1

  • Issue#85614Slack peer bot IDs are required for early delivery but ignored by final bot authorization

Open PRs2

  • PR#85643fix(slack): stop identified peer bots from bypassing sender authorization
  • PR#89044fix(slack): enforce exact peer-bot identities
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/85614.json
cluster/85614.md