Cairn

Add Slack channel history read capability as agent tool

NousResearch/hermes-agent · cluster 6345 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
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
2 issues and 1 PR. Broad area: open items may be separate problems.

These items collectively address exposing Slack's conversations.history API as a read-only tool for agents, including the necessary OAuth scopes, event subscriptions, and gateway integration.

Open issues2

  • Issue#6345Feature: Slack gateway should expose conversations.history as an agent tool
  • Issue#35291feat: Slack adapter — add channel/DM history read scopes and message.channels event subscription

Open PRs1

  • PR#54535feat(slack): add read-only Slack channel history tool
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/6345.json
cluster/6345.md