anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

fix: Slack bot doesn't deliver thread messages with @mentions to agents #9132

New Issue
Closed
opened 2026-02-16 18:11:42 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @dzianisv on GitHub (Feb 11, 2026).

Originally assigned to: @rekram1-node on GitHub.

Problem

When a user mentions an agent (e.g. @SupportEngineer) in a Slack thread where VibeTeam/the bot has already participated, the message is not delivered to the agent for processing.

Root Cause

The Slack bot only registers an app.message() handler, but does not handle app_mention events. When a user @mentions the bot in a thread, Slack sends an app_mention event which the bot completely ignores.

Additionally, the bot does not track threads where it has participated, so it cannot ensure that all follow-up messages in those threads are processed.

Expected Behavior

When VibeTeam/the bot has participated in a thread, ALL subsequent messages in that thread should be delivered to the agent, including:

  1. Direct @mentions of the bot
  2. Follow-up messages in threads where the bot has already responded

Steps to Reproduce

  1. Have the bot respond to a message in a channel (creating a thread)
  2. In the same thread, reply with: @SupportEngineer, please create a PR with a code fix.
  3. The message is not processed by the agent

Proposed Fix

  1. Add an app.event('app_mention') handler to process @mention events
  2. Track threads where the bot has participated (already partially done via the sessions Map)
  3. Ensure both message and app_mention events in tracked threads are routed to the correct session
  4. Deduplicate events (Slack may send both a message and app_mention event for the same @mention message)
Originally created by @dzianisv on GitHub (Feb 11, 2026). Originally assigned to: @rekram1-node on GitHub. ## Problem When a user mentions an agent (e.g. `@SupportEngineer`) in a Slack thread where VibeTeam/the bot has already participated, the message is not delivered to the agent for processing. ### Root Cause The Slack bot only registers an `app.message()` handler, but does not handle `app_mention` events. When a user @mentions the bot in a thread, Slack sends an `app_mention` event which the bot completely ignores. Additionally, the bot does not track threads where it has participated, so it cannot ensure that all follow-up messages in those threads are processed. ### Expected Behavior When VibeTeam/the bot has participated in a thread, ALL subsequent messages in that thread should be delivered to the agent, including: 1. Direct @mentions of the bot 2. Follow-up messages in threads where the bot has already responded ### Steps to Reproduce 1. Have the bot respond to a message in a channel (creating a thread) 2. In the same thread, reply with: `@SupportEngineer, please create a PR with a code fix.` 3. The message is not processed by the agent ### Proposed Fix 1. Add an `app.event('app_mention')` handler to process @mention events 2. Track threads where the bot has participated (already partially done via the sessions Map) 3. Ensure both `message` and `app_mention` events in tracked threads are routed to the correct session 4. Deduplicate events (Slack may send both a `message` and `app_mention` event for the same @mention message)
yindo closed this issue 2026-02-16 18:11:42 -05:00
yindo commented 2026-02-16 18:11:43 -05:00
Author
Owner
Copy Link
Copy Source

@dzianisv commented on GitHub (Feb 11, 2026):

Closing: this issue was filed against the wrong codebase. The actual fix was applied to VibeTechnologies/VibeTeam PR #92.

@dzianisv commented on GitHub (Feb 11, 2026): Closing: this issue was filed against the wrong codebase. The actual fix was applied to VibeTechnologies/VibeTeam PR #92.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9132
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?