← 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:

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:

  1. 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.)
  2. 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.

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.

ToolFree for this?You own it?Locks Mom out?Verdict
Self-hosted screen-share over the private networkYes — free, open sourceYes, fully — your own relayNo — shares the screen, she keeps the keyboardPrimary. Free, yours, never evicts her, same trust boundary as Apex
Chrome Remote DesktopYes — free, no license trapNo (Google's relay), but an identity the family already usesNoNo-setup backup. Two clicks, nothing to buy — best if the primary is fiddly to stand up remotely
AnyDeskNo — paid for family help; free tier flags it as commercialNo — their cloudNoBeaten on every column; rejected
Plain Windows network loginYesNetwork yesYes — kicks her off her own screenRejected for this machine. Fine for the headless Apex box only
TeamViewerEffectively no — aggressive "commercial use" flagging, then a big yearly billNoNoLicense-lockout risk disqualifies it
Game-streaming toolsSome freeSome yesNoWrong 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.

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:

Trade-offs, no spin

ChoiceLocked decisionThe cost of it
Whose accountHer own free Claude on the family email; you're domain admin = root controlNot 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. paidFree to startFree works fully; paid (~$20/mo) only buys higher usage limits later. Your call, no spend without your go.
What Mom opensClaude desktop app (side-panel chat)Friendly and familiar; the powerful engine is deliberately hidden behind it.
How Claude reaches the machineThe 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 toolSelf-hosted share over your private networkA bit more to stand up remotely than the Chrome backup — which is the named no-setup fallback.
Plain network login for her PCRejected (Apex only)Powerful, but it locks her off her own screen — disqualifying for her machine.
Her iPhone on the networkYes — joined tooOne more small install on Saturday; in return phone + PC + Claude are one mesh you can reach.

Constraints honored

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.