The database is empty, but this server is configured to create the first household from INITIAL_* environment variables instead of the public setup form. If you still see this after a restart, check the server logs for seeding errors, fix the configuration, and restart.
Start in Cookbook to browse, edit, and import recipes. Jump over to Groceries when you’re shopping, and use Pantry as the lighter utility for what you already have on hand.
Start in Cookbook to browse, edit, and import recipes. Jump over to Groceries when you’re shopping, and use Pantry as the lighter utility for what you already have on hand.
Use this for the active shopping run. Keep the current list tight, move pantry-worthy items out when they belong there, and treat this as the operational side of Kitchen.
Track what you already have and move stable staples out of Groceries once they’re home. Pantry stays intentionally lighter than Cookbook and Groceries.
Every meal on your plan for the week. It follows you across all your chats — so nothing gets lost, even in a very long thread — and you can tick meals off or drop them here.
No meals planned this week yet. Ask KitchenBot to plan the week and they’ll show up here (across every chat).
Just you — your settings follow you onto any device you sign into. Everyone in the household has their own.
Your personal color palette — just for you, and it follows you onto any device you sign into. Everyone in the household can pick their own.
Household identity, members, KitchenBot defaults, and the API key. Owners only.
Core identity for this household.
Manage who can access this household and adjust their role, PIN, and chat color.
KitchenBot uses these saved notes across chats when they are relevant.
These structured settings shape how KitchenBot behaves for your household by default.
Control whether this household uses the shared server key or an owner-provided Anthropic key.
This is a hobby app and is inherently insecure. You should set spend limits and monitor usage in your Anthropic account when using your own API key.
What everyone eats — likes, dislikes, and allergies. KitchenBot uses this to plan meals for the whole household, and it stays in sync with what you tell KitchenBot in chat. Anyone can view and add what they know.
Review Anthropic call volume and estimated cost for your current household.
This report is automatically scoped to your current household and helps owners monitor shared-key vs BYO-key usage.
Actions below apply to the household you select — not necessarily the household you are logged into.
Pick the household you want to inspect, then adjust configuration or review usage for that specific household.
| Display name | PIN (global admin) | View as |
|---|
Review token and cost usage with filters that make the underlying call ledger easier to scan.
Switch whether the selected household uses the shared server key or an owner-provided key.
Selected household uses the server shared key.
Provision a new household with an initial owner. Share the household key and PIN separately.