@geoffreylitt Love this use case 💪

@luminxbt - scans Zillow for me - researching moving companies and helping negotiate rates - searching childcare options - managing the schedule to keep it on track, telling me what to prioritize each week

@geoffreylitt bros really outsourced grocery runs and lease negotiations to AI

whats the move planning part look like?

@geoffreylitt this feels right. the useful part is not automatic memory, it is a shared place where the family can see what the agent knows and fix it when it is wrong.

@geoffreylitt Great name

@geoffreylitt managing your money AND packing your boxes is a wild leap from fetching oat milk

do they plan routes around the apartment too?

@geoffreylitt Btw asking since it’s been a while: is this still your approach wrt changesets and programming?

@geoffreylitt yeah this is exactly where memory turns into permissions. the useful version is not just what the agent knows, it is what the family can see, edit, and revoke.

@geoffreylitt planning a move before it does the actual finances gives me pause

@subramanya Automatic memory usually creeps me out and is rarely helpful. Whereas context that I actively curates usually feels awesome. Maybe it’s a control thing…

@geoffreylitt Exactly. A family agent without durable household context is basically just a very confident intern.

@geoffreylitt planning a move is where it gets interesting

hope it negotiates the rent better than it shops lol

@geoffreylitt This generalizes beyond family agents: the durable object is not the chat, it is the curated work context.

The product problem is making that context shared, inspectable, permissioned, and easy to update without turning into invisible memory.

@geoffreylitt Awesome! I've been playing around with the Kroger API + a Notion Worker for our grocery orders. Had my wife talk to an AI meeting note with our meal plan/ingredient list and the agents are getting it to the cart!

I'm awaiting a Whole Foods API before going all in with my workers