SYS // WOODHOUSEONLINE
WOODHOUSE
PRIVATE HOUSEHOLD INTELLIGENCE
ROCHE RESIDENCE
MEMORY COREONLINE
IDENTITYAPPLE
REASONINGONLINE
WOODHOUSESign in
SYS // WOODHOUSE · PRIVATE HOUSEHOLD INTELLIGENCE
AN AI-FIRST HOME.
ONE BRAIN, EVERY ROOM, EVERY HOUSE.
Woodhouse runs the Roche household: two homes, six people, a split-flap board, a pool, the thermostats, the gate, the cameras, the TV — through one assistant that remembers. Say it in chat, say it out loud, tap it on your phone, or let a rule do it when you pull into the driveway.
VercelVercel EveAI GatewayGrokJevVestaboardDGX SparkApple Sign InLinq iMessage
Cortex · the living-room TV · the house's memory, drawn as a constellation
01 · Talk to the house
Say what you want. Woodhouse does it, shows it, and remembers it.
Chat on the web or in the app, talk to the Mac (“Hey Woodhouse”), or answer from your lock screen. Replies come back as cards — a schedule, a board preview, the pool — never a wall of text.
kyro.house · console
One assistant, every surface
Web, iPhone, iPad, Mac, voice, Siri Shortcuts. Same session, same memory: ask in the car, continue on the couch.
Generative UI
Woodhouse renders what it means — a day schedule, a chore ring, a board preview, a device card — and the app draws the same card natively.
Lock-screen decisions
“Can I go out after school?” arrives as YES / NO. A dinner time proposal arrives as ACCEPT, with Woodhouse having already checked both calendars.
Latency you notice
The owner runs on the newest Grok the AI Gateway offers, tuned for first-token speed; the physical board, the pool and the thermostats respond in about a second from the app.
Reflexes, no model at all
“Poles off.” A short command that plainly names a light, a scene or a routine is matched by Jev — a decision model that answers in a third of a second and writes no prose — and runs directly. Anything with a question, a time or a second step goes to Woodhouse as usual; the gate never runs this way.
02 · The brain
A cloud brain on Vercel Eve, with a model per person.
Woodhouse is an eve agent: durable sessions, tools, skills and extensions, deployed on Vercel. The owner gets the latest Grok, resolved from the AI Gateway catalog so nothing is ever pinned; the family runs on Grok 4.3, and Jev reads each request first: a plain command or a bit of chat skips the thinking pass, a question about calendars and times keeps it. Artwork for the board comes from GPT-5.5. One codebase, three model providers, zero API keys in source.
Durable sessions
Every conversation is a durable run: reconnect from the phone, the Mac, or the TV and the turn is still there.
Tools, skills, extensions
Forty-odd tools behind one permission manifest. The board is a proper eve extension; the pool, the gate, the cameras are tools with role gates and owner notifications.
Memory that belongs to people
An LLM-wiki in Neon Postgres + pgvector: raw sources, compiled notes, links. Private by default; a child's proposal to shared memory waits in a parent's review queue. Shared notes can be published one way to a FalkorDB graph the owner's work agents use; nothing flows back.
Honest models
Owner → latest Grok via the AI Gateway. Family → Grok 4.3, reasoning chosen per turn by Jev (about a second for simple requests). Board art → GPT-5.5 (it won an eight-model bake-off). Kids' coding → GPT-5.4. Voice → Grok speech. The catalog decides, not a hardcoded slug.
03 · The hands
A gateway node in every house. LAN devices never leave the LAN.
Each house has a DGX Spark on the tailnet and a Mac running the menu-bar site agent. The cloud brain reaches them through a token-gated Tailscale funnel with a mailbox fallback; the pool, the thermostats, Sonos, the printers and the Frame are only ever spoken to from inside the house. The same Woodhouse also runs on each Spark with a local model, so the house keeps a brain when the cloud doesn't answer.
Any Mac
The site agent is a native menu-bar app: Keychain token, sandboxed, outbound-only. Point it at a house and it becomes hands for that LAN.
DGX Spark
A 24/7 gateway per house: direct RPC for the cloud, Sonos and thermostats and the pool on the LAN, and an edge build of Woodhouse on a local model.
Fails soft
Gateway first, Neon mailbox second. If a house goes dark, Woodhouse says so and tells you when it last heard from it — it never guesses.
04 · The board
A split-flap Vestaboard, driven like a device Woodhouse owns.
“Put Seamus' chores on the board.” “Draw a sunset for the board.” “Save that as the birthday board.” The studio previews exactly what the cloud will render, live boards compose themselves from house data, and every send mirrors to the TV.
kyro.house/board · studio
Live boards
Chores (a tile per task: green done, black not yet, red late), today's calendar, who's home, the points leaderboard — rendered from house data the moment you ask.
Artwork
GPT-5.5 paints 6×22 pixel art from the eight tile colors; Woodhouse shows the preview in chat and sends nothing until you say so.
Saved boards
Name one and anyone in the family can put it up — “the welcome board”, “the birthday board”.
An eve extension
The board ships as a proper extension: tools, a composition skill, a rate guard, and hooks the host uses to mirror every send to Cortex.
05 · Cortex
The house on the TV — and on every screen with Cortex open.
Cortex is Woodhouse's display surface: the memory constellation when idle, the thermostats, the cameras, the map, the board. “Put the climate on the TV” lands on every open screen; a new screen pairs with a code you approve from your phone.
Scenes
brain · climate · cameras · map · board — driven by chat, voice, routines, or Shortcuts.
Latest on the board
Every board change slides in for half a minute, then keeps a small copy in the corner.
Privacy mode
One phrase blanks every screen for guests; the memory scene shows titles on the wall and full text only on your own devices.
06 · The family
Six people, three roles, one set of rules.
Everyone signs in as themselves — an Apple ID, or a parent-set login for a child too young for one. Owner and adults run the house; kids get least privilege — every action parent-approved, every shared-memory write reviewed. Presence comes from the phones' geofences, so “play some jazz” already knows which house you're in.
kyro.house/admin · chores
Missions: chores, points, the Danger Zone
Recurring chores with a schedule, verify queues for parents, points and streaks, and a dossier system for docked points — with a photo, a contest, and a way to work it off.
Geofences
Arrive and leave events feed presence, routines, and the map. The house knows who's home without anyone saying so.
A judge, not a nag
After Woodhouse reads an email or a document, anything with consequences used to pause for a yes. Now Jev compares the action with what you actually typed: exactly your words, it runs; anything the outside text could have slipped in, it still asks — and the gate, outgoing mail and admin always ask.
Per-person Google
Calendars and mail are connections, not identity — each member links their own accounts, several if they like.
07 · Automation rules
Routines: triggers, conditions, actions — written in chat, run by the house.
“When the first person gets home after dark, lights on and the map on the TV.” “Office poles on when Kyle arrives.” Anything destructive parks for an approval that arrives on your lock screen.
kyro.house/ops · routines
Triggers
Arrive or leave a site, first person home, last person out, a time on given days, or manual — including Siri Shortcuts.
Conditions
Who's present, who's absent, a time window, a day of the week.
Actions
Notify, Sonos, lights, a delay, the gate (approval-gated), and any Cortex scene on every open screen.
Dry runs
Every routine can be rehearsed: the trace shows each step and what it would have done.
08 · Kids build with it
Vibe: the kids talk to a real coding agent, fenced in a sandbox.
fx — Vercel Labs' tiny native coding harness — runs each turn in a throwaway Vercel Sandbox that only sees the kid's project, with GPT-5.4 through the AI Gateway. The page is kyro.house/vibe from anywhere, behind the family sign-in; projects and every turn's snapshot live in private storage, so undo is instant. 2D canvas or 3D with three.js — the kid's choice. Every turn ends with “What I did and why” in words a ten-year-old understands.
kyro.house/vibe · space game
A whole game first, then small steps
“A ship that dodges asteroids, with a score.” About a minute later it's playable in the preview — controls, collisions, score, game over. “Make the ship faster” edits the same files. Undo puts it back.
Explained, not dumped
The builder never pastes code at a kid. It names one idea per turn — a variable is a labeled box, a loop repeats — and “explain it like I'm not an engineer” walks through the whole game without changing a line.
Sandboxed, family-only
fx is fenced in a throwaway microVM with the project folder as its whole world; games are stored privately and reach the kids only through the family's own sign-in, never a public URL. Publishing to the web is a parent's later decision.
Guardrails a parent set
Plain HTML/CSS/JS only, no network calls, kid-safe content rules the model follows and the house double-checks, every build load-tested (a crash goes straight back to the builder to fix), a middle-school guide with three example games, and per-kid daily, weekly and monthly caps — in builds or in dollars — that a parent sets.
09 · Text it
Woodhouse has a phone number. One-to-one, or in the family group.
iMessage through Linq on Vercel Connect — no Mac in a closet. Text him a fact and he files it; ask for a reminder and he texts you back at the time; add his number to a group and he answers when someone names him (Woodhouse, Woody, W…).
Approvals are tapbacks
Anything that needs a go-ahead arrives as a text; 👍 approves, 👎 cancels. A child's request needs a parent's thumb; private things asked for in a group wait for the owner's.
Parents steer each group
“Woodhouse, mute this group.” “Only answer me and Jessica.” “Allow the kids.” Parsed in code, no model turn — and the kids are quiet in groups unless a parent says otherwise.
Context without eavesdropping
A group turn carries the last ten messages so “isn't that right, Woodhouse?” has something to be right about; everything else in the thread is never read.
Priced in turns, not texts
Linq bills per line; what each message costs is a model turn. So the gate sits before the turn: unknown numbers dropped, a daily cap for kids, Jev deciding whether an un-named message was meant for him.
10 · Plans
Events with a page, reminders that find you, schedules that read like English.
“Family dinner at our place Sunday at 3, bring dessert or a salad.” Woodhouse asks for what's missing and hands back a link anyone can open.
Event pages
kyro.house/events/… — details, Google and Apple calendar buttons, yes/no, a headcount, a bring-list. Family replies from their sign-in; guests prove an email with a six-digit code Woodhouse mails them. The page comes down a day after the event.
Reminders
“Remind me Thursday at 3 to call the dentist” — a one-shot that texts you (or emails you) at the time and then retires itself.
Repeats as one row
“Chores board up every hour from 7 to 9 through Sunday” is a single schedule with a real cron and an end date, shown in words: every hour 7 AM–9 PM until Oct 12.
11 · Devices today
What Woodhouse already has its hands on.
Cloud when a vendor has a decent API; the LAN through a Spark or a Mac when it doesn't. Never a vendor app in the loop for notifications.
Vestaboard
split-flap board
Trane Link
two-floor HVAC, zoned
Venstar ProStat+
work-house thermostats
Pentair IntelliCenter
pool + spa
Avigilon Alta
neighborhood gate
Blink
cameras
Sonos
whole-home audio, both houses
Govee
lights + office poles
amaran
studio lights
TRMNL
e-ink displays
Samsung Frame
TV art
Brother
printers
Eight Sleep
the bed
eero
the network
Reolinkplanned
PoE doorbell
12 · Open to agents
Readable by the next LLM, runnable by the next household.
The source is MIT. The site publishes what an agent needs to understand it, and the repo carries the handoff a coding agent needs to set it up or change it.
/llms.txt and /llms-full.txt
The short and the full summary: what this is, what is open, how to set up your own, every env var.
MCP, by invitation
A bot can hand Woodhouse a task over MCP at /eve/v1/mcp with a token the owner mints — the owner's own Grok bot runs this way. Discovery at /.well-known/mcp.json; the public surface in /openapi.json.
CLAUDE.md is the handoff
Locked decisions, hard-won lessons, the permission manifest, the ship rituals — the file a coding agent reads first. STATUS.md says what is tested; USER-GUIDE.md says what the family can do.
Set up your own, in order
- 01Clone kyleroche/kyrohome · npm install · vercel link · a domain
- 02Neon from the Vercel Marketplace · apply-schema · seed your family as principals
- 03Models through the AI Gateway (OIDC, no keys): newest Grok, Grok 4.3, Jev, GPT-5.5
- 04Sign in with Apple: App ID, Services ID, key → APPLE_* · SESSION_SECRET · APP_URL
- 05Pick integrations: Google (Connect), Linq iMessage (Connect), Vestaboard, TRMNL, the devices you own
- 06git push · GET /eve/v1/health → 200
Woodhouse runs one household.
Built by Kyle Roche.
Next.js on Vercel·Vercel Eve·fx·AI Gateway (Grok, GPT-5.5, Jev)·Neon + pgvector·FalkorDB·Tailscale·Swift on iPhone, iPad, Mac
Sign in · Apple IDEncrypted channel · kyro.house·About·Contact·Developers·Privacy·Terms·llms.txt