Skip to main content
Import agent from @novu/framework when you are not using @novu/framework/ai-sdk or @novu/framework/langchain. Call your LLM, orchestration library, or business logic yourself, then reply through Novu’s handler API. Use this path for the OpenAI SDK, Anthropic SDK, or any stack Novu does not ship a dedicated adapter for.

​
Before you start

Completed the Quickstart? Your agent, bridge, and project are already set up — jump to Minimal agent. Otherwise start with the Quickstart first. All three onboarding paths (dashboard, CLI, AI assistant) walk you through creating the agent and wiring the bridge. This page covers only what’s specific to wiring your own LLM stack.

​
Prerequisites

Install the framework package: 
npm install @novu/framework
Bring your own LLM or agent library — Novu does not require a specific one.

​
Minimal agent

Import agent from @novu/framework, call your logic in onMessage, and reply by returning a string or calling ctx.reply(): 
import { agent } from '@novu/framework';

export const supportAgent = agent('support-bot', {
  onMessage: async (message, ctx) => {
    const response = await yourLLM.chat({
      messages: buildMessages(ctx.history),
    });

    return response.text;
  },
});
Make sure the agent id ('support-bot') matches the Identifier in your dashboard, and that this handler is registered on your bridge route — see Connecting your app. For handlers, replies, signals, typing, and tool approval, see Building blocks. The sections below cover what’s specific to wiring your own LLM stack — return types and manual tool approval.

​
Returning from onMessage

On this path, onMessage accepts the standard reply types — not AI SDK results:
ReturnBehavior
string / JSX CardDelivered as a reply — see Reply
ctx.toolApproval.request(...)Posts the Approve / Deny card and pauses the turn — see Tool approval
nothingAfter you call ctx.reply() yourself
Other handlers (onAction, onReaction, onResolve) accept string, Card, or nothing. Shorthand when you only need onMessage: pass the handler directly. 
const supportAgent = agent('support-bot', async (message, ctx) => {
  const text = await runAgent(message, ctx);

  return text;
});

​
Tool approval

When a tool needs human approval, return ctx.toolApproval.request() from onMessage: 
import { agent } from '@novu/framework';

export const supportAgent = agent('support-bot', {
  onMessage: async (message, ctx) => {
    const toolCall = detectToolCall(message, ctx);

    if (toolCall?.needsApproval) {
      return ctx.toolApproval.request(toolCall);
    }

    return runToolAndReply(toolCall, ctx);
  },

  onToolApproval: async (decision, ctx) => {
    if (!decision.approved) {
      await decision.approvalMessage.delete();

      return 'Cancelled.';
    }

    const result = await issueRefund(decision.toolCall.input);
    await decision.approvalMessage.delete();

    return `Refund issued for order ${result.orderId}.`;
  },
});
See Tool approval for the full API, card customization, and default behavior when you omit onToolApproval.

AI SDK

Return AI SDK results from handlers with automatic tool approval resume.

LangChain

Return LangChain agent configs with automatic tool approval resume.

Typing indicator

Show a Thinking… or custom status while your handler runs.

Reply

Markdown, attachments, and interactive cards.

Tool approval

The shared Approve / Deny primitive.