How to use Claude to build YouTube video approvals
A non-developer used Claude to build a local YouTube approval system with Telegram decisions, DNS restrictions, child profiles, and viewing budgets, reviewing releases through Claude.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a self-hosted video approval app for [household]. Use yt-dlp for search and metadata, Telegram for parent decisions, and approved youtube-nocookie.com embeds for playback. Add [profiles and budgets], document DNS setup, and review code and security before release.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- hax0rsJJ
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports building and sharing a self-hosted system with Telegram approvals, embedded playback, channel allowlisting, child profiles, and category time budgets.
- Human involvement
- The author defined features and reports Claude reviews before every release; the post does not describe independent review.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The author described the desired video approval features to Claude.
- Claude wrote the application code from those feature descriptions.
- Each release underwent security and code reviews via Claude before being pushed.
The author built a self-hosted video approval system after finding that regular YouTube recommendations quickly distracted their preteen from educational content. They describe themselves as a non-developer who supplied feature descriptions while Claude wrote the code. Every release then went through security and code reviews via Claude before being pushed.
The application gives the child a web page for searching and requesting videos. Requests send the parent a Telegram message containing the thumbnail, title, channel, and duration. The parent chooses Approve or Deny, and approved videos play automatically on the tablet.
The access arrangement blocks youtube.com at DNS while allowing youtube-nocookie.com embeds. The author explains that suggested-video links lead back to the blocked domain. Search and metadata use yt-dlp without a YouTube API key. Other reported features include channel allowlisting, separate child profiles with PINs and watch histories, and daily time budgets by category.
The project runs on a Docker machine on the local network, and the author shares its GitHub repository. These are the author's feature and release-process claims; the post does not report independent security testing.
Who it's for: Parents with self-hosting experience who want explicit control over requested videos and viewing budgets.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · hax0rsJJ
Frequently asked questions
How does a parent approve a requested video?
A Telegram message includes the video's thumbnail, title, channel, and duration. The parent taps Approve or Deny; approved videos play automatically on the tablet.
What reviews were performed before releases?
The author says every release went through security and code reviews via Claude before pushing. Independent security testing is not described.
More details
Remaining steps
- The author shared the project repository for other parents.
About this account
Claude wrote the code from human feature descriptions and also performed the reported release security and code reviews.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47165617. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: hax0rsJJ on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude · Telegram · yt-dlp · Docker · DNS filtering
Parental controls · Self-hosting · Video approvals
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.