Viewing as — you're seeing exactly what this user sees.
loading history…
Every request currently waiting in the queue — from all users,
so you can see what's already on the way before requesting it yourself. Who requested
what is not shown. Use Notify me to get an email or a text message the moment a
title becomes available.
loading queue…
Don't see what you want? Ask for it in Overseerr — search any movie or
show, request it, and it lands in this queue on its way to the server. Come back
here and hit Notify me to be told the moment it's ready to watch.Request a movie or show →
A request is stale when what it asked for was delivered and
later deleted from the server (e.g. by the automatic watched-content cleanup) — it will
never complete, and it blocks the title from being requested again. This is every user's
stale requests in one place, plus leftover entries with no request attached
(technically: orphaned Overseerr media records, left when a request was removed
separately). Clearing deletes only those entries from the request system — never any
media.
scanning all requests…
Selected: 0 request(s)
Titles a user removed their request for, in their own words. One only
reaches this queue when that user was the only person who asked for it — when
somebody else wants it too, it simply stops being that user's and stays on the server for
everyone else, with no decision needed from you. Delete from server removes the
title including its files (with an import exclusion, as in the Movies/Television
tabs) and clears the record that it was ever asked for; Keep it touches nothing on
the server and only takes that user off the title.
loading requests…
Experimental Films picked from what
you've already watched, through the same TMDB catalogue Overseerr uses — not a search,
just a starting point. Pick a poster to request it under your own account, exactly like
everywhere else in this app.
working out what you'd like…
Experimental Shows picked from what
you've already finished, through the same TMDB catalogue Overseerr uses. Pick a poster to
open its season picker and request it under your own account.
working out what you'd like…
Every film on the server with its Rotten Tomatoes scores, read from Plex.
The Watched column is your account's.
reading the library…
Every show on the server with its Rotten Tomatoes scores, read from Plex.
The Watched column is your account's. A show counts as watched once every episode is.
reading the library…
Free space on each disk that holds the library, forecast a month ahead.
It counts what Leaving Soon will delete on which day (and the 4K copy it takes
with it), what the download queue is still bringing in, and the disk's own
drift: the usual day-to-day change from everything else, measured from one
reading a day. Until a disk has a week of readings, drift is left out and the
forecast says so.
reading the disks…
What the nightly cleanups are about to take off the server. Nothing on
this tab deletes anything — it is a forecast. A title is first marked
(a Radarr tag for a movie, a Plex label on each episode for a season), and once it has
sat out its hold this app deletes it itself, from both instances.
Every projected date assumes nobody watches the title again: one play restarts a
grace or expiry clock, and for a warned season it calls the removal off entirely.
The one thing you can do from here is Keep a title, which calls its removal off
for good, at any stage.
working out what is due…
Two nightly jobs do all of this (why two?)
Movies · 02:00
Television · 03:00
Every stream Tautulli reported buffering — its Buffer Warning fires when
a stream stalls more times than the threshold you set in Tautulli → Settings → General,
and Tautulli posts it here. Tautulli keeps no buffering history of its own, so this only
holds what has arrived since the webhook was set up. Click a row for everything Tautulli sent,
to read what the user said about it, or to ask them.
loading events…
Everything Radarr and Sonarr are actively fetching, folded onto one
row per download — a season pack is one row, not one per episode. Cancelling takes a
download off the download client, off the arr, and deletes any Overseerr request(s) for
it — no import exclusion is added, so it can be requested again.
checking Radarr/Sonarr…
Stuck
Selected: 0 download(s)
Everything playing on the server right now — who, what, on which
device, whether the server is sending the file as-is or re-encoding it, and what that
costs in bandwidth. Refreshes every few seconds while this tab is open and stops when
it isn't. A stream that has already stuttered in the last hour is flagged, so a
buffering complaint can be matched to the device causing it while you can still go
and look at it.
asking Tautulli…
What each FTP account on the NAS has done, newest first: logins,
downloads, uploads, and failed logins against accounts that exist. The bots guessing at
made-up names are counted in the box below rather than listed. Each account is named for
the person it's linked to in
Settings → FTP. Times are the NAS's own clock. Downloads also reach your phone,
through the FTP server switch under Notifications.
reading…
Everything this app has done on someone's behalf — every deletion,
automatic cleanup, playback survey, account link and settings change, with who did it
and when. Written as it happens and never edited or trimmed, so this is the record if
you need to answer "what happened to that title?". Click a row for exactly what was
written.
reading the log…
Every push notification this app has raised — sent, muted, or
not delivered — so an alert you saw on your phone (or think you might have missed)
can still be found here and acted on. A row with a Keep button still works days
later; it checks the current state rather than trusting what the alert said at the
time.
reading the log…
Bulk transfers Plex's own bandwidth accounting saw with no
matching play behind them at all — the closest thing to a download log this stack
has, since a client that copies a file straight to disk never opens a play session
and so never reaches Tautulli or anything else here.
What counts as one, exactly? reading Plex's bandwidth log…
loading movies…
Selected: 0 item(s) · 0 GB
Every movie on the server, biggest first — not just the ones this
user is on. Sizes add up both instances: a title kept in 1080p and 4K costs the
two together, and only the total is worth acting on.
Deleting here removes the files for everyone, on both
instances, and clears the request record.
reading the library…
0 selected
Who each movie is attributed to, and whether anything is
watching over it. Both cleanups key off attribution — a
requester tag, which Overseerr writes only when it creates a title, or an
Overseerr request naming it. Anything added another way carries neither and
sits outside both flows until somebody claims it below.
classifying the library…
Get an email or a text message the moment a movie arrives in the
library — one you requested yourself, or one somebody else already requested.
loading your movie alerts…
loading series…
Selected: 0 item(s) · 0 GB
Every show on the server, biggest first — not just the ones this
user is on. Sizes add up both instances: a title kept in 1080p and 4K costs the
two together, and only the total is worth acting on.
Expand a show to see its seasons and delete them one at a time.
Deleting here removes the files for everyone, on both
instances, and clears the request record.
reading the library…
0 selected
Who each series is attributed to, and whether anything is
watching over it. Both cleanups key off attribution — a
requester tag, which Overseerr writes only when it creates a title, or an
Overseerr request naming it. Anything added another way carries neither and
sits outside both flows until somebody claims it below.
classifying the library…
Subscribe to a show and get an email or a text message every time
new episodes arrive — for shows you requested yourself, or ones somebody else already
requested.
loading your series alerts…
Newsletter for
A personal email digest with poster art and metadata: requests that just
arrived, titles that are ready and still unwatched, what's still on the way, a watch
recap, and what's new on the server. Pick how often it arrives and what's inside.
Mailings are not configured
on the server (SMTP2GO_API_KEY / DIGEST_FROM_EMAIL) — settings can be saved, but nothing
will be sent until the admin sets them.
What's includedDrag, or use the arrows, to set the order they appear in.
Admin: send this user's issue to a different address for checking the layout —
Deletion warnings for
A short email, three days ahead by default, when something you asked for is
about to leave the server unwatched — why, the date it's due, and a button to give it more
days (a couple of times per title). Watching it doesn't
hold it (finishing it is what releases the server's claim on it); starting it does, and
so does this button.
Mailings are not configured
on the server (SMTP2GO_API_KEY / DIGEST_FROM_EMAIL) — settings can be saved, but nothing
will be sent until the admin sets them.
Admin: send this user's due warnings to a different address for checking the layout —
Newsletter engagement
Whether anybody reads it. An open is the invisible image at the
foot of an issue being fetched; a click is a link in an issue being followed.
Opens are the weaker signal — some mail clients fetch every image the moment mail
arrives — so the open rate only counts issues with an open that doesn't look automatic.
reading engagement…
Specials
One-off themed mailings — Halloween, Christmas, whatever the occasion —
that go out once, to everyone who has the newsletter on. They are drafted by your
assistant over MCP (special_candidates, then draft_special; or use its
holiday_mailer prompt) and nothing is mailed until you press Send here.
loading…
A year in review is different: nobody drafts it. Each reader's copy is
drawn from their own year — hours watched, most-watched shows and films, what they asked
for — when it is sent.
All users (admin)
Opt users in or out, set their address and frequency, and send tests.
Addresses are prefilled from Overseerr where available. Section choices for a user are
managed by picking them in the User selector above.
loading the subscriber overview…
My Seerr for
Have your own Seerr, Overseerr or Jellyseerr instance?
Add its web address to get a View on my Seerr link on newsletter title pages.
Sign in there to view information or request a title for your own server.
Use an http:// or https:// address reachable
from your device. A reverse-proxy base path is supported. No API key, username
or password is needed; this app never contacts your instance or submits requests.
Saved addresses apply to newly generated emails. Existing links
keep the address they were sent with, and forwarded links include that address.
Clear it below to leave it out of future emails. This does not change LETHE's
server-wide Seerr connection.
Some people request through an Overseerr account that has no Plex
login of its own, then watch what arrives on somebody else's Plex account. This app
can't see them: their requests belong to nobody, and the post-watch cleanup, finding
no watch history against their name, treats a movie they watched as one nobody
touched. Linking their Overseerr account to the Plex account they actually watch on
fixes both — and gives them a newsletter of their own.
Once linked, the two of them are a household: both newsletters
carry both people's requests, each one saying who asked for it, and the cleanup
counts a play on the shared account for whoever requested the title. What Plex
cannot do is say which of them pressed play — it logs plays per account —
so the viewing figures are named for the account rather than the person.
Downloads from the FTP server on the QNAP. Each one is pushed to you —
a burst becomes one alert when the account logs out — through the
FTP server switch under Notifications. An FTP account is a login on the NAS, not
anybody's Plex account, so linking one to a person here is what lets the alert say who
it was.
Push notifications
Pushover alerts to you, the server owner. Pick which of the things
that happen in this app are worth a ping — everything else stays in the app and in
the deletion log. Nobody but you receives these.
Also alert me about my own actionsOn, every event below fires whichever of us set it off. Off,
you only hear about what other users do — the app stops echoing your own
clicks back at you. Scheduled and automatic events always come through.
Where this app finds everything it talks to,
and how it names itself. Saved here, these override the matching values in
.env and take effect immediately — no restart. Clearing a service's URL and
key switches that integration off and hides its tab. API keys are stored on the server
and never sent back to this page.
What this app does on
its own once the services are connected: the nightly cleanups, the deletion warnings,
playback surveys and the welcome email. Each is off, or deletes nothing, until you say
otherwise. Saved here, these override .env and apply immediately.
Who may connect an assistant to this server, and what every tool
one can call actually does. Access is handed out an account at a time: switch somebody
on and the Assistant access panel appears in their settings, switch them off and every
token and connection they hold stops working the same moment.
The tool list below is a reference, not a switch — what a connection
may do is still all-or-nothing per scope, until a real per-tool permissions model
replaces it.
This is where you let Claude — or any other assistant that speaks
MCP — ask this app questions on your behalf: what you have watched, what you are still
waiting on, what is about to come off the server, and whether it can request something
new for you. Nothing here changes what the app itself does; it only decides what can
reach it while you are not looking at it.
On a phone, nothing needs pasting. Claude reaches this app
from its own servers, so you add this app as a custom connector and approve it on a
page much like this one; approved connections are listed below and disconnect in one
click. On a laptop, where the assistant runs on your own machine, it needs a
token instead — a long secret that goes in a config file.
Either way, it is only ever yours. It sees your history and
your requests and nobody else's, it can never do anything an admin can — not even if
you are the admin — and it cannot delete a single thing. The most a leaked one can do
is read your own viewing and ask Overseerr for a film. A token is shown to you
once, when you make it: nothing here can look it up again, so if you lose it,
revoke it and make another.
Recommendations for
The For you pages (under Movies and TV) and the newsletter's "Recommended for you" section
pick titles from watch history through the same TMDB catalogue Overseerr uses. This
switch is the only thing standing between this account and a title TMDB has
flagged as adult — off by default for everyone, and off means it's actively filtered
out, not just left unrequested. Checking it doesn't make the engine go looking for
adult titles either — it only stops discarding one that a watched title's own
recommendations happen to include.
Separately, keep mainstream titles above a certain movie or TV rating
out of recommendations — this is TMDB/MPAA certifications (PG-13, R, NC-17, TV-14,
TV-MA), not the adult flag above. Nothing is blocked here by default.
Hidden titles
Titles waved away with Not interested on a Discover tile. They
stay out of the For you pages and the newsletter until shown again here.
History retention for
Keep only a recent window of usage traces. Every night around 3:00 AM,
anything older than the window is purged — play records from the history log
(Tautulli), watched flags on the Plex server, and request attributions (the tags
linking library movies/shows to this user, by the date they were added). Recent
activity inside the window is untouched, and no media files are ever removed. Leave
it off and all usage data stays intact.