Turn a document into memory
Upload a policy, a brief or a deck and turn it into short reviewable facts, without pasting the whole file into every conversation.
You have a brand guide, an onboarding checklist or a pricing sheet, and you want your Talent to work by it. Import it once. Every memory space accepts documents.
Import it
- Open Memory and pick the space you are filling: You, your department, or your workspace.
- Click Add to memory, then Import a document.
- Drop in one file. PDF, DOCX, XLSX, PPTX, Markdown or plain text, up to 10 MB. PDFs are read up to 50 pages.
- Wait while the file is read and classified.
- Review the candidate lines. Edit any of them, retype them, or untick the ones you do not want.
- Commit. The button says Save with a count if you can write directly, or Submit for review with a count if you are a member proposing.
A worked example
An agency imports its 9 page client onboarding SOP into department memory. It comes back as about a dozen lines: kickoff happens within three working days, the Notion project page is created before the kickoff call, invoices go out on the first of the month. The manager deletes two lines that are already stale, fixes the wording on one, and saves. From then on a Talent drafting a kickoff email or a Routine building the weekly client update works from the same rules.
This is deliberately lossy. It captures the durable, reusable knowledge in the document, not the document verbatim. Each line is capped at 200 characters. Read every candidate before you commit: they are model generated, so a line that is subtly wrong is your responsibility to catch, not the reviewer's downstream.
Keeping the source file
On your personal space you can also tick Keep document, which stores the extracted text as a private source document you can point your Talent at later. It is not injected into every turn. Your Talent reads it when you ask for it by name.
Shared spaces do not keep the file. They record where the facts came from, so the source shows up as provenance on each row.
What the result line means
After committing you get a one line summary. It can say any of:
- Saved for lines written straight into the space.
- Submitted for review for lines that became proposals because you are a member.
- Already known for lines that duplicate something the space already holds.
- Skipped, memory full for lines that hit the capacity ceiling. Those are reported, never dropped in silence.
- Skipped for lines the safety filter refused.
A batch never fails halfway. You always get a per line outcome.
Capacity is real. A shared space holds 100 current pages. Your personal memory has one 50 active page owner ceiling across every personal memory domain, not one allowance per section or surface. If a large import comes back mostly as "skipped, memory full", archive retired pages first, then import again.
What to check
- "Could not read that file." It is password protected, or it is a scan with no text layer. Export a text based version and try again.
- The file is rejected on size. The ceiling is 10 MB for one file. Split it, or import the section that actually holds the rules.
- You get two candidates instead of twenty. The document is mostly narrative, tables or images. Documents written as rules distill well. Slide decks and prose reports often do not.
- Nothing new to save. Everything in the document is already in the space. That is a pass, not a failure.
- You imported into the wrong space. Archive the rows in the space you filled, then import again from the correct tab. Nothing moves between spaces automatically.
Curate your department's memory
Give one team its own shared context. What managers edit directly, what members propose, and how company policy overrides a department page.
Check where a memory came from, and undo it
Trace any fact back to its source, read its version history, archive or restore a shared page, and permanently forget a personal one.