arnaudne/Epicure
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: chatbot model setting + tool-calling toggle, simplify admin AI config (v0.59.0)

Browse Source 
Chatbot (general assistant + per-recipe Q&A) now resolves its default model
from its own site setting (DEFAULT_CHAT_PROVIDER/MODEL) instead of sharing
the generic "text" use case with recipe generation, so admins can point it
at a different model.

Added AI_TOOL_CALLING_ENABLED: turns off the chatbot's createRecipe/
addToShoppingList tools (and the forced-retry pass) for models that don't
reliably support tool calling — it falls back to plain text answers.

Simplified the admin AI Configuration page: it showed provider keys and
routing settings twice (a read-only card, then an identical edit form).
Merged into one editable section; the resolved fallback provider is now a
one-line note instead of its own card.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Arnaud
2026-07-20 21:14:04 +02:00
parent f6975e98a9
commit 623e5bcd34
10 changed files with 120 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/web/app/api/v1/ai/cooking-chat/route.ts
+23 -12
View File
@@ -7,6 +7,7 @@ import { applyRateLimit } from "@/lib/rate-limit";
import { withAiQuota, resolveAiConfigOrError } from "@/lib/ai/ai-error";
import { getModelConfigForUseCase } from "@/lib/ai/resolve-user-key";
import { resolveModel } from "@/lib/ai/factory";
import { isAiToolCallingEnabled } from "@/lib/site-settings";
import { getUserPrivateBio, buildUserBioContext } from "@/lib/ai/user-bio";
import { createRecipeTool } from "@/lib/ai/tools/create-recipe-tool";
import { addToShoppingListTool } from "@/lib/ai/tools/add-to-shopping-list-tool";
@@ -68,9 +69,10 @@ export async function POST(req: NextRequest) {
const limited = await applyRateLimit(`rl:ai:${session!.user.id}`, 30, 60);
if (limited) return limited;
const [configResult, privateBio] = await Promise.all([
resolveAiConfigOrError(() => getModelConfigForUseCase(session!.user.id, "text")),
const [configResult, privateBio, toolCallingEnabled] = await Promise.all([
resolveAiConfigOrError(() => getModelConfigForUseCase(session!.user.id, "chat")),
getUserPrivateBio(session!.user.id),
isAiToolCallingEnabled(),
]);
if (!configResult.ok) return configResult.response;
const aiConfig = configResult.data;
@@ -79,16 +81,23 @@ export async function POST(req: NextRequest) {
const locale = (session!.user as { locale?: string }).locale ?? "en";
const lang = LANG[locale] ?? "English";
const system = `You are Epicure, a helpful culinary assistant answering general cooking questions — not tied to any specific recipe (techniques, substitutions, timing, equipment, food safety, etc). If asked who you are or what model/AI you're built on, say you're Epicure — never name the underlying model or provider. If a question has nothing to do with cooking or food, politely redirect. Keep answers under 200 words. Respond in ${lang}.\n\nYou have two tools. Using one only drafts something for the user to review — it never saves by itself.\n- createRecipe: the user is asking you to create, save, or write down a recipe (e.g. "make me a recipe for X", "give me a recipe for Y", "write that down"). This includes any request for a full recipe, not only ones that say the word "create" or "save".\n- addToShoppingList: the user is asking to add ingredients/items to a shopping list.\n\nIMPORTANT: when the user's request matches createRecipe, you MUST call that tool instead of writing the recipe's ingredients or steps directly in your text reply. Never output a full ingredient list or numbered steps as plain text — that content belongs in the tool call, not the message. Your text reply in that case should just be a short line like "Here's a draft — check it below and confirm if it looks right." Only skip the tool if the user is asking a general question (no specific recipe requested) or explicitly wants prose, not a structured recipe.${bioContext}`;
const toolsInstructions = toolCallingEnabled
? `\n\nYou have two tools. Using one only drafts something for the user to review — it never saves by itself.\n- createRecipe: the user is asking you to create, save, or write down a recipe (e.g. "make me a recipe for X", "give me a recipe for Y", "write that down"). This includes any request for a full recipe, not only ones that say the word "create" or "save".\n- addToShoppingList: the user is asking to add ingredients/items to a shopping list.\n\nIMPORTANT: when the user's request matches createRecipe, you MUST call that tool instead of writing the recipe's ingredients or steps directly in your text reply. Never output a full ingredient list or numbered steps as plain text — that content belongs in the tool call, not the message. Your text reply in that case should just be a short line like "Here's a draft — check it below and confirm if it looks right." Only skip the tool if the user is asking a general question (no specific recipe requested) or explicitly wants prose, not a structured recipe.`
: "";
const system = `You are Epicure, a helpful culinary assistant answering general cooking questions — not tied to any specific recipe (techniques, substitutions, timing, equipment, food safety, etc). If asked who you are or what model/AI you're built on, say you're Epicure — never name the underlying model or provider. If a question has nothing to do with cooking or food, politely redirect. Keep answers under 200 words. Respond in ${lang}.${toolsInstructions}${bioContext}`;
const result = await withAiQuota(session!.user.id, session!.user.tier as "free" | "pro" | "family", () =>
generateText({
model,
system,
prompt: parsed.data.question,
tools: { createRecipe: createRecipeTool, addToShoppingList: addToShoppingListTool },
stopWhen: stepCountIs(3),
}), { skipQuota: aiConfig.isByok }
generateText(
toolCallingEnabled
? {
model,
system,
prompt: parsed.data.question,
tools: { createRecipe: createRecipeTool, addToShoppingList: addToShoppingListTool },
stopWhen: stepCountIs(3),
}
: { model, system, prompt: parsed.data.question }
), { skipQuota: aiConfig.isByok }
);
if (!result.ok) return result.response;
@@ -101,8 +110,10 @@ export async function POST(req: NextRequest) {
// Catch both: the prose-list shape, or the user's own message clearly
// asking for a recipe in the first place. Rather than surface either
// failure, force the tool call on one extra pass — same system+prompt,
// just no longer letting the model opt out.
if (final.toolCalls.length === 0 && (looksLikeUnstructuredRecipe(final.text) || looksLikeRecipeCreationRequest(parsed.data.question, locale))) {
// just no longer letting the model opt out. Skipped entirely when tool
// calling is turned off admin-side (e.g. a local model that can't
// reliably call tools) — there's no tool to force in that case.
if (toolCallingEnabled && final.toolCalls.length === 0 && (looksLikeUnstructuredRecipe(final.text) || looksLikeRecipeCreationRequest(parsed.data.question, locale))) {
try {
const forced = await generateText({
model,