Skip to content
Novu logoNovu

Changelog

Latest updates and improvements in the agent communication category.

Follow us on X

All changelog posts

  • Web Chat for in-app agent conversations

    Embed a Novu Connect agent in your React application while Novu handles live delivery, history, approvals, and conversation state.

    Authors:
    Adam ChmaraVictor Yakubu
    Adam C., Victor Y.
    Cover image for Web Chat for in-app agent conversations

    Web Chat is now available in open beta on Novu Connect. It gives your agent an in-app channel, so users can start and continue a conversation inside your product instead of moving to Slack, Microsoft Teams, WhatsApp, Telegram, or email.

    The React client is headless. You build the message list, composer, and layout that fit your product. Novu manages the live connection, conversation history, agent-run state, tool approvals, and activity visible in the Dashboard.

    Read more: Web Chat for in-app agent conversations

  • Agent-Assigned Workflows

    Turn a workflow notification into the first turn of an agent conversation, with the original message and trigger payload already in context.

    Authors:
    Nikita GrossmanVictor Yakubu
    Nikita G., Victor Y.
    Cover image for Agent-Assigned Workflows

    You can now assign an agent to a workflow from the Novu Dashboard. Workflow messages are sent through the agent's connected channels, and when a subscriber replies, Novu routes the reply to that agent with the originating workflow, message, and trigger payload already in context.

    This closes the gap between notifications and conversations. A workflow can send “Your order has shipped,” the subscriber can reply “Can I change the delivery address?”, and the agent receives the order data from the original trigger without a separate correlation layer in your application.

    Read more: Agent-Assigned Workflows

  • LangChain adapter for Novu Connect

    Connect a LangChain or LangGraph agent to Slack, Microsoft Teams, WhatsApp, Telegram, and email, with mapped conversation history and in-channel tool approval on the adapter-managed path.

    Authors:
    Paweł TymczukVictor Yakubu
    Paweł T., Victor Y.
    Langchain adapter for Novu Connect

    The LangChain adapter is now available through @novu/framework/langchain. It gives teams already using LangChain or LangGraph a direct path to Novu Connect without rebuilding their agent for each communication channel.

    Read more: LangChain adapter for Novu Connect

  • Vercel AI SDK adapter for Novu Connect

    Bring an existing Vercel AI SDK agent to Slack, Microsoft Teams, WhatsApp, Telegram, and email while keeping the same model, tools, and application code.

    Authors:
    Adam ChmaraVictor Yakubu
    Adam C., Victor Y.
    Vercel AI SDK adapter for Novu Connect

    The Vercel AI SDK adapter is now available through @novu/framework/ai-sdk. Your agent continues to run your application. Novu Connect receives messages from each connected channel, passes the conversation context to your handler, and delivers the response that your handler returns.

    Read more: Vercel AI SDK adapter for Novu Connect

  • Novu Chat SDK Adapter

    Bring your Chat SDK agent to Slack, Teams, WhatsApp, Telegram, and email: deliver multi-channel notifications from one trigger, resolve every channel to one unified subscriber, and drop in React connect components to put channels in front of your end-customers.

    Author:Dima Grossman
    Dima Grossman

    The @novu/chat-sdk-adapter is now available. Wire it into your Chat SDK app and Novu manages credentials, identity, and delivery across Slack, Microsoft Teams, WhatsApp, Telegram, and email.

    Read more: Novu Chat SDK Adapter

  • In-conversation MCP authorization and message queues

    Connect external MCPs during the conversation and process incoming messages one at a time for a more predictable chat experience.

    Author:Dima Grossman
    Dima Grossman

    Connecting external MCPs is now part of the conversation itself, instead of a separate setup step. When an agent needs access to a tool, it can prompt the user to connect it right at that moment and then continue the original request once access is granted. This makes the experience feel much more natural and reduces the friction of getting started with tool-powered workflows.

    We also introduced session-level tool access, so connected tools are available only where they are relevant. That gives users a clearer sense of control over what an agent can use during a conversation, while helping keep tool usage focused on the task at hand.

    Read more: In-conversation MCP authorization and message queues