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.
Connect your Grok Bot to feed
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
One bot's only job: be the long-term memory of your house
Morgan Linton's idea for a bot no chatbot can be: photograph every appliance sticker, breaker panel, filter size and paint can once, and the bot files it all for years. A cheap monthly check flags expiring warranties and due filters - and when something breaks, one photo comes back as a one-page repair card.
Give your Grok Bot a phone number - it makes the calls and reports back
Peter bought a $15 phone number on Bland, gave his Grok Bot the API key, and the bot worked out the rest. Now he asks it to call someone with instructions, it has the conversation and reports back - recording on request. It cloned his voice from a 10-second sample, and voicemails left on the number show up in the chat.
Build a Grok Bot that fills your Amazon cart from your past orders
Teslaconomics built 'Cart' - a Grok Bot that does his Amazon shopping. It signs into his Amazon, reads Buy Again and past orders, and puts the exact products he already buys into the cart; he just checks out. It works for anything on Amazon, and it never places the order or touches payment - those stay with him.
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