Page watch

Let me know when the price on this page changes

The agent checks a page on a schedule and writes to you only when what you're watching has changed: a price, availability, a new job opening, a new listing. The rest of the time it stays silent.

How to set it up

Tell the builder which page to watch and what to watch on it:

Watch https://shop.example/teapot — let me know when it gets cheaper

The builder will:

1. create a watcher agent (if there isn't one yet — one watcher can watch any number of pages);
2. set a schedule for this page — every hour by default;
3. run the first check right away and tell you what the agent sees on the page. If what you're watching isn't visible there, it will say so plainly — then there's nothing to watch;
4. tell you where the message will arrive.

Another page — the same sentence with a different address: the same agent, its own schedule.

How much it costs

A check where nothing changed stays silent and costs no credits: the agent compares the page text with what it saw last time and doesn't call the model at all. You pay only when something on the page has changed — then the model reads what exactly and decides whether it's what you're watching.

So frequency isn't about paying for checks, but about two other things:

• more often — you find out sooner: every hour means you'll learn about a change within an hour;
• more often — noise wakes the model more often: if the page changes by itself (ads, "12 people viewing now"), each such change is one call to the model, even though it won't write anything to you.

The exception is pages built by scripts (see below): they're read by a real browser, and each check costs a few seconds of browser work — at the sandbox rate.

Where the message arrives

The same place as the result of any schedule: your linked chat with the agent in Telegram, and if there isn't one — as a notification (Telegram support, email). If there's neither, the builder will say there's nowhere for messages to go and suggest what to connect.

Noise

A page changes not only when the price does. So:

• clocks and "updated 5 min ago" never count as a change;
• counters and ads — name them in words: "ignore views and reviews" — and lines with those words won't count;
• a part of the page can be named with a CSS selector — "watch only the .price block" — if you or your developer know it. The builder itself doesn't see the page markup and doesn't guess selectors;
• even when a change gets through all of this, the agent won't write to you if it isn't about what you're watching.

Dates deliberately don't count as noise: "in stock from 12.10" is exactly the change people come for.

Pages built by scripts

Many modern pages return an empty shell and draw the price in with scripts. If a simple request doesn't see text on the page, the agent opens it with a real browser by itself — nothing to turn on.

When a page won't open

Not silence. If a page fails to open three checks in a row (the site is down, the address changed), you'll get a problem "Page … can't be read — watching it has stopped". As soon as the page can be read again, the problem closes by itself.

If the site forbids automated reading (the robots.txt file), the problem arrives right away: repeating won't change it, and the agent won't bypass the restriction.

What to say

Say	And it
"watch … — let me know when the price changes"	sets up the watch and shows the first check
"check every 15 minutes"	changes this page's schedule
"ignore the view count"	stops counting those lines
"stop watching …"	removes this page's schedule
"what's there now?" (in the chat with the agent)	opens the page and tells you
"show me what it would do now"	runs a rehearsal: reads the page and tells you what would be sent to you — first reading, a change or "no changes". Memory doesn't move, failures aren't counted, the browser doesn't open (it only says it would open it)

What isn't there

• Logging in to a site. The agent can't see pages behind a login.
• A "before — after" screenshot. The message is text: what was, what is now, and the address.
• Watching hundreds of pages with one schedule. Each page has its own schedule.
• Unlimited memory. The agent keeps what it saw last time in its memory — 64 KiB per agent together with everything else. To show "before → after" word for word, up to 4,000 characters go to one page. When there are many pages or they're long, the agent remembers fewer words: it will still show what's new in words, and about what disappeared it will say "and N more lines" without inventing what was there. If there's no room even for that, it will say the page changed and give an excerpt. Watching a block of the page instead of the whole page is the best cure for this too. When watching a page is removed (or its address is changed), its record disappears from memory along with it; if another schedule watches the same page, the record stays.