Chef Kai Goes Social

This is the one we've been building toward. Chef Kai isn't just inside the app anymore — he's on Facebook Messenger, on your recipe pages, and ready to import recipes from anywhere on the internet. Let's break it all down.

Chef Kai on Facebook Messenger

This is the headline feature. DM @KitchenKaiApp on Facebook and Chef Kai responds. Same personality, same tools, same recipe knowledge — just in a platform you already use.

Share a YouTube video or recipe blog link in the conversation and Kai auto-imports the recipe. He'll extract ingredients, instructions, cook time, and servings — then send you a rich template card with the full recipe right there in Messenger.

The real magic is account linking. Type "link" in the conversation, enter your KitchenKai email, verify a code, and you're connected. Once linked, Kai knows your family size, allergens, dietary preferences, and pantry — so responses are personalized to you.

No OAuth popups. No app switching. Just a quick email verification right in the chat.

Recipe URL Import

We teased this in the v6 post. Now it's shipped and working everywhere.

Paste a YouTube cooking video URL and Kai extracts the full recipe from the transcript, video description, and comments. He picks the cheapest extraction path first — description and comments are nearly free, transcript costs a bit more, and vision (frame analysis) is the last resort.

Paste a recipe blog URL and Kai pulls from structured data (JSON-LD, microdata) or falls back to raw HTML parsing. Most recipe blogs have structured data these days, so extraction is fast and accurate.

Every imported recipe gets proper attribution. You'll see "▶️ Dish With Drew" or "🔗 Budget Bytes" with a clickable link back to the original source. We're not claiming credit for other people's recipes.

Dedup is built in. If you (or anyone) already imported that exact URL, Kai returns the existing recipe instead of creating a duplicate. URLs are normalized — YouTube playlist params, tracking codes, and index numbers get stripped before comparison.

This works in the app chat, on the web, and via Messenger. Same pipeline everywhere.

Community Image Gallery

Recipes aren't just text anymore. Every recipe now supports multiple photos — upload your own, browse what others have shared, and pick your favorite as the hero image.

• Upload your own photos — with rotate and crop editing built in
• "Set as my photo" — choose which image you see on recipe cards
• Delete your own uploads and re-edit with rotate/crop anytime
• Stock photo attribution — overlay shows the source on non-user images

The hero image on recipe cards follows a priority chain:

So if you've set a preference, that's what you see. If not, your own upload wins. If you haven't uploaded anything, the community's most popular photo shows. Stock images are the fallback.

Gallery metadata lives in DynamoDB (not RDS), so the original stock photo URL is never overwritten. Your uploads are additive.

Web Chat

Visit kitchenkai.com/recipes and you'll find Chef Kai embedded right on the page. No signup required.

Anonymous users get a limited toolset — recipe search, image lookup, and recipe creation. Enough to be useful, not enough to need an account. Ask Kai to modify the recipe you're viewing and he'll swap it inline on the page. "Make this dairy-free" — done, the recipe updates right there.

Quick suggestion chips appear for common requests: "Make it spicier", "Double the servings", "Substitute chicken". One tap and Kai handles it.

The chat uses the same WebSocket infrastructure as the app — real-time streaming responses, progress messages, the whole thing. It just skips chat history for anonymous sessions.

Orchestrator Playbook Architecture

Under the hood, the AI engine got its biggest refactor yet.

The old system prompt was a ~4,000 token monolith — every instruction for every possible pipeline crammed into one prompt. It worked, but it was slow, expensive, and the model would occasionally ignore instructions buried deep in the context.

Now we have a lean ~1,200 token base prompt plus on-demand playbooks. When Kai identifies what you're asking for (recipe search, meal planning, grocery list, URL import, pantry management, or FAQ), he fetches the detailed playbook for that specific pipeline. Only the relevant instructions load.

Six specialized playbooks:

• Recipe Search — how to search, filter, present results
• Meal Planning — date spreading, category logic, follow-ups
• Grocery — pantry comparison, staple filtering, cleanup
• URL Import — extraction pipeline, attribution, dedup
• Pantry — add/remove/update logic, expiry tracking
• FAQ — account questions, feature explanations, troubleshooting

Results: ~40% faster response times and the allergen safety check now fires reliably every single time. Before, it was buried at line 180 of the system prompt and occasionally got skipped. Now it's in the base prompt where the model always sees it.

Landing Page Refresh

The new kitchenkai.com is live. Highlights:

• Social proof section with a live Chef Kai demo
• URL import showcase — see the extraction pipeline in action
• Social bot teaser — Facebook (live), YouTube (beta), Instagram (coming soon)
• Updated roadmap reflecting where we actually are
• Pricing section with founding member rates and color-coded tier banners
• Unified nav across all pages (recipes, features, how it works, dev blog)

Privacy policy and data deletion pages are also deployed — required for the Facebook App Review process.

Quality of Life

The small stuff that adds up:

• Date range picker for grocery lists — custom Fri-Thu planning instead of always Mon-Sun. Pick your grocery shopping day and generate a list for exactly that window.
• Chat history fix — only the first user message was being saved to DynamoDB. Now every message persists. Old chats actually show the full conversation when you reload.
• Lazy recipe maintenance — old Spoonacular recipes auto-reformat on access. The database cleans itself through normal usage instead of requiring a migration.
• Meal plan stacking fix — adding a second meal of the same category no longer overwrites the first. UUID suffixes on meal IDs.
• Photo upload fix — recipe image uploads were silently failing (PUT path missing the recipe ID). All recipe updates were broken. Fixed.
• Safety check fix — allergen warnings now fire reliably (moved to base prompt via playbook architecture).
• Bold text on share pages — public recipe pages now render markdown bold correctly.
• Share link routing — deep links no longer show the wrong recipe for logged-in users.

What's Next

The social platform is just getting started:

• YouTube bot — Chef Kai responding to comments on our channel (needs first video published)
• Instagram integration — DM-based, same architecture as Facebook
• Google Play Store listing — public Android app distribution
• Family sharing — shared pantry, meal plans, and grocery lists across household members
• Voice assistant integration — "Alexa, ask KitchenKai what's for dinner"

The foundation is solid. Chef Kai lives on the web, in the app, and on Messenger — and the same orchestrator powers all of them. Adding new platforms is now a matter of writing an adapter, not rebuilding the brain.