Every guide here started as a question a member actually asked, in a real working session. When the same question comes back, it earns a spot here. For the full walkthroughs, the manual is the place.
Memory & imports
Yes. Ask your clone to delete those conversations. Deletes are scoped: on local memory, a whole import at once, one project, or one session; on hosted memory, one project or one session for now. Wiping everything blindly is refused by design. Your clone first shows a preview of exactly what would be removed, and nothing is deleted until you explicitly confirm.
How memory is organized: Your clone's memory.
Neither, anymore. /klyr:status now counts everything your clone remembers, imports included, and each part of the product reports working, degraded, or broken, with the last error in plain words. If your status looks wrong, update first.
The update ritual: Troubleshooting.
Google Drive sync
Nothing — that is the designed path. The first sync catches up by itself in the background, a little at a time, and slows down on its own when Google asks it to. Configure your folders once and let it catch up. After that, it only fetches what changed.
The full model: Connectors.
Yes. Name it. "Pull the clients/Acme folder" fetches that folder — or a single document — right now, ahead of the regular schedule, and touches nothing else. It is the natural gesture at the start of a session: pull what you are about to work on, then work.
More: Connectors.
You already are, by default. The sync ships docs-only: Google-native documents, exported as text. Other profiles exist — add plain-text files, everything-but-media, or your own custom rules — plus a size guard that skips oversized files regardless of type. Skipped files are counted and shown in status, so an exclusion is never silent. Change the profile anytime with /klyr:config.
More: Connectors.
By itself. Your Drive folders sync automatically on a cadence you choose — every 15 minutes, hourly, daily, or manual-only — set with /klyr:config. One thing never runs on a schedule: writing back to Drive. A push is always explicit, one document at a time, confirmed by you.
More: Connectors.
Day to day
Direction. The workspace is your clone's home: the folder where it files what you share with it, as plain markdown you own. Sources point the other way — read-only places it watches, like your Drive mirror, that feed its memory without it ever writing there. Your folders stay yours; the clone has its own desk.
The full picture: Workspace & sources.
No. Every setting you can change is reachable from /klyr:config, interactively: memory consent, sources, connector folders, sync cadence, file filters, crash reports, all of it. If you ever find a setting that requires editing a file by hand, that is a bug — tell us.
Living in the terminal without fighting it: The terminal, tamed.
Ask anything at hello@getklyr.ai or from the help page. A human answers, usually the one who built the thing. The first time, you get a direct answer. The second time someone asks the same thing, it gets written up here.
Ask a question