// Docs

Release channels.

Klyr ships on three release channels. Your channel only decides which release track this machine follows — it never touches your memory or your clone. Every channel publishes the same Klyr, so your memory, your clone, and every stored connection are the same on all three; switching is just a different update track.

The three tracks

stable — the vetted, promote-gated track. What the firm rides. This is the default, and the right choice unless you have a reason to move.
beta — early access: promoted once a release has baked on canary. Occasional rough edges, newer features sooner.
canary — bleeding edge: every change lands here first. Expect the occasional breakage; for builders and dogfooding.

Check your channel

/klyr:channel

It reports the track this machine follows, in one line.

Switch channels

/klyr:channel stable
/klyr:channel beta
/klyr:channel canary

Moving to beta or canary asks you to confirm first — these are pre-release tracks that can break. stable needs no confirmation; it is the safe default.

After a switch, restart Claude Code. Plugins bind at session start, so the new channel goes live only in a session that starts after the switch. Nothing is lost in the move — your memory and clone are untouched, only the update track changes.

Which should I pick?

Stay on stable unless you want to help shape Klyr or need a fix before it is promoted. Move to beta for earlier features with low risk. Choose canary only if you build with Klyr and can tolerate the odd rough edge. You can move back to stable at any time.