Searching your own documents: what a library actually does
An attachment and a library are not the same tool
Attaching a document to a conversation solves exactly one question, in exactly one chat, and then the document is gone again. That is fine for a one-off. It is useless for the thing people actually want, which is: this body of material is the ground truth for my work, and I want to be able to ask it anything, from any conversation, for months.
A library is that. You upload contracts, specs, research, spreadsheets or notes once; StickyFriend reads each file and indexes it; and from then on any chat you point at that library can search it and quote from it.
What happens when you upload
A file goes through three visible stages, and the visibility is the point:
- Read. The text is extracted from the file. You watch each file’s status while this happens rather than staring at a spinner over the whole batch.
- Indexed. The content becomes searchable. Until this finishes, a chat pointed at the library will not find it.
- Failed, with a reason. If a file cannot be read, it is marked Failed and the reason is on screen, along with what would fix it. It is not quietly added as an empty document — which is the failure mode that matters, because an empty document does not error, it just makes the library confidently incomplete.
Answers name the file
When an answer comes out of your library, it tells you which file it came from. This is not decoration. A quote you can trace is a quote you can check against the original clause, the original spec, the original number — and checking is the entire reason you put your own documents in front of an AI rather than trusting its general knowledge.
Try this on day one
Ask your new library a question you already know the answer to, and look at which file it cites. Two minutes of that tells you more about whether the upload really worked than any progress bar.
Which chats can read it — the default is none
Each conversation picks which libraries it may read. The library button sits beside the Smarter toggle, above the message box, and shows the count on its face, so you can always see whether the chat you are in is reading your documents.
A chat with none selected reads nothing of yours and costs nothing extra, and that is the default. Pointing a chat at a library is a deliberate act, not something that happens because you once uploaded a file.
What gets read without OCR, and what needs it
This is the part that is usually explained badly, so plainly:
- Text extraction covers more than people expect, and it is on every plan that has libraries at all: PDFs with a text layer, Word, Excel, CSV, HTML and plain text.
- Slide decks do not need OCR and never did. A
.pptxor.pptis read as text on every library plan — slide text, table cells and speaker notes, one slide at a time. OCR is only called for an individual slide that turns out to be a picture with no text on it. If you have presentations to put in a library, Silver reads them. - OCR is for scans and photographs. Scanned PDFs, photographs of pages and plain images need a model to look at the image. That runs on Gold and Diamond.
- Silver is text extraction only, and says so before you upload. A file with no readable text layer is refused, or marked Failed with the reason and the upgrade named.
OCR sits on the bigger plans because it is the most expensive step in the pipeline — a model call per page or per image — not because of an arbitrary tier line.
What each plan allows
- Bronze — no libraries at all. Libraries are a paid feature, and the block is enforced on the server rather than hidden in the interface.
- Silver — 3 libraries, 200 files, 2 GB. Text extraction only.
- Gold — 15 libraries, 2,000 files, 20 GB, with OCR.
- Diamond — 50 libraries, 10,000 files, 50 GB, with OCR.
Libraries, files and storage are metered against your plan on the Libraries screen and in the extension, with a warning before you reach the ceiling instead of a refusal after it.
How to organise them so they stay useful
- One library per body of knowledge, not per file. “Supplier contracts” is a library. “Contract with the supplier” is a file. Three libraries goes a long way when they are drawn along real boundaries.
- Use folders inside a library for the structure you already think in — by year, by client, by version.
- Keep the noisy stuff out. A library that contains eleven drafts of the same document will cite you a draft. Upload the version you would actually act on.
- Point a chat at the narrowest library that can answer it. It is faster to read and much easier to sanity-check the citation.
The honest limits
Libraries do not make the AI infallible, and they do not read a document you did not upload. A citation tells you which file an answer came from; it is still worth opening that file when the answer is going to cost you money. And on Silver, a folder of scanned PDFs is going to tell you it cannot read them — deliberately, and before you have built a workflow on top of a library full of blanks.
The full plan detail is on the pricing section, and the FAQ answers the OCR question in one paragraph if you want it even shorter.