Skip to content

feat(gateway): Enable Slack thread replies without explicit @mentions - #5579

Closed
jarvisxyz wants to merge 1 commit into
NousResearch:mainfrom
jarvisxyz:2026-04-06.eizus.slack-thread-replies
Closed

feat(gateway): Enable Slack thread replies without explicit @mentions#5579
jarvisxyz wants to merge 1 commit into
NousResearch:mainfrom
jarvisxyz:2026-04-06.eizus.slack-thread-replies

Conversation

@jarvisxyz

Copy link
Copy Markdown
Contributor

Fork PR: jarvisxyz#1 (testing/verification)

Changes:
When a user replies in a Slack thread where the bot has an active conversation session, the bot now processes the message even without an explicit @mention. This improves UX for ongoing threaded discussions.

  • Added set_session_store() to BasePlatformAdapter for adapters to check active sessions
  • Modified SlackAdapter to detect thread replies and check if a session exists for that thread before requiring @mentions
  • Updated GatewayRunner to inject the session store into adapters
  • Added comprehensive tests for the new behavior

Testing:
Tests included in tests/gateway/test_slack.py covering:

  • Thread replies without @mention are processed if session exists
  • Channel messages still require @mention
  • Edge cases for thread detection

Related: This addresses the common user expectation that once a thread conversation is started, replies within that thread should not require repeated @mentions.

When a user replies in a Slack thread where the bot has an active
conversation session, the bot now processes the message even without
an explicit @mention. This improves UX for ongoing threaded
discussions.

Changes:
- Added set_session_store() to BasePlatformAdapter for adapters to
  check active sessions
- Modified SlackAdapter to detect thread replies and check if a
  session exists for that thread before requiring @mentions
- Updated GatewayRunner to inject the session store into adapters
- Added comprehensive tests for the new behavior

Fixes: Thread replies without @jarvis are now processed if there is
an active session, matching user expectations for conversation flow
@teknium1

teknium1 commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

Merged via PR #5733. Your commit was cherry-picked with authorship preserved. Thanks @jarvisxyz!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants