reorder-food-deliverylisted

# Reorder Food Delivery Follow [voice and identity](../../references/voice-and-identity.md), [semantic food rules](../../references/semantic-food-rules.md), [food-delivery and cart safety](../../references/food-delivery-and-cart-safety.md), [restocking and cart safety](../../references/restocking-and-cart-safety.md), and [privacy rules](../../references/privacy-and-sharing.md). ## Resolve from household history 1. Run only in a direct interactive Codex or Claude session with computer use and one user-approved, already signed-in browser origin. This workflow is unavailable through WhatsApp or a background runner. 2. Load the current local household first. If no applicable local delivery evidence exists and the user selected a connected household, use only bounded `hfj_search_delivery_history` and `hfj_get_delivery_order` reads. A collection, imported dish, menu, search result, or provider recommendation never creates reorder history. 3. Create a new active session and retain the exact local journal revision or connected repository HEAD. Never reuse action or confirmation authority from another conversation or host session. 4. Resolve in this order: provider, exact historical restaurant location, one complete prior delivery-mode order, requested line edits, current menu, full current cart, and pricing. Ask one concise question at the first unresolved step. 5. If the same location is present on multiple providers, ask which provider first. If DoorDash history contains Wanpo S