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.
The install command ended without installing Klyr
A finished install always ends with a closing line that starts Klyr is installed (on Windows it can also read Klyr installed and ready), followed by your next step. If the command went back to the blinking cursor without that line, Klyr is not installed, even if nothing on screen looks wrong. The /klyr: commands further down this page come with Klyr, so they cannot help yet. Here is what to do instead, depending on what you see:
- "Klyr was NOT installed. Nothing was changed on this computer." The installer could not be downloaded at that moment, and the problem is on our side. Wait a few minutes, then paste the same install command again.
- One line starting with
curl:, or red error text on Windows. The download itself did not get through, often because the connection dropped. Check that you are online, then paste the same install command again. - A message from the installer itself (for example, that Git is missing on Windows, or that the window was opened as administrator). Do what that message says, then paste the same install command again.
Running the install command again is always safe: it picks up where it left off. If it still ends without that closing line, write to hello@getklyr.ai and paste the last few lines the window shows.
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
Klyr's background helper updates itself, so changes reach you without a command. When something feels stale or half-broken, two steps, in this order:
- Fully restart Claude Code. Quit it completely and open it again. A full restart is what pulls a new plugin version; anything less is not enough.
- Run
/klyr:repair. It checks your install and repairs whatever has drifted./klyr:updatestill works and runs the same thing.
Common fixes
The status line shows the product name instead of your clone's name. Update: restart Claude Code fully, then run /klyr:update.
The memory segment shows ✦—. Memory is not reachable at this moment. Two usual causes: your memory 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.
Signing in shows a "Reconnect Klyr" page. The app you signed in from is using an old Klyr connection that has expired. Most of the time Klyr now picks that connection back up by itself and the sign-in simply continues. When this page shows instead, give the app a fresh connection. In a terminal, run claude mcp logout klyr, then type /mcp, select klyr and choose Authenticate. In a web or desktop app, remove the Klyr connector, add it again, and sign in. Your account and your memory are not affected.
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 hello@getklyr.ai 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.