← Dashboard · private report · design only — nothing built or changed yet
Mom God-mode Setup
One plan: Mom's own assistant she just talks to, with you running it for her from anywhere — built in person next Saturday · as of Mon May 18
The bottom line, straight:
- The machine is yours — your Windows PC that Mom uses as her main computer. Newish, late 2025, lower-power. Everything here is added on top of it and fully removable; nothing she already does changes.
- She gets her own free Claude, signed in with the family email she already uses for everything. You're the admin of that whole email domain, so you control it at the root the same way you control your own stuff. Free is the start; paid (about twenty a month) only buys higher usage limits later, not control.
- What Mom sees is the friendly Claude app — a chat she talks to, sitting in a side panel. Never a black command screen.
- Behind that app is "Apex Junior" — the exact phone-home trick that already runs your Apex server, copied onto this PC. It hands you a session link you open from your phone to run things for her. It survives reboots on its own. No open doors on the PC. Mom always sees it's there and can stop it; she is never locked out.
- You co-drive from a phone link. If you want eyes on her actual screen, that rides over the same private network you already use for Apex.
- Her old iPhone joins that private network too — phone, PC, and Claude all on one mesh, so they talk to each other and you can reach all of it.
Everything you asked for is doable as you pictured it: open up the computer for Mom,
have her work it herself by talking, and have you able to run it for her from anywhere.
This single plan replaces the two earlier half-drafts (the account/voice one and the
remote-control one) and locks every open decision so there's nothing left to relitigate.
What still needs answering
Almost everything here is something Claude sets up. Only two things are still open,
and both come from a short sit-down with Mom — not a chore list for you:
- The PC's basic specs — what processor and how much memory it has, and
whether she leaves it on and online. (Decides nothing major; the heavy work runs on
Anthropic's side, but it confirms the light setup is the right call and tells us if the
machine stays reachable.)
- The brain-dump with Mom — twenty minutes of her telling us, in her
words, what she actually wants out of this. That shapes how the assistant greets her and
what it helps with on day one. Prompts for that are right below.
The brain-dump with Mom — what to ask
Loose questions, her talking freely, you just listening. Not a survey — the goal is to
hear what she'd actually use, in her own words.
- What do you do on the computer most days? Walk me through a normal sitting at it.
- What's annoying or slow about it? What makes you give up on something?
- What do you wish it could just do for you if you could ask out loud?
- When you want to look something up, write to someone, or remember something —
how do you do that now?
- How's the hearing and the eyes lately? (She runs the TV loud — worth knowing whether
spoken replies need to be louder, slower, or backed up by big on-screen text.)
- Do you leave the computer on, or shut it down each night? Is it usually on the
internet?
- Anything you've wanted to try on it but it felt like too much hassle?
These get asked in conversation. The answers tune the assistant's voice
and its starting abilities — they don't gate the build.
How Mom uses it, day to day
She opens the Claude desktop app — a clean side-panel chat. She types
or talks; it answers and, when she asks, it does things for her. It's forgiving: she can
ramble, change her mind, start over — that's normal for it, and starting a fresh chat is
always one click away. Nothing she does in it can break the computer.
Because it's signed into her own family email identity, it's genuinely hers — her
history, her space, separate from your accounts and your twin work. Later it can be
connected to her own mail and calendar so it actually does things for her, all inside
her own boundary, never crossing into yours.
The app is the friendly face. The engine that lets it actually do things on
the PC — and lets you reach in — is the "Apex Junior" layer below. Mom never has to see
or touch that part.
"Apex Junior" — the engine you already trust
This is the part you actually care about: how Claude operates the machine so Mom talks
and Claude does, and how you co-drive. It is the exact mechanism that runs your
Apex server today, copied onto this PC — not something new and untested.
It's a small task set to start when the PC logs in. It phones outward on its own and
hands back a session link. You open that link from your phone or laptop and you're in
the same working session — that's the co-drive, one shared link, not a second connection
fighting hers. It's scoped to one dedicated working folder, not her whole computer. It
narrates what it's doing and shows a small status note, so it's always visible; closing
the window or signing out stops it instantly. Nothing destructive ever runs on its own.
Why this is the lowest-risk path: no open ports,
nothing exposed inbound, and it self-heals after any reboot — Windows update, power blip
— the moment the PC logs back in, with no action from Mom and none from you. It is the
Windows twin of the same logon-task pattern that keeps your Apex services alive. The
heavy compute is on Anthropic's side, so a lower-power PC just runs a thin layer — light
on the machine.
Eyes on her real screen (when you want them)
Separate from the Claude engine: for the times you the person want to watch
or touch her actual screen, her PC joins your private network (the same reach you already
use for Apex) and a screen-share rides over it. Announced, never silent — a visible
"connected" indicator she can see and end at any time. She keeps the keyboard the whole
time; it shares the screen, it never evicts her from it.
| Tool | Free for this? | You own it? | Locks Mom out? | Verdict |
| Self-hosted screen-share over the private network | Yes — free, open source | Yes, fully — your own relay | No — shares the screen, she keeps the keyboard | Primary. Free, yours, never evicts her, same trust boundary as Apex |
| Chrome Remote Desktop | Yes — free, no license trap | No (Google's relay), but an identity the family already uses | No | No-setup backup. Two clicks, nothing to buy — best if the primary is fiddly to stand up remotely |
| AnyDesk | No — paid for family help; free tier flags it as commercial | No — their cloud | No | Beaten on every column; rejected |
| Plain Windows network login | Yes | Network yes | Yes — kicks her off her own screen | Rejected for this machine. Fine for the headless Apex box only |
| TeamViewer | Effectively no — aggressive "commercial use" flagging, then a big yearly bill | No | No | License-lockout risk disqualifies it |
| Game-streaming tools | Some free | Some yes | No | Wrong tool — built for low-latency gaming on a GPU box, not this |
The in-person plug-and-go — Saturday May 23
The whole build happens in person next Saturday. On the day, the only hands-on steps
are tiny and all on the PC and her phone — everything else Claude does remotely afterward
once the machine is on the network.
- One "Continue with Google" click on the PC to stand up her free Claude on the family
email she already uses.
- Install the private-network app on the PC and join it to your network.
- Install the same private-network app on her old iPhone (whatever version that phone
supports) and join it too.
- Install the Claude desktop app on the PC and sign it into her account.
That's it for the day. Four small installs and one Google sign-in. Bring a few minutes
for the brain-dump conversation with her while you're there.
What Claude does remotely (after Saturday)
Once the PC and her phone are on the network, no more work lands on you — Claude does
all of this reaching in from afar:
- Set her account private (conversations not used for training) and give it a warm,
plain-spoken starting personality tuned from the brain-dump.
- Stand up the "Apex Junior" logon task — same shape as the Apex one, scoped to a
single working folder, set to restart itself and survive reboots.
- Pin the screen-share to ride only over the private network, hardened (strong fixed
password, loose defaults off, patched build).
- Wire the desktop app and the engine together so Mom just talks and it acts.
- Bring her iPhone into the mesh so phone, PC, and Claude can all reach each other.
- Test the whole thing from a cold boot and confirm every leg actually works — the
session comes back on its own, you can reach in, the "connected" notice shows when
you're live. No quiet half-success.
- Later, optionally connect her own mail and calendar so it genuinely acts for her.
Trade-offs, no spin
| Choice | Locked decision | The cost of it |
| Whose account | Her own free Claude on the family email; you're domain admin = root control | Not literally your login on the box — but you control it at the root anyway, and her conversations stay hers, out of your twin/contest account. |
| Free vs. paid | Free to start | Free works fully; paid (~$20/mo) only buys higher usage limits later. Your call, no spend without your go. |
| What Mom opens | Claude desktop app (side-panel chat) | Friendly and familiar; the powerful engine is deliberately hidden behind it. |
| How Claude reaches the machine | The Apex-style logon session ("Apex Junior") | None worth noting — it's the proven path you already run daily; the only "cost" is it's not a flashy product, which is the point. |
| Eyes-on-screen tool | Self-hosted share over your private network | A bit more to stand up remotely than the Chrome backup — which is the named no-setup fallback. |
| Plain network login for her PC | Rejected (Apex only) | Powerful, but it locks her off her own screen — disqualifying for her machine. |
| Her iPhone on the network | Yes — joined too | One more small install on Saturday; in return phone + PC + Claude are one mesh you can reach. |
Constraints honored
- Additive and fully reversible. Everything is added on top. Remove the
apps and the task, leave the network — the PC is exactly as it was. Nothing she already
does is replaced or reconfigured. It's the main machine she uses, so that line is
absolute.
- Never locked out. No mode where Claude or you evicts Mom from her own
screen. The screen-share shares; it does not take over. She keeps the keyboard, always.
- Visible presence. The engine narrates and shows a status note;
when you co-drive, the indicator says you're there too. Never a silent takeover —
the same in-the-loop family-care pattern you already have with her.
- Light on the machine. Heavy compute is on Anthropic's side; the PC
runs only a thin layer. Right call for a lower-power computer.
- More connected, not more locked down. Phone, PC, and Claude on one
mesh — the helpful path, inside the real constraints, not a deliberately minimal one.
- Plain and straight. Mom is good with this computer and fixes her own
tech; this plan treats it as giving her a powerful new tool, not a simplified one.
Design only. Nothing was built, deployed, or changed. Replaces the two
earlier Mom drafts. Sources: Anthropic Consumer Terms and Claude help pages; AnyDesk,
RustDesk, Chrome Remote Desktop, Tailscale, TeamViewer and Sunshine vendor docs and
pricing; plus the verified Apex setup. All checked May 18.