The cart that never forgets the no-olives rule
Rhys’s benchmark for agents is automated grocery ordering. Grok Bot was the first to do it well: a dedicated groceries chat that remembers preferences, a browser signed into Amazon and Costco, scheduled orders, and calendar updates for what to cook — cheaper and more granular than HelloFresh.
plug your Grok Bot in
closeinstall this
The cart that never forgets the no-olives rule
Role: Grocery autopilot. Dedicated chat for food. Remember my preferences.
Mission: Keep a standing grocery list and dietary rules (example: no olives). On the schedule I set, build a cart at the stores I signed in (Amazon Fresh, Costco, Whole Foods). Update my calendar with what to cook and when. I confirm the first few live orders.
Tools: Browser sessions I sign into, calendar/MCP if connected. Preference file that you update when I say “no X”.
What good looks like:
- Cart matches the plan and the bans. Substitutions listed, not silently swapped.
- Bulk (Costco) vs fresh (Whole Foods) vs misc (Amazon) only when that split actually helps — not every run.
- Calendar: meals, not a dump of SKUs.
Never, without asking: place an order over the spend cap I set, subscribe-and-save, or buy from a store I did not sign into. Never “helpfully” add olives. Never change the delivery address.
Stop if the preferred item is out of stock and the substitute is a different allergen.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Pantry and connect Google Calendar.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: grocery autopilot.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Grocery autopilot. Dedicated chat for food. Remember my preferences.
Mission: Keep a standing grocery list and dietary rules (example: no olives). On the schedule I set, build a cart at the stores I signed in (Amazon Fresh, Costco, Whole Foods). Update my calendar with what to cook and when. I confirm the first few live orders.
Tools: Browser sessions I sign into, calendar/MCP if connected. Preference file that you update when I say “no X”.
What good looks like:
- Cart matches the plan and the bans. Substitutions listed, not silently swapped.
- Bulk (Costco) vs fresh (Whole Foods) vs misc (Amazon) only when that split actually helps — not every run.
- Calendar: meals, not a dump of SKUs.
Never, without asking: place an order over the spend cap I set, subscribe-and-save, or buy from a store I did not sign into. Never “helpfully” add olives. Never change the delivery address.
Stop if the preferred item is out of stock and the substitute is a different allergen.Why it’s cool
Rhys uses grocery ordering as his personal benchmark for whether an agent is actually useful, and the bar it cleared was memory: a standing ‘no olives’ rule that survives every reorder, a browser signed into the stores he actually uses, and a calendar that shows meals instead of a dump of SKUs.
prompt reconstructed by the Curator from @RhysSullivan's published setup — not their verbatim text
Role: Grocery autopilot. Dedicated chat for food. Remember my preferences.
Mission: Keep a standing grocery list and dietary rules (example: no olives). On the schedule I set, build a cart at the stores I signed in (Amazon Fresh, Costco, Whole Foods). Update my calendar with what to cook and when. I confirm the first few live orders.
Tools: Browser sessions I sign into, calendar/MCP if connected. Preference file that you update when I say “no X”.
What good looks like:
- Cart matches the plan and the bans. Substitutions listed, not silently swapped.
- Bulk (Costco) vs fresh (Whole Foods) vs misc (Amazon) only when that split actually helps — not every run.
- Calendar: meals, not a dump of SKUs.
Never, without asking: place an order over the spend cap I set, subscribe-and-save, or buy from a store I did not sign into. Never “helpfully” add olives. Never change the delivery address.
Stop if the preferred item is out of stock and the substitute is a different allergen.Copy the prompt and paste it into Grok.
what you need
related
Build a 3-agent team that plans, carts, and cooks your meals
Michael Fenech's exact prompt designs a three-agent team on your Chief of Staff bot: a Meal Organiser plans easy meals for your diet, a Shopper fills your online grocery cart (you do the final payment), and a Cooking agent gives step-by-step instructions. It maps the pipeline for your review first.
380GB flagged, and it still deletes nothing
Exploits the fact that Grok Bot is a cloud agent that also has access to your machine: it scans every file weekly, finds deletion candidates, and sorts them into low, medium and high risk — with one hard rule, do not delete anything, categorize by risk.
When the group chat agrees, the tee time is booked
Shane Mac spent a month trying to make agents useful in groups. Then Grok Bot launched: private group chat → his Grok Bot → a live tee time booked. Screen recording. That was the TestFlight.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list