The Saanora Library: every chat, upload, and document Mark made
Files you send Mark and files Mark builds for you used to live wherever the conversation left them. The Library puts all of it on one page — searchable, filterable, and traceable back to the chat it came from.
You asked Mark for a deck three weeks ago. You know it was good. You have no idea which conversation it was in.
That is the failure the Saanora Library fixes. Every file connected to your account — the ones you uploaded and the ones Mark generated — now lives on one page, instead of being scattered across however many chats you happened to have them in.
Uploads and outputs, in one place
Two kinds of file end up in Saanora, and until now they behaved completely differently.
Files you upload are attachments: the PDF you asked Mark to read, the spreadsheet you wanted checked, the photo of a whiteboard. Files Mark generates are outputs: the Word document, the PowerPoint deck, the Excel sheet, the PDF it built when you asked for one.
The Library treats them as one collection with a filter between them, because when you are hunting for something you rarely think in those terms. You think “the thing about the Q3 numbers”.
Grid, list, and filters that match how you look for things
The page is deliberately small. Search by name, filter, and choose how to look at it:
- Grid or list — grid when you are recognising something by shape, list when you want dates and sizes.
- Filter by source: everything you uploaded, or everything Mark made for you.
- Filter by type: documents, spreadsheets, presentations, PDFs, images, or the rest.
- Every file shows the conversation it came from, so one click takes you back to the context.
Open it without downloading it
Clicking a file in the Library opens the same canvas the chat uses. Word documents, PDFs, plain text and code render right there, side by side with the page, and anything a browser genuinely cannot display gets an honest download panel rather than a broken frame.
Which means the Library is not a list of names you have to download to identify. You can look before you commit.
An honest note about how it finds your files
One implementation detail we would rather say out loud than hide, because it explains a limit you might otherwise trip over.
Generated documents are stored under keys that contain no user id — nothing about the stored object says whose it is. So the Library finds yours the only way it honestly can: by reading the download links out of your own messages. If it appeared in your conversation, it is yours, and it appears here.
The alternative would have been to list the storage bucket and show everyone's documents to everyone. That is exactly the class of bug we spent a day closing elsewhere in the product, and it was not going to be reintroduced for a file browser.
The Library sits in the sidebar, directly under New chat, on the web and on the desktop app. It fills up on its own — there is nothing to file, tag, or organise.