eve agents on Slack can now keep replying in a thread without repeated mentions, cancel an in-progress response or reset a conversation entirely, and react to any event your Slack app subscribes to. Mentions no longer have to carry the conversation. Once a thread has an active session, your agent can reply on its own. The new hook receives incoming Slack messages, and two helpers decide which ones to handle: detects an explicit mention, and checks whether the message belongs to a thread with an active eve session:onMessagectx.isBotMentioned()ctx.isSubscribed() When routing depends on who has joined the thread, the new helper returns unique human Slack user ids in first-appearance order.

Public channel messages require the trigger event type and the bot scope; private channels also need and .ctx.thread.listParticipants()message.channelschannels:historymessage.groupsgroups:history Message hooks also receive two thread-bound session helpers. stops the current turn while keeping the session: call it before returning to queue the new message as replacement input, so a mid-turn correction drops the stale work and the agent responds to the latest message.ctx.cancel(){ auth } When the…