My 3-year-old doesn’t know what AI is.
He knows that mom sometimes talks to her watch, scribbles in a notebook, and that things happen because of it – a game appears on his computer, groceries show up, a recipe prints itself. He thinks this is normal. He’s right.
The strange part isn’t that I use an AI agent to handle mundane tasks so that I can have more quality time with my son. The strange part is that, for a while, the only way to talk to it looked exactly like not being present.
My phone is the command surface for half my life: messages, calendar, email, notes, photos, reminders, shopping lists, maps, drafts, all of it. It’s also the most attention-capturing object in the house. Every time I picked it up to send a one-line instruction that would save me an hour later, my son saw the same thing every child sees when a parent picks up a phone:
Mom chose the rectangle over him.
The task got done. Something else got lost.
So I started rebuilding the interface. Not because I wanted less technology, exactly – I wanted less visible extraction. The agent was never the problem. The surface was.
The phone is the wrong interface for parenting hours.
What the agent does
I run Hermes, an AI agent framework that gives me a persistent assistant I can talk to over iMessage. In practice, it handles the boring connective tissue of family life: email summaries, meal planning, homeschool tracking, draft capture, reminders, research queues, and the small logistics that otherwise pile up in my head until they turn into fog. (What that household memory should and shouldn’t hold is a question of its own .)
The default interface, though, was texting. Which meant picking up my phone. Which meant unlocking the black hole.
One quick instruction became one notification. One notification became one glance at email. One glance became ten minutes of tiny unrelated decisions. Even when I resisted that slide, the visual signal had already gone out. My son couldn’t tell the difference between “Mom is ordering groceries” and “Mom is doomscrolling instead of playing Lego.”
He saw the rectangle.
So I moved the commands somewhere else.
Fast capture: the Watch
For quick, disposable commands, I use my Apple Watch.
Raise wrist, dictate task, lower wrist. Three seconds of talking to my arm, then I’m back to the block tower, the train track, the argument about whether the Lego police car ran into the Matchbox FedEx van or if it was the other way around.
On the other end of the iMessage, Poke handles the task or adds it to my Todoist for me to tackle later. That turns the Watch into a real command surface, not just a smaller keyboard.
It’s perfect for the mental lint that otherwise sticks to me all day:
“Add printer paper to the shopping list.”
“Remind me after bedtime to make new letter tracing sheets.”
“Note that he said the red car game needs a mountain road, not a racetrack.”
None of those thoughts need to kick off a scroll session. All of them need to not be lost.
The Watch isn’t a universal interface. Dictation mangles technical terms and unusual names. It’s terrible for reviewing anything longer than a sentence. Nobody should edit a draft on a screen the size of a cracker (I tried).
But for the eighty percent of commands that are just load-bearing scraps, it’s exactly right. My son sees a raised wrist, I say a quick sentence. Then he gets me back.
Slow capture: the notebook
For anything that needs to percolate before it becomes a prompt, I use paper.
I use an inq pen that digitizes handwriting from a dot-pattern paper notebook . I write by hand, it transcribes the page, and I can send the result into the Hermes pipeline later.
This is my favorite interface, because it changes the social meaning of the act.
A parent with a phone looks absent, even when she’s doing something useful. A parent with a notebook looks like a parent with a notebook. Kids read that difference long before they can explain it.
The notebook is where I put thoughts that need a little oxygen: post ideas, observations from homeschool, weird things my son says that might become an essay later, the outline of a project, a question I want the agent to research after bedtime.
A typical version goes like this. He says something during play – maybe he’s debugging a game in toddler language: “No, the car has to jump from the mountain, not the road.” I don’t open my phone. I write the sentence down. Later, the note gets routed to Hermes, which files it under the right project or turns it into a draft seed. At night, when I’m actually in a work window, the thought is waiting for me.
The transcription isn’t really the point. The point is that I didn’t have to hold the thought in my head, and I didn’t have to disappear into a screen to save it.
A pocket notebook would do most of this. So would index cards, a kitchen whiteboard, or a paper planner. The smart pen is convenient, but the principle is older than every device in this stack: write it down somewhere that doesn’t open doors to the internet.
No capture: scheduled work
The best interface is no interface at all.
A lot of what my agent does shouldn’t require a command from me in the first place. Hermes runs scheduled tasks: checking email at intervals, monitoring mentions, building overnight summaries, reminding me about recurring household things, preparing reports while I sleep.
This is the part people underestimate. Automation isn’t just about saving the minutes spent doing a task. It removes the decision point before the task.
I don’t have to remember to check email. I don’t have to decide whether now is the moment to scan for something important. It happens on schedule, and I get a summary when something matters. The cognitive load stops existing.
This is also where the system becomes least visible to my child, which is the whole point. The cleanest command surface is the one he never sees, because it never requires me to stop playing in the first place.
The rule underneath the gear
You don’t need Hermes, an inq pen, or an Apple Watch. The principle is interface design, not gear.
Move recurring work off your hands. Whatever you check daily – email, calendar, the school portal, a delivery window – should come to you, not the other way around. Cron jobs, iOS Shortcuts, scheduled emails to yourself, a smart-speaker routine. Anything that turns “I need to remember to check this” into “it’ll show up when it matters.”
Pick a not-phone surface for live capture. The Watch and the pen work because they don’t look like scrolling. A pocket notebook does the same job. A whiteboard on the fridge does the same job. The input device your child sees you use shouldn’t be the same shape as Instagram.
Batch the phone into windows. Morning, midday, after bedtime. Between those windows, the phone is in another room. This is the rule that makes the rest possible. Without it, every “quick check” turns into ten minutes of something else.
Design for what they see. Your kid can’t tell the difference between “mom is doing something important” and “mom is scrolling.” They see the rectangle. Pick the interface that sends the message you actually want them to receive.
What my son sees
Right now, my son sees a mom who writes in notebooks, talks to her watch sometimes, and gets things done without staring at a screen.
When he’s older, I’ll show him the infrastructure – the agents, the automations, the message routing, the draft queues, all the strange machinery humming underneath ordinary family life.
For now, he sees the outcome: a parent whose attention comes back quickly. That’s the part worth shipping.
If you want a structured starting point for the screen-free part of the day, I wrote a twelve-week project curriculum at buildwithyourkid.com – hands-on building activities for ages 2-6, field-tested on a real preschooler. No coding required, screens optional. The same principle applies there too: the interface matters. Start with the world your child can touch, then let the technology support the thinking instead of swallowing the room.