// Docs

Troubleshooting & FAQ.

Klyr heals itself. On session start it checks its own health and repairs what it safely can, so most problems fix themselves before you notice them. When something does surface, here is the order of operations.

First diagnostic: /klyr:status

Type /klyr:status in Claude Code. It shows Klyr's overall health in a few lines: prerequisites, services, memory, plugin state. Whatever is wrong, this tells you where. Most fixes below start from what it says.

Updating

Two steps, in this order:

1. Fully restart Claude Code. Quit it completely and open it again. A full restart is what pulls the new version; anything less is not enough.
2. Run /klyr:update. It brings your install up to the current version and applies whatever changed.

If something feels stale or half-broken after an update, this same path is the fix.

Common fixes

The status line shows the product name instead of your clone's name. Fixed in 0.26.34. Update: restart Claude Code fully, then run /klyr:update.

The memory segment shows ✦—. Memory is not reachable at this moment. Two usual causes: the memory backend is still starting (give it a minute, especially right after boot on a local install), or you are not signed in (hosted mode: run /klyr:login). /klyr:status tells you which.

Setup was interrupted. Run /klyr:init again. It remembers where you were and continues. It never redoes or erases finished work.

Crash and error reports

If you opted in during setup, Klyr can send an anonymized report when it hits a problem it cannot fix itself. What it contains: the technical signature of the error, nothing else. What it never contains: your notes, your files, your file paths, or anything your clone remembers about you. Anonymous means anonymous. You can turn this on or off anytime with /klyr:config.

Still stuck?

Write to [email protected] and say where it stopped. A human reads every message, and it is usually the human who built the thing. Straight answers, no ticket queue.