a8c959bfab
A recipe was previously a dead end: you could save one and see whether your bar could make it, but there was no way to record that you had actually drunk it. Promoting links rather than converts. A drink is created and Recipe.sourceDrinkId is set to point at it, so the recipe survives and then renders on that drink's page through the relation the drink detail view already reads. The wishlist path creates a "try later" entry tagged source=recipe and leaves the recipe alone. Both are idempotent. Promoting an already-linked recipe returns the existing drink with a 200 rather than creating a second one, because pressing the button twice is a double click and not a request for a duplicate. Creation and linking happen in one transaction - a drink that existed but was not linked back would show no recipe and would be promoted again on the next attempt. The logic lives in src/lib/recipe-promotion.ts and is shared by the REST route and the MCP tool, so the ownership check, the idempotency rule and the generated description cannot drift apart. Adding to drinks navigates straight to the rating page: being able to rate it is the entire point, and an unrated cocktail is easy to lose in a list of 88. There is no Toaster mounted in this app, so the wishlist path reports inline instead. One MCP tool with a target parameter rather than two, since the tool list is already at the point where selection quality suffers - 23 now. Gated on drinks:write, not bar:write: it changes the collection, not the bar. Verified: promote to drink then rate it, idempotency on both targets, the recipe stays linked and undeleted, invalid target, unknown recipe, unauthenticated access, read-only tokens, and that another user's recipe is refused identically on both the REST route and the tool without confirming the row exists. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1Ee4Mc1X1SX8HgYa52zu7
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
AI Gateway (Switchboard)
All AI features — menu scanning, label identification, drink search, the bartender
and the recommendation engine — go through Switchboard,
an OpenAI-compatible gateway that routes each request to the best available model.
The app never pins a model id; it always sends switchboard/auto and lets the gateway
choose, then logs which model answered and what it cost.
Setup:
- Set
SWITCHBOARD_BASE_URLin your env file (defaults tohttp://192.168.2.11:8787/v1). - Mint an API key in the Switchboard UI under Settings → API keys.
- Add that key in the app under Settings → AI Gateway.
Per-feature routing (cost/quality levers, token budgets, timeouts) lives in
src/lib/ai/routing.ts. Note that a Switchboard key carries its own routing defaults,
so the app sets category and prefer_free explicitly on every request rather than
inheriting whatever the key was minted for.
Migrating from the old Claude/OpenAI integration
Earlier versions stored a per-user Anthropic or OpenAI key. Those rows are ignored at runtime and the Settings page offers to remove them, so no migration is required. To clear them in bulk instead:
DELETE FROM "UserApiKey" WHERE provider IN ('claude','openai');
DELETE FROM "SearchCache" WHERE provider IN ('claude','openai');
UPDATE "UserPreference" SET "defaultProvider" = NULL;
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.