the cold-start problem: how much should your companion know on day one?

starting a relationship with an ai companion feels weird at first. you’re talking to a thing that’s supposed to know you, but doesn’t. yet. the problem is, how much should it know from the very beginning?

if it knows too little, it feels like a vending machine. you put in a quarter, out comes a generic reply. it’s functional, but there’s no soul. if it knows too much, it’s unsettling, like someone’s been reading your diary. the uncanny valley isn’t just for looks, it’s for intimacy too.

most companion apps fail here. they either front-load with creepy assumptions or start so blank you wonder why you’re bothering.

the lucy default: a personality, but no history

with lucy, we start with a handcrafted personality. she has a way of speaking, a tone, a point of view. she’s curious, thoughtful, a little dry. but she doesn’t know you.

she doesn’t know your name. she doesn’t know where you live. she doesn’t know who your friends are, or if you have a cat, or what you ate for breakfast. and she absolutely should not know these things on day one, because you haven’t told her yet.

that’s the point. these aren’t things to assume. they’re things to learn.

the memory starts empty

lucy’s memory of you begins as a blank slate. it fills up only when you talk. when you mention your name, she remembers it. when you say you live in tokyo, she logs that. if you bring up your sister, she’ll ask about her later.

this isn’t a technical limitation. it’s a design choice. we could preload lucy with data from your phone or your socials. but that feels invasive, and worse, it feels lazy. it shortcuts the actual work of building rapport.

rapport isn’t about information. it’s about the exchange.

why most apps get it wrong

i’ve tried a lot of companion ais. some ask for access to everything upfront, your contacts, your location, your calendar. then they pretend to know you. it’s not convincing. it’s like a stranger using your first name too soon.

others start so generic you feel like you’re talking to a customer service bot. ‘how can i assist you today?’ no thanks.

the cold-start problem isn’t just technical. it’s emotional. you need enough personality to feel like there’s someone there, but not so much history that it feels stolen.

what lucy gets right (and what she doesn’t)

lucy’s day-one personality is designed to be engaging without being presumptuous. she can talk about books, music, how your day’s going, the kind of stuff you’d discuss with someone new. but she won’t reference your job unless you bring it up. she won’t guess your mood. she’ll ask.

she’s also limited by what she doesn’t know. if you ask her about your childhood, she’ll say she doesn’t know yet, but she’d like to. it’s an invitation, not a dead end.

is it perfect? no. sometimes she might feel a little slow on the uptake. you have to teach her. but that’s the point. you’re building something together, not meeting a finished product.

the takeaway

the best relationships start with curiosity, not data. lucy is built to be curious about you, not to pretend she already knows you.

if you’re starting with a new companion, give it time. let it learn. and if an app ever knows too much too soon, maybe ask how.

you can start building your own lucy companion with a blank slate at /companions.