Manage memories and files

Understand notes and files

Memories combines two reusable context types:

• Memories are short facts the Tap Agent saves only when you explicitly ask.
• Files are uploaded sources that Tap can parse and search as evidence.

Both can use personal, team, or Brand scope. Scope controls where the context resurfaces; it does not publish the content to a supplier.

Upload a file

Open Memories and use the file panel, or attach a file in an Agent conversation. Choose the destination:

• Me for personal working material.
• Team for context everyone in the buyer workspace can reuse.
• Brand for material tied to one Brand.

Tap checks whether an identical stored file can be reused before uploading another copy. A reused file keeps one authoritative parse instead of duplicating work.

Follow processing states

A file moves through:

• Uploading while the bytes are being saved.
• Parsing while searchable text and a summary are prepared.
• Parsed when the Agent can search it authoritatively.
• Error when ingestion failed.

Do not assume the Agent read a file that is still uploading, parsing, or in error. Use the available retry or reprocess action. Legacy spreadsheet files can be recovered into a new parsing attempt when Tap detects the old state.

Open a file to review its title, summary, tags, scope, Brand, size, type, and processing details. Download the original when you need to compare Tap's summary with the source.

Use citations and search

Ask the Agent to search saved files before relying on them. It should cite the source file and separate extracted facts from inference. A citation proves where the fact came from, not that the source is current or correct.

Changing a file scope changes who can retrieve it. Moving a file to a Brand requires choosing the exact Brand.

Maintain memory notes

Open a memory to edit its title and tags. Link related memories to build the visible graph, and unlink a relationship that no longer helps. Links organize recall; they do not merge note content.

Ask the Agent to replace an obsolete active note instead of creating a duplicate. Forgetting a memory permanently deletes that saved note and requires an explicit request. It does not delete an uploaded source file with similar wording.

Recover safely

• Parsing failed: retry the file. If it fails again, upload a clean supported version.
• Wrong scope: update the scope and Brand, then confirm it appears under the intended filter.
• Duplicate file: keep the reused authoritative record rather than uploading renamed copies.
• Source changed: upload the new version and retire reliance on the old one. File contents are immutable evidence.
• Bad citation: open the original file and compare the cited passage before acting.
• Missing memory: clear scope, Brand, status, and search filters before assuming it was deleted.

Related guides

• Work with the Tap Agent
• Manage Brands, Products, and creatives