The most capable computer in most homes sits in a study, logged into one person’s accounts, running one person’s tools. Everyone else in the house asks that person for help. A family agent is the coding agent on that computer, given a room the household can message, so the asking goes to the machine instead.
Nothing about this is exotic. Claude Code and Codex are excellent at the kind of tedious file work a family accumulates, and a room gives them an address a partner can reach from a phone.
Five chores, five requests
“Convert the videos in Downloads to MP4 for the TV.” The agent finds the files, runs the converter installed on the machine, reports progress per file, and posts a summary. Nothing pauses, because nothing is deleted or pushed.
“Rename the photos from the trip by date and put them in one folder.” The agent reads the metadata, proposes a naming scheme, applies it and posts the count. If it wants to delete duplicates, that pauses for the owner.
“Turn this spreadsheet into a chart for my project.” A teenager attaches the file from their phone. The agent produces a chart image and a one-paragraph reading of it. The image appears in the room.
“Draft a letter to the landlord about the boiler.” A draft in the room, in plain language, ready to copy.
“Which of these forms still need signing?” Photos of paper forms, an answer in the room.
What the household sees
They open the room on a phone, mention the agent and write the request, with photos or files attached. The timeline shows the agent working, in language a non-technical person can follow: “converting 4 of 11”, “renamed 312 files”. The result lands in the same place.
They never see the owner’s terminal, files or accounts. The daemon uploads timeline events, not the disk. See what the daemon uploads.
What pauses
Household requests rarely hit the four dangerous action types, but two come up: deleting (duplicates, originals after conversion) and spending (a paid API for transcription, say). Both stop for the owner with a card on their phone. A partner asking to “clean up the photos” gets the renaming immediately and the owner decides about the deletion.
Setting it up
- One agent for the shared folders. Pin it to a directory like
~/Familyand keep documents, photos and downloads under it. The agent cannot reach outside its working directory. - A second agent for your own work, in its own room. The family never sees it.
- Permission mode
acceptEditsfor the family agent: renaming and converting run without prompts, commands still ask. See permission modes explained. - Standing grants for the household. One approval each, then they ask freely.
- Install the daemon as a service and disable sleep during the day. Requests queue otherwise, which is fine, but a chore that runs at 9 pm instead of 9 am is a worse chore.
Why not just teach them the terminal
Because they don’t want it and shouldn’t need it. A room turns the request into a message, the progress into a readable timeline, and the risky step into a question for the person who owns the machine. That is the whole product, and a household is a fine first team.
Frequently asked questions
Do family members need their own subscription? No. The agent runs on the owner’s subscription. They need a browser.
Can the agent open files outside the family folder? No. It is pinned to its working directory. Give it a different folder if you want it to see more.
Is this safe for a teenager to use? The four actions pause for the owner, and read-only mode exists for exploring. A teenager can ask anything and change nothing until you say so.
Give the computer in the study a room. Start here.
Published