When should you use it?
- Several people in the house add to the shopping list
- You reorder similar items each week
- You want the cart built but not paid for
Not for: Stores that forbid automated access in their terms; Anyone wanting fully unattended spending
What do you need, and what do you get?
You need
- Past order history
- Whitelisted chat members
- Store login
You get
- Agreed list in the chat
- A validated cart waiting for checkout
How does it work, step by step?
- Restrict who can talk to itAllow only household numbers in the chat the agent listens to.
- Start from past ordersHave the agent post a first draft drawn from what you usually buy.
- Collect editsMembers add, remove or change quantities in the thread until a cutoff time.
- Fill the store cartThe agent fills the store cart and reports anything out of stock or substituted.
- Finish checkout yourselfReview the cart and place the order in the store's own app.
The prompt
Our own prompt, inspired by post_below on Hacker News and written to work in OpenClaw, Custom agent and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is this week's grocery thread: {thread} Suggested list based on recent orders: {draft_list} Merge the requests into one list with quantities, flag conflicts between people, and ask about anything ambiguous. After I confirm, build the cart at {store}, list out-of-stock items and substitutions, and stop before checkout.
Inspired by post_below on Hacker News: Hacker News comment on a self-hosted Signal agent for grocery orders. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Without a cutoff, edits keep arriving after the cart is built.
- Giving the agent payment ability is a separate decision; the author held off on it.
Our take
The part to copy is the split of responsibilities: the group decides, the agent assembles and checks, a person pays. That keeps useful automation, collecting everyone's requests and building a long cart accurately, while spending stays human. post_below's setup restricts the Signal group to approved household numbers, which is the first thing to copy; an open chat would let anyone add to your order. Starting from past orders gives the family a draft to edit rather than a blank list, and that is where most of the time saving comes from. Set a cutoff time for edits, or changes keep arriving after the cart is built. When the agent fills the store cart, have it report anything out of stock or substituted, then review the cart and pay in the store's own app. He held off on giving the agent payment ability, and that is a sensible line to keep. Check the store's terms on automated access before building this.
Where the time goes back: The list and the cart assemble themselves from the group chat, so nobody retypes items into the store.
FAQ
Why keep checkout manual?
Does it need a custom browser tool?
Source and credit
Inspired by post_below on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on a self-hosted Signal agent for grocery orders
- Creator
- post_below on Hacker News
- Published on
- Hacker News
- Original date
- Feb 22, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.