amazon-fresh-shopping

Amazon Fresh Shopping

Use fresh as the sole execution layer. Let the agent make shopping decisions; keep authentication, cart mutations, checkout, and orders inside the CLI. Commands emit one JSON value to stdout and errors to stderr.

Safety rules

• Never request or accept Amazon passwords, MFA codes, cookies, CSRF tokens, HAR secrets, or raw authenticated HTML. Use fresh auth login or fresh auth refresh.
• Treat search, cart edits, address selection, slot selection, substitutions, and tip changes as reversible.
• Treat order placement and cancellation as irreversible actions requiring fresh, explicit user confirmation.
• Never infer PLACE ORDER or CANCEL ORDER from vague approval such as “looks good,” “try it,” or “go ahead.”
• Before requesting PLACE ORDER, show item count, masked address and payment method, delivery window, every checkout line, tip, exact total, and maximum total.
• Bind the preview maximum to the exact total unless the user explicitly chooses a higher ceiling.
• Never reuse an expired preview token or place after any cart, address, slot, payment, tip, substitution, or price change. Preview again.
• Never retry an ambiguous placement or cancellation. Inspect orders and cart state; report the outcome as unknown until an order ID or user-visible confirmation exists.
• Never claim success from an empty cart alone.

Authenticate

Run:

fresh auth status

If unauthenticated, use fresh auth refresh. If refresh cannot recover the session, use fresh auth login and let the user complete Amazon's device-code flow. Never automate credential entry.

Build a cart

1. Read the existing cart with fresh cart list before changing it.
2. Search with fresh search --limit 10 "QUERY".
3. Compare title, size, price, unit price, availability, promotion, and cart quantity. Avoid out-of-stock results and misleading pack sizes.
4. Add the selected result using its exact returned ASIN, price, and URL:

fresh cart add ASIN --expected-price PRICE --source-url 'SEARCH_RESULT_URL'