eve adds new Slack event hooks and session controls
eve agents on Slack can now keep replies in a thread without repeated mentions, cancel in-progress responses, or reset conversations entirely. New hooks allow agents to react to any Slack event the app subscribes to, with helpers for detecting mentions, checking active sessions, and listing thread participants.
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 conversation should start over instead, terminally retires the session that owns the thread. The next delivered message begins a new session with fresh history, state, and sandbox. Inside your dispatch logic, a reset command takes three lines:ctx.reset()onMessage
Your agent can now react to any event your Slack app subscribes to.
The new hook receives raw events such as , , and . Inside the hook, call to start an agent turn, or call it several times to fan one event out to multiple targets. The event, for example, can kick off onboarding in each of your welcome channels.onEventreaction_addedteam_joinchannel_createdctx.receive()team_join
Read the to get started, or add the channel to your eve agent with .Slack channel documentationeve channels add slack
Continue conversations without repeated mentions
Cancel a turn or reset the conversation
Handle any Events API callback
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
OpenAI Decisions API now available on AI Gateway
OpenAI's Decisions API is now accessible through Vercel's AI Gateway with an OpenAI-compatible endpoint, enabling decision models to answer typed questions and return probabilities, choices, and scores for routing, triage, and guardrails use cases. Support is available across the OpenAI SDK, AI SDK, HTTP API, and CLI with the latest versions.
Timestamp attributes now supported in Vercel Flags
Vercel Flags now supports timestamp attributes for entities, allowing you to create time-based targeting rules. Use this feature to run limited-time campaigns, show content between specific dates, or target users based on registration date.
Glyph Cluster now available in stealth on AI Gateway
Glyph Cluster, a reasoning model for coding and long-context analysis, is now available as a stealth model on Vercel's AI Gateway for Pro and Enterprise plan teams with purchased AI Gateway credits at no cost during the stealth period. The model supports function calling, streams responses, and can be accessed via AI SDK, OpenAI-compatible APIs, and coding agents.