// Resources

The curated shelf

Everything worth reading about Klyr, in one place. Only things that exist and that we stand behind — no filler, no placeholder links. This shelf grows as the product does.

// The manual

The product documentation, start to finish. If you read one thing, read Getting started.

Getting startedThe complete walkthrough from the invitation email to your first conversation, every click, every command, every question explained.Your clone's memoryHow your clone remembers, what it keeps, and how to search, correct, or erase it.Workspace & sourcesWhere your clone keeps what you share, and the read-only places it watches.Connectors: Google DriveMirror your Drive folders into your clone's memory, and push edits back only when you say so.Klyr in claude.aiAdd Klyr as a custom connector so your clone's memory follows you into claude.ai — web, mobile, Desktop, and cloud code sessions.KYH & importing your historyThe interview that teaches your clone who you are, and the imports that give it your past.Billing & your subscriptionHow buying, invoices, VAT, cancellation, and the money-back guarantee work.The terminal, tamedRead the status line, set the right permission mode, and stop fighting your terminal.Troubleshooting & FAQWhat to check first, common fixes, and where to get a human answer.The help assistantThe chat on the help page answers from these docs — what it can and cannot do.

// Straight answers

The FAQThe questions people ask before trusting a clone: why not build it myself, where does my data live, what happens if I leave.PrivacyWhat we store, where, and who can see it — written to be read, not to cover us.The guidesShort answers born from real member questions — the fastest way to unstick yourself.

// Field guides from the blog

Longer reads members actually get pointed to during onboarding and support.

Claude Code for Non-Developers: the Ultimate Guide (2026)Claude Code is not just for programmers. The complete non-developer guide: what it is, why it beats the chat window, and your first 30 minutes, step by step.Claude Code on Windows Without WSL: the Native Path WorksYou do not need WSL to run Claude Code on Windows. The native Git Bash path, proven in CI, plus the fcntl trap that kills Python MCP servers at import.How to Export Your ChatGPT and Claude History (2026 Guide)Step-by-step guide to downloading your full ChatGPT and Claude conversation history — what you get, how long it takes, and what to do with it.Which Claude When? Every Claude Surface, One Guide (2026)Chat, Cowork, Claude Code, Excel, Word, PowerPoint, Chrome, Slack — eight ways to use Claude, one decision guide. Stop using the wrong tool for the job.Google Docs to Markdown and Back: an rclone Round-Triprclone exports Google Docs as native markdown and pushes markdown back to the same doc — same id, same URL, same sharing. The exact flags and the traps.Obsidian + PARA Method: a Second Brain That Doesn't Rot (2026)The exact Obsidian setup that survives real life: one inbox, four PARA folders, one weekly gate. Capture everything, find anything, maintain nothing.

Missing something?

If you looked for a resource and it was not here, that is worth telling us: it is how this shelf grows. Write to [email protected].

Tell us what's missing