// Guides

Asked for real, answered for real

Nothing on this page was invented in a docs sprint. Every guide started as a question a founding 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

"I imported thousands of conversations by mistake. Can I delete them?"

Yes. Ask your clone to delete the import. Deletes are scoped — a whole import, one project, or one session; 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. That preview-then-confirm ritual is identical in hosted and local mode; scoping a delete by source is currently local-only.

How memory is organized: Your clone's memory.

"Status said I had no memory. Recall clearly worked. Which one lies?"

Neither, anymore. This was a real bug: the health check only counted the memory stores it knew by name, so imports living in their own stores were invisible to it — while search found them fine. It is fixed: /klyr:status now counts every store you have, 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

"My first sync is a hundred gigabytes and Google started throttling. What now?"

Nothing — that is the designed path. The initial sync runs bite by bite: a budgeted slice per run, a daily volume cap, automatic backoff when Google throttles, and it resumes by itself on the next scheduled run. Configure your folders once and let it catch up in the background. Once caught up, the same schedule carries light delta pulls of just what changed.

The full model: Connectors.

"Can I pull just the folder we're about to work on?"

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.

"My Drive is full of videos and audio. How do I keep them out?"

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.

"Does the sync run by itself, or do I have to think about it?"

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

"What's the difference between my sources and the clone's workspace?"

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.

"Do I ever need to edit a config file?"

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.

How a question becomes a guide

Ask anything at [email protected] 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 — that is the only way onto this page.

Ask a question