Most of what people need to learn doesn't start from nothing. It starts from a PDF someone sent you, a set of lecture slides, a research paper you're supposed to have an opinion on by Thursday, a policy document at work. The Library exists for exactly that material: the stuff you already have, already trust, and just need a better way to actually get through.
Why a library, and not just another upload button
Uploading a file and generating a brand-new course from it is useful when you want a structured path built around the topic. But sometimes that's not the job. Sometimes the file itself is the thing you need to understand, word for word, not a course inspired by it. The Library is built around that second case: instead of turning your material into something else, it gives you direct ways to work with the file as it is, listening to it, questioning it, condensing it, and comparing it against something else you've also brought in.
Read it, or have it read to you
Not every file gets read the same way, and not everyone absorbs a page of dense text best by staring at it. The Library can read a file aloud, which matters more than it sounds like it should: a long document becomes something you can go through on a commute, while cooking, or during a walk, instead of only at a desk with your eyes on a screen. It's the same material, just available through a channel that fits the moment you actually have available.
Ask about it instead of hunting through it
Two related but different tools live here. Chatting with a file is for open-ended exploration: talking through what a document is actually arguing, working out how one section connects to another, thinking out loud about it the way you would with a colleague who'd also read it. Asking a direct question is for the narrower case: you need one specific answer, a figure, a clause, a definition, and you don't want to reread three pages to find it. Both pull from the same file, but they solve different moments: one is for understanding, the other is for retrieval.
- Chat: for working through what a file means, section by section, in your own words.
- Ask: for pulling a specific fact or detail out of a file without rereading the whole thing.
- Both stay grounded in the actual file, not a general answer that happens to sound plausible.
A summary when you don't have time for the whole thing
Sometimes the honest goal isn't deep understanding, it's knowing enough to decide whether the full document is worth your time at all. A summary gives you that first, compressed pass: the shape of the argument or the content before you commit to reading every page. It's not a replacement for reading something you actually need to know well, but it's the right tool for deciding what deserves that level of attention in the first place.
Two files, side by side
Some material only makes sense next to something else: two drafts of the same document, a set of lecture notes against the textbook chapter it's based on, two papers making competing claims about the same question. Reading them one after another and holding the differences in your head is where most of the actual comparison gets lost. Split view puts two files on screen at once, so the comparison happens where it should, in front of you, instead of in memory.
None of these tools exist to replace a generated course. They exist because a lot of real learning starts with material you didn't write and can't rewrite, and the Library's job is making that material as usable as anything built for you from scratch.