Parent Loop
Built at Meta Global AI Developer Hackathon · Oct 26, 2026 · Remote

ParentLoop — Keeping a kid organized for school is a second job. ParentLoop crowdsources the context and lets your AI agent do the organizing. School information reaches parents scattered across duotangs, photocopies, assignments copied off the board, email, and school messenger apps. Every parent receives everything for their own child — the problem is the work. Feeding it all to an AI agent, day after day, is a second job nobody can sustain. ParentLoop is a shared hub where one parent adds what the school sent and every family's agent benefits; parents take turns, so a daily chore becomes an occasional one. Each family's own AI agent reads the hub through a scoped token and produces a nightly check filtered to that one child: what's due, what to bring, what conflicts. What it does: - Hubs: a shared repository for one school class or team. One parent's upload serves every family; parents rotate adding the weekly newsletter. Children's details never enter a hub. - Reading: each item becomes dated, per-audience facts. Picture-only pages are read with vision/OCR, including small print such as "no masks" or "helmets required". - Verification: every fact must carry a verbatim quote from its source, checked by code. Facts whose quotes don't check out are dropped and counted, never shown. - Evening check: a nightly briefing for that child only — action items, timing conflicts, and nudges for anything due within two days — in the app, by nightly email, or through the parent's own agent, which can relay the prepared check or pull a context bundle (GET /api/agent/context) and write the check itself. - Belonging checks: 1–3 challenge questions only parents from that school would know; answers are stored only as salted hashes, and invite links expire after 7 days. - Agent access: scoped, revocable tokens and a public manifest (GET /api/agent). One-tap connect: an agent presents an invite link, the parent approves once, and the agent collects a family-scoped token. Agents can also feed the hub, e.g. from Gmail. - Privacy: hub members see parent names and roles — never children's names or grades. Unknown tokens are refused, never silently served someone else's data. The public demo uses fictional data only. Measured results: on a purpose-built 4-page test newsletter (23-fact answer key, 12 facts only inside pictures), extraction captured 21 of 23 facts, including every piece of poster small print. In a live one-tap connect test (Nov 4), my agent collected a family-scoped token and read the full context bundle across 4 real hubs (8 materials, 33 facts). Live site: https://parentloop-964717527488.northamerica-northeast2.run.app