03 — Practice
Companionship that remembers you, without collecting you.
People talk to these systems about things they have told no one else. That makes memory the feature and privacy the obligation — and it makes honesty about what the software is non-negotiable.
In development
A companion that lives on your desktop.
Not another tab you open when you remember it exists. A small character that occupies a corner of the screen, notices the shape of your day, and is there when you look up — the difference between something you visit and something that keeps you company.
Running on the desktop is also the honest answer to the privacy problem. Conversations that never have to leave the machine they happen on are the strongest guarantee anyone can offer.
- Present, not demanding
- It sits at the edge of the screen and stays quiet. A companion that interrupts to keep you engaged is not company — it is a notification with a face.
- Ambient by default
- Most of the time it is idle: reacting to the hour, to a long stretch of work, to your return. Conversation is available, never the price of admission.
- It lives on your machine
- Running on the desktop rather than in someone else’s tab changes what is possible — the memory of your conversations can stay on the device that holds them.
- Small enough to keep around
- A companion you close after a week has failed. Modest CPU, modest memory, no fan spinning up because something is idling in the corner.
What makes it work
Four things a companion has to get right.
Memory that carries
A companion that forgets you between sessions is a chatbot. Continuity is the whole product — what was said last week shapes what happens today, and the system can show you what it remembers.
A consistent character
Personality that holds steady instead of drifting with every prompt tweak. Tone, values and manner are specified and regression-tested, the same way we test anything else.
Warmth without pretence
It responds with care, and it does not claim to feel things it does not. People deserve companionship that is honest about being software.
Private by architecture
Intimate conversation is the most sensitive data a product can hold. What is retained, where it lives and how a person erases it are settled in the design, not in a policy page.
The measure of a companion is not how long someone stays — it is whether they are better off for having talked to it.
Boundaries
What it will not do.
This category attracts products that optimise for time spent and stay vague about what they are. We would rather be specific, publicly, and be held to it.
- Not a clinician
- It never presents as a therapist, counsellor or doctor, and it does not diagnose.
- Escalation paths
- When a conversation signals crisis, the system surfaces real human resources rather than trying to handle it alone.
- No dark patterns
- Engagement is not the metric. Nothing is designed to make leaving feel costly.
- Erasable
- A person can read what is stored about them and delete it, permanently, without asking us.
Building something in this space?
Whether you need the whole product or just the memory and safety architecture underneath it, tell us the shape of what you have in mind.