Your Kid Already Has an AI Tutor. Nobody Hired It.
Recommendation feeds are teaching your kid for hours a day, with a curriculum nobody chose. What deliberate AI learning looks like instead.
July 22, 2026 · about 8 min · written to be read aloud
There is a tutor in your house right now. It works with your kid for hours every day — more hours than any teacher, coach, or grandparent gets. It is endlessly patient, superhumanly attentive, and it never takes a day off. It has one lesson plan, and the lesson is: keep watching.
You never interviewed this tutor. Nobody did. It doesn't work for you.
I want to be careful here, because this is not a talk about screens being bad. You've heard that talk. It wasn't useful, because it treated all screen time as one substance, like everything on a screen was the same gray paste. This is a talk about something more specific: the difference between a tool your kid uses and a system that uses your kid — and how to tell, from across the room, which one is happening.
Start with what a recommendation feed actually is, because it's the most successful AI product in history and the least examined at the dinner table. Every short-video app, every autoplay queue, every endless scroll is running the same loop. It shows your kid something. It measures what happens — did they linger, did they skip, did they rewatch, did they hesitate half a second before skipping. It updates its model of your kid. Then it chooses the next thing. That loop runs hundreds of times a night, and every pass makes the model of your kid slightly more accurate. It is, in the most literal sense, studying your child. There has never been anything in a child's life that studies them this closely. Not school. Not you.
And here's the sentence I'd put on the fridge: a feed is a teacher whose only measure of success is that class never ends.
That sentence explains almost everything about how feeds behave. A human teacher wants the lesson to land so your kid can leave and use it. The feed wants the opposite. It is graded — its makers are paid — on time spent, so it drifts toward whatever keeps attention, and away from anything that resolves it. Curiosity that gets satisfied is, to a feed, a bug. A kid who watches one video about volcanoes and then goes outside to build one out of baking soda is churn.
The result is a curriculum. That's the word I want you to sit with. Not "content" — curriculum. Your kid's feed has a set of topics it returns to, a sequence, an emotional temperature it maintains. It teaches taste: what's funny, what's cool, what's embarrassing. It teaches pace: how long an idea deserves before the next one arrives — currently about nineteen seconds. It teaches, above all, a posture: that the world arrives, and you receive it. Nobody designed this curriculum. It emerged, statistically, from what a billion thumbs did. Which means your kid is being taught, for hours a day, by the aggregate twitch of humanity's attention.
You wouldn't accept that from a school. You'd at least want to see the syllabus.
Now, the turn — because I promised this wasn't a doom talk, and it isn't. The same underlying technology that runs the feed can run the other direction entirely, and the difference isn't in the AI. It's in the posture of the kid.
Watch a child in front of a feed: reclined, thumb moving, eyes tracking. The machine is the actor; the kid is the surface being acted on. Now watch a kid using a chatbot to figure out why their game code crashes, or asking an image model for twelve versions of a creature they invented, or building a chatbot that talks like their grandmother's parrot. The body language flips. Forward, not back. Asking, not absorbing. The machine has stopped being the current pulling them downstream and become the oar in their hands. Same rooms, same devices, same AI underneath — opposite educations. One system is optimizing the kid. In the other, the kid is optimizing something they're making.
That distinction — being the product versus having a project — is, I'd argue, the entire modern parenting question in one line. And the encouraging thing is that kids feel the difference immediately once they've had both. The feed is candy; making things is a meal. But — and this is the honest part — nobody chooses the meal when the candy is preloaded, autoplaying, and refined by ten thousand engineers to be un-put-downable, while the meal requires setup. The playing field is not level. The feed has a head start of hours a day and some of the best-funded behavioral science on earth.
So the job isn't to lecture kids off the feed. Lectures lose to feeds every time; ask any parent who's tried. The job is to make the other posture available, normal, and social. Available: a project on the table — a chatbot to build, a robot that falls over, a comic to finish — because you can't ask a kid to leave the stream for nothing. Normal: adults nearby who make things too, even badly, especially badly. And social, maybe most of all — because the feed's deepest hook isn't the videos, it's that everyone else is watching them. A room full of kids building things resets that gravity. That's why we built Hi, Bot as a place kids go together rather than an app they use alone. Posture is contagious.
I'll leave you with the fridge test, because parents keep asking for something they can actually use on a Tuesday. Walk past your kid on a device and ask one silent question: right now, is my kid the author or the audience? Not "is it educational" — plenty of things labeled educational are just the feed in a lab coat. Author or audience. That's the whole test.
No panic if the answer is audience — the answer will often be audience; it's fine; we're all the audience sometimes. But the hours add up, and they're teaching, whether or not anyone hired the teacher.
The tutor came free with the phone. The question it was never going to ask is the one you get to ask tonight: what do you want to make?