← All work

On-sale alerts for premium screens

A self-hosted watcher that pushes a notification to my phone the moment IMAX 70mm or Dolby Cinema tickets go on sale at the three LA theaters I go to, with one tap to the seat map.

Status
In production · formerly imaxer
Runs
Cue
Started
Jun 2026 · renamed Oct
Stack
PythonhttpxPlaywrightFastAPISQLiteReact 19ntfyDocker
151 daysEarliest alert, ahead of opening
457Automated tests
750/hRequest budget, hard cap
3Venues, 2 formats

The Problem

The best premium-format screenings in LA sell out within minutes of going on sale, and no theater offers an alert. Refreshing ticket sites by hand is a losing game. The one metric that matters is latency from on-sale to my phone buzzing, without ever getting the watcher flagged.

How It Works

The workflow, step by step.

  1. 01

    Know what's coming

    Release calendars from IMAX and Dolby are pulled daily and merged into one row per film. The Watchlist shows them as a list or a month of posters, and I switch a film on per auditorium.

    Know what's coming
  2. 02

    Poll in tiers, politely

    Cue checks the ticket sites about every three minutes and spends most of its attention on what's soonest. Showtimes from today through the next four days are checked on every pass. Preferred showtimes that I set are checked every few passes. The rest of the next two months is covered a few days at a time, in turn. And because one film's tickets went on sale 151 days early, it also looks up to six months ahead every 30 minutes. It never sends more than 750 requests an hour, and slows to every 20 minutes overnight.

  3. 03

    Track every screening

    Each screening in a watched house is one row, keyed to theater, house, film, date and minute, never the source's ID. It is on sale, coming soon, sold out or gone, and it pushes once, plus once more if it sells out and comes back.

    Track every screening
  4. 04

    My showtimes push hardest

    My preferred showtimes are tagged with 🔥: an urgent push each, straight to the seat map, and again whenever seats come back. The rest of a drop is folded into one summary push per film and house.

    My showtimes push hardest
  5. 05

    Alerts, then the film

    The Alerts tab lists every push by day with its live status. A tap opens the film: where it's showing, the switches and the showtimes, my preferred ones marked 🔥, in one screen.

    Alerts, then the film

Built Overnight, Unattended

A brief written for an agent with no prior chat.

The first build ran while I slept. The brief set hard request budgets for the night, a stack not to re-litigate, six tasks each with a definition of done, and one rule above all: skip what's blocked, log it, move on. The session log is how I knew it worked.

docs/AUTONOMOUS_BRIEF.md → docs/SESSION_LOG.md
  1. briefYou are running unattended (the user is asleep, permissions skipped). This file + CLAUDE.md + the other docs/ are your only context: there is no prior chat.
  2. briefDon't wait for the user. If a task hard-requires a credential or a decision, skip it, log it under "Blocked / needs user", and move to the next task.
  3. briefRespect the politeness guardrails. Getting flagged kills the project. This is more important than finishing fast.
  4. briefFandango: at most ~10 requests tonight, 30 s apart, jittered. AMC: at most ~5. If you hit a waiting room, stop touching AMC. No purchases, ever.
  5. logWorked the AUTONOMOUS_BRIEF task list unattended. Live requests used tonight: Fandango 6 of ~10; AMC 5 of ~5; IMAX.com 0.
  6. logNo blocks, no challenges, no Queue-it. No purchases attempted.
  7. logT1 Fandango source confirmed ✅ … fixtures saved, so tests never need the network again.

Quoted from the repo's history; the June log has since been retired. The same pattern (brief, guardrails, open-items log) is how this site was built.

On The Phone

A real phone layout, not a shrunk desktop.

Alerts: every push, grouped by day, with live status
Alerts: every push, grouped by day, with live status
On sale: one row per film
On sale: one row per film
A film: where to watch it, and my preferred showtimes
A film: where to watch it, and my preferred showtimes
The Watchlist as a month of posters
The Watchlist as a month of posters

The Details

Where the rigor shows.

01

"Getting flagged kills the project"

Jittered intervals, conditional GETs, Retry-After honored, an hourly budget with a hard cap, a circuit breaker, and backoff persisted to disk so a reboot can't cause a hammering.

02

A trade-off, written down

Fandango's robots.txt disallows the endpoint Cue reads. I accepted that knowingly for a personal, low-volume tool, and the decision log says to revisit it before any auto-purchase.

03

At-most-once alerting

After a flapping showtime fired about 1,000 pushes in a day, alerts moved to a ledger committed only after a successful send. Failed pushes retry; nothing is lost or doubled.

04

Identity is the screening, not the ID

167 screenings were pushed twice because the source reissued every ID. A showing is now keyed to what it physically is, and a move of up to 30 minutes is the same showing.

05

Fails safe, and says so

An unreadable database or an empty calendar skips the cycle and sends one "Cue needs attention" push per outage. So does Fandango refusing every poll for 30 minutes. A silent watcher is the worst failure.

06

Guarding against a silent wrong answer

The AMC check that finds a seat link is gated to AMC venues. Run against a Regal, it would vouch for the wrong building and drop a real on-sale, and a test fails if the gate is ever removed.

07

Turning a film on never floods

Screenings already on sale when a house is switched on are settled silently, so watching a new film doesn't send fifty pushes for seats that went on sale last week.

08

Deploys that can't lose a cycle

The deploy ships a clean export of the committed tree, runs every check first, tags a rollback image and stops the poller only while it sleeps, because a kill mid-cycle loses its commits.

09

457 tests on real fixtures

421 Python and 36 web tests, captured from real responses so the suite never touches a ticketing site. They run before every commit.

Architecture

How the pieces fit.

  1. IMAX · Dolby
  2. Tiered planner
  3. Fandango
  4. SQLite showings
  5. ntfy
  6. iPhone

Three containers on my home server: the poller, the web app and a self-hosted ntfy. Settings changed in the app apply on the poller's next cycle, with no restart. Only the push wake-up ever leaves the box.

How AI Built It

The process behind the product.

  1. An overnight first build

    Briefed at bedtime with hard request budgets; by morning a working app, real fixtures, one real test push, and a list of what was blocked on me.

  2. Review rounds in parallel lanes

    Review round 2 was planned as calls on a decision page, then built as three lanes in separate git worktrees (film-first screens, the calendar, the film sheet) and merged the same day. Round 3 shipped the same day too.

  3. An orientation file that stays current

    CLAUDE.md describes Cue as it is now, section by section, and the dated log of how it got here moved to its own history file, so a fresh session reads the present, not four months of past.

  4. A rebrand in rounds

    The name imaxer was someone else's trademark, and it watches Dolby too. Logged rounds landed on Cue: a seat grid shaped like the IMAX screen, in IMAX blue.

  5. From Reflex to React

    Same lesson as Macro Meeter: the first UI round-tripped every interaction, so it was replaced with a client-first React app, and then rebuilt on the family's phone standard.

In Motion

On the phone: alerts, on sale, a film, the Watchlist as a month

More Screens