Pantry checked Just now
Agent ready Local bridge online
Budget 25 / 40 GBP
Next delivery Sat, 11 May
Alerts 2 items
Overview
Your household command center.
Plan meals Done
2 Check pantry Done
3 Resolve conflicts In progress
4 Build shopping list Pending
5 Shop and cook Upcoming
Command strip
Say what you want NomNomBot to shop for.
assistant Tell me what you want NomNomBot to shop for. I will stage it as an agent instruction for the shopping page.
Stripe
Billing lives outside the shopping agent.
NomNomBot can link to Stripe for subscription checkout while grocery checkout remains a human-owned retailer action.
Agent-ready kitchen data
Enough structure for useful help. Enough scope to stay contained.
The product model keeps household context tight: recipes, calendar slots, pantry stock, shopping preferences, and agent credentials all resolve through the active tenant.
4 core food objects
1 scoped agent bridge
Flow
From recipe idea to matched basket.
01
Capture
Recipes arrive from the extension or a quick manual add.
02
Plan
Meals land on a calendar with servings, slots, and prep context.
03
Subtract
Pantry inventory removes the staples already sitting at home.
04
Delegate
The scoped agent resolves products, prices, and substitutions.
Recipes
Capture the food you actually cook
Save recipes from the browser extension or add them manually. Meal tags and ingredient lines make every recipe useful for planning.
Meal plan
Turn recipes into a calendar
Plan breakfasts, lunches, dinners, and snacks across the week, then generate a shopping list from the plan.
Pantry
Skip what is already at home
Keep staples and current inventory in one place so generated lists only ask the agent to buy what is missing.
Agents
Let local agents handle product matching
The tenant-scoped MCP bridge lets Codex read and write inside one household, then research carts, substitutions, and prices.
Connected workflow