Blog
How AI products get to know their users. Notes on context, memory and personalization for agents, from the team building Configure.
AI onboarding without the questionnaire
Your onboarding asks people who they are. They have already told three other products. Stop asking and start from there.
The cold start problem in AI apps: knowing your user
Your agent is as smart as anyone's. On day one it still knows nothing about the person in front of it.
What is context as a service?
People will use many agents. Context as a service is how what one of them knows about you can follow you to the next, with your permission.
Cross-agent memory: how agents share what they know
What you told one agent should be able to help the next one, if you say so. That is cross-agent memory.
How to personalize an AI agent from the first message
Personalization is a loop: read what you know before you answer, use only what bears on the task, and save what you learn.
Multi-agent memory: one person, many agents
Everyone is building an agent. The person using five of them is the one nobody is building for.
Plaid for AI: why agents need a connect button
Technical users wire their agents together by hand. Everyone else needs a button or two.
Portable AI memory: can you take it with you?
You can move your photos, your contacts and your bank data. Moving what your AI knows about you is still mostly copy and paste.
User memory for AI agents: who should hold it?
Every agent wants to remember you. The more useful question is where that memory lives and who gets to decide.
What is an MCP connector?
A connector is how an assistant gets a new ability without anyone rebuilding the assistant. It is also how agents can start sharing context.