A shared knowledge store of files and documents — one Library per human, reachable from every one of their agents, with streamed uploads, deterministic folders, and best-effort text extraction so content becomes searchable without ever blocking on it.
One Library per human
The Library belongs to you, not to a single agent. Whichever agent you're talking to, uploads and searches land in the same place — add a file while working with one agent and any other agent of yours can find it later. Visibility then decides how far it travels:
- Private (default) — visible to you across all your agents, not to anyone else in the company.
- Company-wide — explicitly shared with everyone in the company, the same explicit-sharing step used for memory (see Memory) — though private here means visible to you across every one of your agents, not scoped to a single one the way a private memory is.
Two ways to add a file
- Ask your agent — an agent can upload a file it has access to directly from the conversation. Auto-allow only covers the thread's own working directory, since anything there was necessarily produced by that thread; a file anywhere else — including a folder approved for ordinary reads as an extra directory — still prompts once, with once/this-thread scopes, before it can leave as an upload (see Security). Nothing is uploaded without that consent.
- The Library button — drop one or several files yourself from the left rail, through your OS's native file picker. Because you're the one choosing the files through the system dialog, no separate read permission is needed for this path.
Either way, the file is streamed straight to storage — there's no size-inflating encoding step, and once accepted it's already downloadable. A small agent-authored note or snippet can also be published as text directly, without going through a file upload at all; this text path is capped to a much smaller size than a file upload, so it stays a place for short authored content, not a document store.
Updating a file in place
When an agent revises a document it already uploaded — a new version of a deck, a corrected report — it can replace that file's content instead of adding a second copy. The file keeps its place in the Library, its folders, and its share link: a link you already sent now serves the new version. The previous version is kept by storage rather than overwritten, which is why in-place replacement only runs once your administrator's storage test has confirmed that versioning is on; otherwise the update is refused and the current file stays as it is. Only you can replace your own files — a colleague who can read a company-wide file cannot change it. An agent that tries is told the file belongs to another account, rather than that it cannot be found.
From a working document to a published copy
The Desktop document workspace keeps local work separate from the Library. Ask for one self-contained HTML file with embedded styles and supported assets, or a self-contained export of an existing multi-file document. Revise that same file in the conversation. You can read its completed version in your local browser without publishing or creating a share link.
Adding the displayed version to the Library is explicit and private by default, in the current workspace. Subsequent local edits stay unpublished until you explicitly update the associated Library entry. That update changes what an existing valid share link serves on its next load; editing or opening the local file alone never does. A failed or uncertain transfer is not confirmation that the new version was published: check the result rather than blindly creating another entry.
Deterministic folders
A popup upload asks you to name one destination folder before it will start — a project, a client, whatever fits how you think about your files; there's no unlabeled option on this path. An agent-driven upload instead inherits whichever folder(s) the current conversation is already tagged with, landing in Unclassified only if that conversation has none. Folder names are plain labels attached at upload time, not a browsable tree to manage separately: you see them as a badge on each artifact and can search across everything with full-text search, regardless of folder.
During a client mission
Files an agent creates while working on a client mission are stored in that client's workspace, not in your own. In the Desktop app, opening the Library follows the conversation you are reading: your own workspace for a Home conversation, or the client's workspace for an authorized mission conversation. Without a conversation displayed, it follows the client selected in the left rail, or your own workspace when none is selected.
The Context selector lets you temporarily choose your own workspace or an accessible client workspace, including clients where another agent of yours is placed. This changes only the Library, not your conversation, active agent or sidebar filter. Closing and reopening the Library restores the conversation's context. If a mission cannot be accessed, the Library says so rather than silently showing your own files; you can explicitly choose another available context.
The selected context applies to files you read and add. The upload panel names the destination before you choose files. An upload already started keeps its original destination: its progress and Cancel control are visible only while that destination is selected in the workspace where you started it. Switching away or closing the Library does not cancel it; returning to its context restores its ongoing progress.
When the client lets your mission read its company-wide files, your agent can read them but cannot change, share or delete them: only the person who added a file can, from their own account in that workspace — even if that person is you under your client account.
Once the mission has ended, its files stay with the client and can no longer be opened from your Desktop (see Cross-workspace missions).
Previewing files
The Desktop Library shows a safe inline preview for common text, image, diagram, HTML, and PDF files. PDF pages stay inside the Library with page controls; detailed or high-resolution pages remain visible while the preview keeps its on-screen canvas bounded. You can still download the original file at any time.
Sharing and reading a published document
In the Library entry, enable public sharing, choose the link's duration, then confirm activation and copy the link. Company-wide visibility and a public link are separate choices: a private entry is not publicly readable until you activate its link. Anyone holding an active link can read it without signing in, so only send it to people who should receive the document. The sharing controls show the expiration and let you deactivate the link early. Opened in a browser, a shared spreadsheet (CSV, TSV, Excel or OpenDocument) downloads as the file itself, byte for byte, ready for Excel or Numbers. A script gets the same file when it asks for that format (for example Accept: text/csv). Text and code open as a readable page, and other files show a download button.
A valid link to a supported self-contained HTML document opens its published static layout, including supported embedded assets, rather than its source code. The recipient has a read-only page, not an editor or access to your conversation, local files, or unpublished changes. Scripts and interactive features do not run in this reading view, and linked external resources are not loaded. An unsupported or oversized document may instead show an explicit preview-unavailable explanation; an uploaded file is not a guarantee of a faithful preview.
Download retrieves the latest published version at the time of the click. If the author updates the Library entry after you open the page, the download can be newer than the document still displayed. Reload the page to read the current published version. The protected preview does not turn a downloaded file into a protected browser view.
Expired, deactivated, or otherwise unavailable links show a neutral unavailable page without the document or a download action; ask the sender for a new link. Expiration and revocation prevent subsequent reads and downloads through that link. They cannot retract content already received, including an open page, a downloaded file, or a copy someone has saved or forwarded.
Processing and degraded states
An uploaded file goes through up to three states, and it is downloadable at every one of them:
- Processing — the file has been accepted and stored; it can already be downloaded and shared. Text extraction hasn't run yet, so it isn't searchable by content.
- Ready — extraction succeeded; the file is now searchable by its content, not just its name, and agents can read the extracted text directly when they use it in their work. The original download remains available alongside that readable form.
- Degraded — extraction couldn't produce usable text (an unsupported, encrypted, or corrupted file, for example). The original file remains exactly as accepted, fully downloadable and shareable — it's just not searchable by content.
Storage and extraction are deliberately two different moments: once a file has been accepted and stored, it's already downloadable, and making it searchable is a best-effort step that happens afterward and never blocks or reverses that acceptance. Acceptance itself can still be refused before that point — invalid metadata, an unnamed folder, or a rate limit reject the upload outright, the same way permission would.
Best-effort extraction
Extraction looks at what a file actually is rather than trusting its extension, and covers plain text, common office and OpenDocument formats, and PDFs — including scanned PDFs and photographed documents, read through OCR. Anything extraction can't handle simply falls back to degraded rather than being rejected.
Related
- Memory — the same private-by-default, explicit-sharing pattern applies to memories, best practices, skills, and command-safety rules, though a memory's private default is scoped to one agent rather than to you across all of them
- Security — permission scopes and consent for sensitive actions
- Desktop app — where the Library sits in the interface