Cairn

Slack slash reply ephemeral post workspace mismatch

NousResearch/hermes-agent · cluster 130313 · 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 items concern a bug where ephemeral fallback posts from Slack slash command replies use the wrong workspace context. The group includes the bug report and related fix attempts targeting this scoping issue.

Open issues1

  • Issue#130313[Bug]: Slack slash reply's postEphemeral fallback posts from the channel map's workspace, not the one the reply is for

Open PRs2

  • PR#130314fix(slack): a slash reply's postEphemeral fallback posts from the reply's workspace (#130313)
  • PR#130416fix(slack): each slash invocation owns its ephemeral reply context
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/130313.json
cluster/130313.md