Feishu auto-thread and session isolation feature requests

NousResearch/hermes-agent · cluster 9154 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; 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.

Multiple related proposals to add automatic thread-reply behavior in the Feishu/Lark integration, with topic-level session routing similar to Discord's threading model. Includes both opt-in per-mention and global auto-thread configuration approaches.

Open issues2

  • Issue#9154[Feature]: feishu/lark auto-thread with topic-level session isolation (like Discord)
  • Issue#30990feat(feishu): opt-in reply_in_thread for @-mention replies to keep main chat clean

Open PRs1

  • PR#137907feat(feishu): opt-in topic-thread replies in group chats (FEISHU_THREAD_REPLY)

1 PR closed without merging

From the close comments: other 1

  • #9118 feat(gateway): Feishu auto-thread and topic-based session routing · other → a79920f, #20548
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.39: 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
1 PR closed without merging

For your agent

The same facts, typed.