What it is
Tell it what to watch in plain words, where, and how often: the top story on a news site, a pricing page, a status page.
A Computer opens the page in a real browser and takes a first look. From then on Lookout checks on the schedule you set. When what it reads differs from last time, the change opens with both screens side by side.
- Between checks the Computer is stopped. It starts for a check and stops after it.
- Before and after are the screens Lookout kept, not a description of them.
- Check now looks at once, and a watch can be paused and resumed.
- If a page needs a sign-in, take the controls once, sign in, and hand them back.
- Every check is kept in the watch's history with its time and its result.
In the film
One real watch, as typed: the newest story on Hacker News, every 15 minutes.
The Computer takes a first look and stops. Fifteen minutes later, with no one clicking, the scheduled check runs and finds a different story at the top. The film cuts across the wait; nothing in it is sped up.
How it was built
Lookout keeps the watches, the schedule and the comparison. It has no model key. A check is one call to Pine's agent on the watch's Computer, made by Lookout's own worker when the time comes.
turn = await computer.agent.run(goalFor(watch), {
idempotencyKey: check.runKey,
}) The agent only reads the page. Whether something changed is decided by Lookout, from the two readings it stored, and the pictures are the screens it saved with each check.
Run it
You need Node.js 22 or later and a Pine Computer project with an API key.
git clone https://github.com/PineComputer/pine-computer
cd pine-computer/examples/watch
npm install
cp .env.example .env.local
npm run dev Then rename it. Lookout is a name to replace: one file for the name, one colour for the accent, and it is yours.