Straight answers

The questions you're actually asking.

Klyr is a Claude Code plugin that puts your DNA into Claude, so it stops being a generic assistant and becomes your clone. Before you trust it with how you think, you should ask hard questions. Here they are, answered plainly.

The product

Why not just build this myself?

You could. I did, over two years. Here's the trap: the memory part is the easy part. Anyone can bolt a notes database onto Claude in a weekend, and that is exactly what you get, a memory system that needs babysitting. The two years is turning that into a clone that thinks like you and stays sharp on any machine without rotting. You want to run your business, not become the maintenance engineer of your own brain-in-a-box. And you'd need the machine: 16 GB of RAM is the floor to even install the local stack, not comfort. Nice results take an Apple Silicon Mac with 64 GB, or a serious NVIDIA GPU. Hosted, the heavy models run on datacenter hardware, and your machine does none of the lifting. Klyr is the two years you don't spend.

Isn't this just a big system prompt or a CLAUDE.md file?

A file is a dead snapshot. It doesn't remember last week's call, doesn't grow when you decide something new, doesn't follow you across machines. You would spend your evenings feeding it by hand until it rots. Klyr isn't a file you maintain. It's a second you that shows up already up to speed and gets sharper as you work.

Claude has memory now. Why Klyr?

Claude's memory is real, and good: it learns your preferences from your chats, inside Claude. Klyr goes two layers deeper. One, it doesn't just note a few preferences, it builds a living model of how you actually think and work, on top of the identity you author yourself, so it acts like you, not like a tool that caught a few facts about you. Two, the part Claude has no answer for: your whole past, carried with you. Import your history from Claude, ChatGPT and OpenClaw, add everything you do in Claude Code, and your own notes vault, all kept on a timeline so last year and last week never blur into one. That's your second brain, not a chat summary. And it's yours: self-host it, take it anywhere, it never lives locked inside one app.

Why not OpenClaw, Hermes, or one of the other agent tools?

I ran both, for months, so this is my experience, not a spec sheet. OpenClaw started brilliant, then for me it rotted: pile on enough memory and it began hallucinating, mixing up my clients, contradicting decisions I'd made the week before. And I became its full-time babysitter, pruning, patching, restarting, a second job I never asked for. Hermes "fixed" that by capping its own memory, which to me is just a goldfish with a smaller bowl: it stays sane by staying dumb, forgetting you on purpose. Both buried me in flashy features that looked powerful in a demo and did no real work for me. And there's a structural risk worth knowing: Anthropic has already restricted third-party tools on Claude subscriptions once, and could again. Klyr doesn't run as an outside harness that pipes your subscription out. It runs inside Claude Code itself, the first-party path Anthropic keeps supported, the same place their own routines run.

Your data

Where does my DNA live? Is it private?

It's yours, and you can see it. Klyr only remembers what you give it inside Klyr, never your whole machine or your files behind your back. You can read, edit or wipe any memory, anytime, it's not a black box. It lives on your own machine, or your own private space in your region if we host it. When your clone thinks, it sends only what that question needs to Claude, on the Claude subscription you already have. We never read it, never train on it, never sit in the middle. You're the customer, not the product. Nobody gets a window into your head but you.

Where exactly is the hosted version hosted?

In your own private space, hosted in your region. One space per person: your memory is never pooled with anyone else's, never shared, and never used to train any model. We run the servers so you have nothing to install or maintain; what's inside stays yours. The fine print is on the privacy page.

Does Klyr store my conversations?

Yes, and that's the point: Klyr keeps a searchable copy of your Claude Code sessions in its long-term memory. That's how it recalls the call from three weeks ago instead of asking you to repeat it. Secrets like passwords, keys and tokens are redacted before anything is stored, and the copy lives wherever your memory lives: on your machine if you self-host, in your private hosted space if we host you.

Don't want it? One setting turns conversation storage off entirely, whether you self-host or we host you. Off means off.

What happens to my data if I leave?

You leave with it. Your identity files are plain text you can open, edit and copy; nothing proprietary. Self-hosting, one command exports your memory to a plain, open file you keep. Hosted, export and full deletion are available on request. Day to day you can already wipe any single memory yourself, anytime. Your clone is yours, not a hostage.

Practical

What do I need to run it?

Klyr is a Claude Code plugin. Today it runs on Claude Code, on Mac and Linux, or Windows through WSL. Coming soon: Codex, and native Windows.

How do I get in?

Klyr is in private founding beta and the founding cohort is full. If a few spots open, the waitlist goes first. No promises. Already invited? Setup takes minutes: follow the get-started page.

Your business has run on one brain long enough.

The founding cohort is full. If a few spots open, the waitlist goes first. No promises.