Private beta · invite required

Your clone, alive in minutes.

Klyr is a Claude Code plugin that puts your DNA into Claude, so it stops being a generic assistant and becomes your clone. This page takes you from a fresh machine to the first conversation where it already knows you.

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

Four steps. No key to paste, nothing to babysit.

Before you start

What you need

  • Claude Code, with a Claude subscription. Klyr runs inside Claude Code and thinks on the Claude subscription you already have.
  • A Mac or Linux machine. Windows works through WSL.
  • Your invite. It carries your install script and the email address your access is tied to.

Step 1

Install the plugin

Run the install script from your invite in a terminal. It sets up the basics on your machine and installs the Klyr plugin into Claude Code.

When it finishes, fully quit Claude Code and open it again, so the plugin loads.

Step 2

Connect your clone

In Claude Code, run /klyr:init and pick Hosted. It walks you through everything: your browser opens to sign in (enter the email from your invite, click the link we send you, single-use, expires in 15 minutes; no key to copy), then it either brings your existing Klyr onto this machine or sets up your clone from scratch. One command, start to finish.

Once you're in, your clone's memory lives in your own private space, hosted in your region. Always on, zero maintenance, nothing extra to run on your machine.

Prefer to keep everything on your own machine? Same command, choose Local: the free, self-host path. Fair warning: 16 GB of RAM is the floor to even install the local stack, not comfort. Adding a second machine to an existing hosted account later? /klyr:login then /klyr:sync is the short path.

Step 3

Let it meet you

Start talking, in plain language: what you're working on, how you like to work, what matters right now. Or run /klyr:kyh and let it interview you. You talk, it writes down who you are, how you decide, what you're building. That becomes your DNA: the identity it carries into every session.

Already have a past with AI? Import as much or as little of your ChatGPT and Claude history as you want, so it starts already knowing you.

Step 4

Make it prove it

Quit Claude Code. Reopen it. Ask: "what do you know about me?"

A generic assistant starts from zero. Your clone picks up where you left off: your projects, your decisions, your way of working, already loaded. That's the moment most people get it.

That's the whole setup. From here it compounds: it learns how you work as you work, and every week it is a little more you.

Stuck somewhere?

Founding beta means you talk to the person who built it, not a ticket queue. Write to [email protected] and say where it stopped. Straight answers, no scripts.

Not invited yet? Get in line.

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