Set a flight-price alert with limits
Design a fare watch that checks the itinerary I actually need.
Track a needed item without creating a stream of unnecessary shopping suggestions.
Optional settings update the preview and copied task. Nothing entered here is saved or sent to our server. Do not enter passwords or account numbers.
TASK SETTINGS — fill only what is relevant Scope: [selected accounts, records, or task] Budget: [amount and currency, or no new spending] Deadline: [date, time, and timezone] Tone: [polite and concise] Contact channel: [no contact until approved] Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything. Track a needed item without creating a stream of unnecessary shopping suggestions. Use only the accounts and materials I authorize. Start with: the exact model and variant, credible sellers, condition, total-price target, deadline and maximum check frequency. Verify the current baseline and distinguish a genuine discount from a changed pack size, variant, membership offer or missing fee. Prefer an official price alert where possible. Specify when to notify, when to suppress duplicate alerts and when the watch should stop. Include stock and delivery timing in the qualifying condition. Work read-only and prepare drafts first. Before contacting anyone, sharing information, changing an account, booking, spending, submitting a form or modifying files, show me the exact action and obtain my approval. Do not buy, subscribe to a paid deal service, bypass rate limits or expand the product list. Verify that your tools actually support the requested work. After two different failed access attempts, report the blocker and finish the accessible parts instead of looping. Never invent an action, source, availability or confirmation. Return: a monitor specification, current comparable offers, source coverage and approval needed to schedule it. Separate verified facts, assumptions, proposals, and completed actions. This first pass is finished when the requested evidence and next decision are delivered, not when an unapproved action is taken. For ongoing checks, propose a cadence, timezone, trigger, end date and any cost. Do not claim monitoring is active until I approve and you return the actual task ID and next run. Respect service rules and rate limits; do not bypass anti-bot controls. Keep a manual backup for critical deadlines. Standing-brief setup: First perform one read-only baseline check. Then propose the exact schedule, timezone, end/review date, trigger, cost limit, and notification destination for my approval. Create a recurring task only after approval and only with a real scheduler. Return the actual task ID, next run, and pause/stop instructions; otherwise say it is not scheduled. On subsequent runs, compare with the last successful checkpoint, deduplicate alerts, retain only necessary state, and report failures or stale access rather than treating them as no change. Respect service rules and rate limits. No external actions are authorized by a scheduled check.
Give your agent only the relevant records. Review the proposed action and require confirmation of what actually happened.
A different job for another time.
Design a fare watch that checks the itinerary I actually need.
Build a renewal watch from verified dates, not guesses from old receipts.
Notify me when a particular conversation reaches a meaningful decision point.