Build a safe Minecraft library in Watchly in ten minutes

What a Minecraft-only library looks like in Watchly

The Watchly home screen for a kid is a library, not a feed. You add channels; the library is the union of those channels' uploads. There is no sidebar recommending content from outside the library, no autoplay into 'similar' channels, no search of YouTube at large from inside the kid's profile. Whatever the kid sees on their screen, you put there. That is the entire structural promise.

For a Minecraft-only library this matters more than it might sound. The Minecraft tag on YouTube is the most-trafficked kid-search topic on the platform, which means it is also the most algorithmically gamed. A 'Minecraft kids' feed on regular YouTube pulls from a sea of channels that range from genuinely calm to engagement-engineered to be sticky for the wrong reasons. The closed-library model takes that whole sea off the table. The library is the universe, and you defined the universe.

Inside the library, autoplay works the way you actually want autoplay to work, one approved channel's video into the same channel's next video, library video into library video. The Saturday-morning use case of 'put on a channel and let it run' is fine and supported. What's not supported is the regular-YouTube autoplay behavior where the next video is whatever the algorithm picked from the whole platform. That structural distinction is what makes the library safe to leave running.

The per-profile structure adds another layer. Each kid has their own profile with its own library. A five-year-old and a nine-year-old in the same family have different Minecraft libraries, different channels, different age-band content, different filter thresholds. The PIN keeps each kid in their own profile. When the older kid wants something the younger kid shouldn't see, the older kid logs into their profile and the content lives there. The younger kid's library is unchanged.

The AI transcript filter sits on top of the closed-library model and handles the per-upload work. Every new video from every channel in every library gets scanned against your family's rules. Profanity, slurs, scary content, jumpscare patterns, sponsor-heavy structures, and a handful of others. The scan is per-upload, so channel drift doesn't matter, the channel doesn't need to be re-vetted by you. The filter does the per-video check on every upload, continuously.

What you actually do, week to week, is much less than parents expect. The initial setup takes ten minutes. After that, the maintenance is mostly approving or rejecting the occasional flagged upload (maybe one or two a week, depending on library size) and adding the occasional new channel your kid asks for. The day-to-day 'standing in the doorway watching what the iPad serves' work goes away.

The setup walkthrough at narrative level

Sign up. Free trial. You land on the parent dashboard. First action: create a profile for the kid who wants Minecraft. Name, emoji avatar (the kid picks this part if they're around), birth year, four-digit PIN. The birth year sets the default filter strictness; a five-year-old's profile starts stricter than a ten-year-old's. You can tune from there.

Second action: add a Minecraft library. The fastest path is to import the predefined Minecraft library, it includes channels matching the calm-pace patterns by age band, pre-screened against the family-friendly criteria from earlier pages in this guide. The import is one tap. You can then edit it down to just the channels you want, or leave the full set as the starting point and remove channels over the next week based on what the kid actually watches.

Third action: add any channels the kid specifically asks for that aren't in the predefined library. Search by channel name, the search returns the channel with a thumbnail and recent uploads, you tap add. Each addition takes about ten seconds. We'd suggest pre-screening the most recent few uploads from each channel before adding, current uploads tell you more about a channel's tone than its reputation does.

Fourth action: set a time cap and a schedule. Daily limit, per-session limit, allowed hours. The cap is enforced by Watchly itself, when time's up, the player closes, the kid sees a friendly 'see you tomorrow' screen, and you don't have to be the one ending the session. Most parents start with twenty to thirty minutes for the youngest kids and adjust from there. The schedule lets you block, for instance, the hour before bedtime.

Optional fifth action: turn on the watch-history monitoring features in the dashboard. You'll get a weekly digest of what the kid actually watched, grouped by channel, with any flagged uploads called out. The digest is useful for spotting drift over weeks, if one channel in the library has been hitting flags more often than it used to, that's the signal to trim or remove.

That's the setup. Ten minutes of focused work, and you have a Minecraft library that your kid can use on Saturday mornings without standing in the doorway. The closed-library structure does the structural work; the AI filter does the per-upload work; the watch-history dashboard gives you the data to tune the library over time. The day-to-day vigilance work mostly stops being your job.

What happens after the setup

Once the library is running, the maintenance is light. The AI filter scans every new upload from every channel and flags anything that hits your rules. You'll see one or two flags a week in a moderately-sized library, usually a sponsor-heavy upload, an off-tone collab episode, or an audio slip. You approve, deny, or block from the dashboard in two taps. That's almost all the ongoing work.

Channel drift is the case the AI catches that you'd otherwise miss. A channel you trusted six months ago starts hitting flags more often. The watch-history dashboard groups flagged uploads by channel, so you can see the pattern, three flags in a week from one channel is signal. You decide whether to keep, demote, or remove. The data makes the call possible; the call is yours.

Your kid asks for new channels. The Watchly request feature lets them mark channels they want; the requests show up in your dashboard. You either pre-screen and approve or deny. This routes discovery through you instead of through autoplay, which is the structural shift the whole product is built around. The kid still gets to ask. The platform doesn't get to pick.

Over weeks, the library settles. The channels the kid actually watches stay; the ones they bounce off get removed. The filter catches drift continuously. The watch-history dashboard shows you what stuck. And the Friday-night 'put it on the iPad and walk away' use case becomes something you can actually do, because the library is bounded, the autoplay is bounded, and the AI is watching the per-upload behavior so you don't have to.