Preference editors are useful, but they are rarely where clients naturally explain what changed.
Someone might say, "I want to eat vegetarian this week," or "I have black beans and tortillas now," long before they open a settings screen. The expanded Lumo Agent is designed to make that conversation useful.
Clients can now ask for changes in plain language, and Lumo can turn that message into saved preference and pantry updates.
What changed
The Agent can recognize when a client is asking for a persistent change rather than just asking a question. In the pilot example, the client asks Lumo to make meals vegetarian and add black beans and tortillas to the pantry.
Lumo can acknowledge the request in character, then reflect the actual saved updates back to the client:
- Updating preferences.
- Updating pantry.
- Confirming what changed.
That turns a casual message into structured context the product can use later.
Why it matters
Personalization gets weaker when preference updates are buried behind forms. It gets stronger when clients can simply tell Lumo what changed and see that the product understood.
This is especially important for food. Pantry availability, prep time, dislikes, diet patterns, and household constraints shift constantly. A chat-first update flow lets Lumo keep up without making the client do administrative work.
We are continuing to test where this should be automatic, where Lumo should ask for confirmation, and how much control dietitians should see on the care side.