@honcho-ai/vercel-ai-sdk

Memory middleware and tools for the Vercel AI SDK, powered by Honcho.

Memory that reasons, not just recalls.

Honcho models the user behind the conversation — preferences, patterns, what they've told you over time — and injects that model into your prompts. Reasoning, not just retrieval from a vector DB.

Install

npm install @honcho-ai/vercel-ai-sdk

Requires ai@^6 and Node.js >=18.

Use the skill

The package ships a Skill that walks an agent through wiring Honcho into your Vercel AI SDK app. The skill greps for your generateText / streamText call sites, asks where userId / sessionId come from, and applies the integration in place.

npx skills add plastic-labs/vercel-ai-sdk

Then invoke /honcho-vercel-ai-sdk.

Alternative: manual symlink from npm package

If you've already installed @honcho-ai/vercel-ai-sdk via npm, you can symlink the skill directly. Example shown is for Claude Code:

mkdir -p ~/.claude/skills/honcho-vercel-ai-sdk
ln -sf "$(pwd)/node_modules/@honcho-ai/vercel-ai-sdk/skills/honcho-vercel-ai-sdk/SKILL.md" \
       ~/.claude/skills/honcho-vercel-ai-sdk/SKILL.md

Restart the session, then invoke /honcho-vercel-ai-sdk.

Environment

HONCHO_API_KEY=...
HONCHO_WORKSPACE_ID=...

createHoncho() reads API key/workspace from options and env.
If workspace is missing in both, it implicitly falls back to "vercel-ai-sdk" (with a one-time warning).

If userId or sessionId is omitted, the provider lazily generates IDs for that provider instance.

This is convenient for local scripts, demos, and single-user flows. For server apps or any setup where one provider instance may handle many users or conversations, pass userId and sessionId explicitly per request so memory does not bleed across requests.

You can also set explicit provider defaults for deterministic IDs:

const honcho = createHoncho({
  defaultUserId: "user",
  defaultAssistantId: "assistant",
  defaultSessionId: "session",
});

Resolution behavior:

• assistantId defaults to "assistant"
• missing userId lazily generates a provider-scoped user ID
• missing sessionId lazily generates a provider-scoped session ID

Override per call when needed, or disable session behavior with sessionId: null.

Quick Start

import { generateText, wrapLanguageModel } from "ai";
import { openai } from "@ai-sdk/openai";
import { createHoncho } from "@honcho-ai/vercel-ai-sdk";

const honcho = createHoncho({
  defaultAssistantId: "assistant",
});

const model = wrapLanguageModel({
  model: openai("gpt-4o-mini"),
  middleware: honcho.middleware({
    userId: request.user.id,
    sessionId: request.chatId,
  }),
});

const { text } = await generateText({
  model,
  prompt: "What should I focus on today?",
});

This is the recommended pattern for apps: keep the assistant identity stable, and pass userId plus sessionId from request context.

Local Scripts / Single-User Zero-Config

const honcho = createHoncho();

const model = wrapLanguageModel({
  model: openai("gpt-4o-mini"),
  middleware: honcho.middleware(),
});

const { text } = await generateText({
  model,
  tools: honcho.tools(),
  maxSteps: 3,
  prompt: "What should I focus on today?",
});

This uses generated IDs scoped to that provider instance. It is fine for local experiments and single-user flows, but not the safest default for multi-user server traffic.

Add Persistence

Set sessionId when you want explicit thread boundaries. Session mode is active by default (auto-generated when omitted), and can be disabled per call with sessionId: null:

const { text } = await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      userId: "user-123",
      sessionId: "chat-456",
    }),
  }),
  prompt: "What should I focus on today?",
});

With session mode active:

• output is always persisted as assistantId (default: "assistant")
• input is persisted when persistInput is true (default)

Add Tools

const { text } = await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      userId: "user-123",
      sessionId: "chat-456",
    }),
  }),
  tools: honcho.tools({
    userId: "user-123",
    sessionId: "chat-456",
  }),
  maxSteps: 3,
  prompt: "What should I focus on today?",
});

Available tools:

• honcho_chat (dialectic reasoning)
• honcho_context
• honcho_search
• honcho_search_conclusions
• honcho_get_representation
• honcho_save_conclusion

Messages Array Usage

If you already pass a messages array to generateText, disable Honcho history injection to avoid duplication:

await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      userId: "user-123",
      sessionId: "chat-456",
      injectHistory: false,
    }),
  }),
  messages: conversationHistory,
});

Multi-Peer

Choose which AI peer is generating with assistantId:

await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      assistantId: "agent-coordinator",
      userId: "alice",
      sessionId: "group-123",
    }),
  }),
  prompt: "Coordinate next steps for Alice.",
});

await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      assistantId: "agent-specialist",
      userId: "bob",
      sessionId: "group-123",
    }),
  }),
  prompt: "Respond as specialist for Bob.",
});

Manual Input Persistence

When your app persists user input itself, set persistInput: false:

await honcho.send({
  userId: "alice",
  sessionId: "group-123",
  content: "Can you help me plan this sprint?",
});

await generateText({
  model: wrapLanguageModel({
    model: openai("gpt-4o-mini"),
    middleware: honcho.middleware({
      assistantId: "coordinator",
      userId: "alice",
      sessionId: "group-123",
      persistInput: false,
    }),
  }),
  prompt: "Can you help me plan this sprint?",
});

Direct SDK Access

For advanced use cases, use the underlying @honcho-ai/sdk client:

const session = await honcho.client.session("chat-456");
const context = await session.context({
  peerPerspective: "assistant",
  peerTarget: "user-123",
  summary: true,
});

const openAIMessages = context.toOpenAI("assistant");
const anthropicMessages = context.toAnthropic("assistant");

Experimental Modules

These are still exposed as separate modules:

• @honcho-ai/vercel-ai-sdk/openai
• @honcho-ai/vercel-ai-sdk/identity

Development

npm run typecheck
npm run build

License

Apache-2.0