Where did my file go, across tools

Hannah is sure she attached Q3_forecast.xlsx yesterday. The file was 2.4 MB. At 4:17pm on the laptop she watched the paperclip sit next to her prompt, then asked for a one-page readout. This morning she is on her phone in the 8:40 standup. She opens a fresh chat and types “what’s the Q3 bottom line from the sheet.” No paperclip. The model answers $4.2M. That is last quarter. The live sheet in Shared Drive, still sitting at /Finance/FY26/Q3_forecast.xlsx, says $4.87M. She almost typed $4.2M into Slack.

This is Part 19 of Phase P, and Part 3 of Memory, projects, and files across AI tools. Part 1 split history, memory, and projects. Part 2, Uploading docs safely, covered what to strip before you attach. This part is the hunt: the UI hides chat attachments, project files, memory facts, Drive connectors, and desktop-app folders behind one paperclip. Next is Turning a messy folder into a working project. Related: AI setup from zero, accounts and Free vs paid, which product, files and office work, run it yourself, Learn, and Practical AI.

What you’ll learn

• Name the drawers a spreadsheet can live in: this chat, a project or Gem, memory, a connected Drive, a desktop folder, Downloads, and trash
• Tell a chat paperclip from a project knowledge file, and from a CSV the model generated
• Catch Memory quoting last quarter’s $4.2M when the 2.4 MB sheet is somewhere else
• Walk a hunt path on ChatGPT, Claude, Gemini, or Grok-style products (names move; confirm as of writing)
• Delete the extra copy on purpose, instead of re-uploading until you have four

Four drawers, one filename

The paperclip looks like one button. Behind it sit at least four cabinets, and they do not share a catalog. Hannah’s 2.4 MB workbook can sit in Monday’s thread, in a project, as a fact in Memory, as a Drive pointer, on a laptop folder she granted the desktop app, or in Downloads. The product will not print that map. You walk it.

A chat attachment is a file you clipped into one conversation. Scroll that thread and you should see a chip or a paperclip. Same account, later in the day: the chip is usually still on that thread. Open a new chat and the chip is gone. That is why Hannah’s Tuesday box looked empty. The model did not inherit Monday’s file.

A project file (Claude project knowledge, ChatGPT project files, Gemini Gem knowledge, similar buckets) sits on the job, not on one message. Chats inside that bucket can see it. Chats outside it cannot. Moving a chat into a project does not always copy the attachment into knowledge. Look at the knowledge list.

Memory is a list of facts the product may keep across chats: job title, preferred tone, “last quarter’s bottom line is $4.2M.” It is almost never the spreadsheet. Hannah’s model quoted $4.2M because that sentence sat in Memory from a Q2 recap. The 2.4 MB xlsx was never in that list. If you want the sheet, open the file.

Rule of thumb: If you cannot see a filename and a size, you do not have the file. A quoted number is a memory, a guess, or last quarter.

Yesterday’s thread and today’s empty box

Vendors train you to hit New chat. New chat is a clean slate for the thread. It is a terrible place to look for yesterday’s workbook. Hannah had 14 threads in the sidebar. The one she wanted was titled “Q3 dump (do not share).” She had renamed it because the default title was “Help with spreadsheet,” which is how every other dump was labeled. Search the sidebar for the filename, then for a word from the title you actually used.

On the phone, the same account usually shows the same threads. Open Monday’s laptop chat and the paperclip should be there. What will not follow you is a file you only dragged onto the desktop, or a folder you granted the desktop app. Drive’s picker stalled, so Hannah saved a copy to Desktop/Q3_forecast.xlsx and clipped that. The phone has no Desktop folder. The Shared Drive original follows her Google account. The desktop copy stays on the Mac until she puts it somewhere shared.

Generated files confuse the hunt. Monday’s model wrote a one-page CSV readout and offered a download. That CSV is a new object. It may land in ChatGPT’s Library (as of writing, OpenAI documents a Library at chatgpt.com/library for uploaded and created files), in Downloads, or as a Claude artifact. Standup needs the workbook. The CSV is a derivative with a different date and a different size.

Project files vs a paperclip

Claude’s help (as of writing) is blunt: anything you upload to project knowledge is used across chats in that project, and context is not shared across those chats unless it sits in the knowledge base. Hannah’s teammate later dropped the same xlsx into a Claude project called “FY26 forecast.” New chats in that project could see it. A standalone chat on her phone could not. Archiving hides the project in the archived list. Deleting it (unarchive first, then delete) removes the knowledge. Removing one file from knowledge is the smaller move if you still want the bucket.

ChatGPT Projects, as of writing, keep a file list on the project. Chat attachments stay on the chat. Library is a third shelf: files you uploaded or the model created, browseable on the web, separate from the daily attachment cap. If today’s box has no paperclip, spend 30 seconds in Library. Look for Q3_forecast.xlsx and for the readout CSV under a generated name. Delete what you did not mean to keep. Storage there still counts against the product’s file budget.

Gemini Gems (as of writing) take knowledge two ways. Upload from the device and you get a snapshot. Add from Drive and Gemini uses the latest Drive version when the file changes. Hannah’s Shared Drive workbook is the live one. If she clips a stale export into a Gem, the Gem can keep arguing $4.2M while Drive already says $4.87M. Open Drive. Check modified time. Then decide which copy the Gem should hold.

Memory can quote $4.2M without holding the sheet

This is the part that makes people think the file followed them. ChatGPT Memory, Claude memory on paid plans, and similar features store short facts. OpenAI’s Memory FAQ (as of writing) describes useful context from chats, files, and connected apps, plus a summary you can edit. To fully delete something, you may need to clear it from chats, files, the summary, and connected apps. Claude keeps project memory separate from non-project memory on the plans that have it. None of that is a folder of workbooks.

Hannah opened Settings, then Memory. Line 7: “Hannah’s last quarter bottom line is $4.2M.” She had said that out loud in a June recap chat. Tuesday’s new chat had no paperclip, so the model reached for the saved line. $4.2M sounded confident. It was a quarter late. She deleted the line and went back to the sheet. Stable facts belong in Memory (“I work in FP&A, write in bullets”). A number that moves every close belongs in the workbook. Attach the workbook when you need it.

Temporary or Private chats try not to file things. Names move. Grok’s help (as of writing) describes Private Chat as history you cannot see, deleted from systems within about 30 days unless they must keep a safety copy. Wrong drawer if you will need the attachment tomorrow. Right drawer for a messy paste you do not want in Memory. Hannah’s forecast did not belong there.

Drive, desktop folders, Downloads, trash

Connectors are pointers, not copies. Gemini with Workspace connected can @ a Drive file. ChatGPT and Claude have shipped Drive, Box, and similar connectors on some plans; labels move, so check Settings the week you rely on them. The live file stays in Drive. Delete it there and the chat cannot honestly claim it still has the 2.4 MB original. Disconnect the connector if you no longer want that product reading the folder. Disconnect is not emptying trash.

Desktop apps add a fifth physical place. Claude Cowork (as of writing) reaches local files through the Claude Desktop app, for folders you grant. ChatGPT’s desktop Work-style surfaces can open a local folder after you permit it. Those files live on that Mac or PC. They do not teleport to the iPhone thread. If Hannah granted ~/Finance/FY26 on the laptop, the hunt on the phone will never see that path. Open the laptop. Confirm the 2.4 MB file is still there. Decide whether the source of truth is Drive or disk.

Downloads and trash are boring and they win hunts. Models offer “download this table.” Browsers drop it in Downloads as Q3_forecast.xlsx, Q3_forecast (1).xlsx, or export.csv. A frustrated click can send the original to Trash. Hannah found nothing in Downloads and nothing in Trash. The original had never left Drive. The extra copy was still on Desktop. Two real files, one Memory fact, one missing paperclip. That is a successful hunt.

Hunt path when the paperclip is gone

Walk the drawers in this order so you do not re-upload a third copy while the first two sit in Drive and on Desktop. Stop when you have a filename, a size, and a modified time that match.

1. This chat: scroll for a paperclip. A brand-new thread will not hold Monday’s sheet.
2. Yesterday’s chat: sidebar search for Q3_forecast and for the title you used. Confirm 2.4 MB.
3. Project / Gem / Library: list files. Download one and read the date.
4. Memory: read saved facts. Delete the stale $4.2M. Do not expect an xlsx here.
5. Connected Drive: open the live file. Size and modified time beat whatever the chat quoted.
6. Desktop app folder: only on the computer you granted.
7. Downloads, then Trash. Then stop. Re-attach on purpose if you still need the chip in a new chat.

Paste this into a note and fill it once. The point is a location, not a vibe.

FIND THE FILE
Name: Q3_forecast.xlsx
Size I remember: 2.4 MB
Vendor today: [ChatGPT / Claude / Gemini / Grok]
Date I think I attached: [Mon 4:17pm]
Account email: [the one I actually logged in with]

1. THIS CHAT
   Paperclip or file chip here? [yes/no]
   If no, this thread is new. Do not trust quoted numbers.

2. YESTERDAY'S CHAT
   Sidebar search: Q3_forecast
   Title I used: [Q3 dump (do not share)]
   Chip present, size matches 2.4 MB? [yes/no]

3. PROJECT / GEM / LIBRARY
   Bucket name: [FY26 forecast / none]
   File listed in knowledge or Library? [yes/no]
   Downloaded copy date modified: [____]
   Generated CSV or artifact (not the xlsx): [name or none]

4. MEMORY
   Stale fact that quotes a number? [e.g. $4.2M]
   Deleted or corrected? [yes/no]
   Memory is facts. It is not the workbook.

5. CONNECTED DRIVE
   Path: [/Finance/FY26/Q3_forecast.xlsx]
   Live size and modified time: [2.4 MB, Mon 3:51pm]
   Connector still on? [yes/no]

6. DESKTOP APP LOCAL FOLDER
   Computer: [Hannah's Mac]
   Granted folder: [~/Finance/FY26 or Desktop]
   File on disk? [yes/no]  (will not follow the phone)

7. DOWNLOADS + TRASH
   Downloads match: [none / Q3_forecast (1).xlsx]
   Trash / Recycle Bin: [empty / restored]

Found in: [drawer]
Action: [open that copy / re-attach on purpose / delete extras / fix Memory]

What that checklist does: it makes you write a path. Hannah’s filled copy said “Found in: Monday chat plus Drive plus Desktop. Memory had $4.2M. Phone chat had nothing.” Once you can say that out loud, the missing paperclip is explained. You still pick which copy standup will use.

Where attachments live, by product (as of writing)

UI names move. Treat the table as a shape, then click the vendor’s help the week you hunt. Same four drawers, different labels.

Two extra rails show up in bills and in hunts. The email you signed in with is the cabinet you search (Part 7). API file stores (OpenAI, Anthropic, xAI console) are not your consumer chat. If someone uploaded via a key, look in the console Files page, not in the phone app. Hannah did not have that problem. She had a new chat, a Memory line, and two real copies of the same 2.4 MB name.

Worked example: 2.4 MB, $4.2M, no paperclip

Hannah’s hunt on Tuesday at 8:41, before standup ended. Same filename everywhere. Only two rows are the workbook.

Fix, in order. Delete the Memory line so $4.2M stops walking into new chats. Use Drive as the source of truth for standup. Attach that file (or @ it) in a thread you intend to keep, or put it in the FY26 project knowledge once. Delete or rename the Desktop duplicate so next Monday’s picker cannot grab the wrong one. Leave the CSV labeled as a readout, or delete it if nobody needed the download. Do not start a third chat and re-upload “just in case.” That is how you get Q3_forecast (1).xlsx in Downloads and a second Memory fact.

If she had been on Gemini with Drive connected, the right move would have been to confirm the chat pointed at the live Drive file and read B12 herself. If she had been in Claude Cowork on the Mac, she would have opened the granted folder and skipped the phone hunt. Same drawers. Different door.

Common mistakes

• Starting a new chat and treating a quoted number as proof the sheet is attached.
• Asking the model “where did you put my file?” instead of searching the sidebar, project list, Library, Drive, and disk.
• Confusing a generated CSV or artifact with the 2.4 MB workbook.
• Assuming Memory stores files. It stores sentences. Hannah’s $4.2M was a sentence.
• Hunting on the phone for a folder you only granted the desktop app.
• Re-uploading until you have Drive plus Desktop plus two chats plus Downloads, then not knowing which one finance will audit.
• Deleting the chat and thinking Library, project knowledge, Drive, and Memory all went with it. They often do not.
• Mixing grok.com, Grok-in-X, and an API Files bucket, then searching the wrong door.

How to practice this week

Pick one real file you attached in the last seven days. Fill the checklist. You want a filename, a size, and one source of truth. If Memory has a number from that file, delete or correct the fact. If you find three copies, keep Drive (or the shared disk) and remove the extras. Next: Turning a messy folder into a working project. Previous: Uploading docs safely. Setup map: AI setup from zero and Learn.

Quick recap

• Hunt in order: this chat, yesterday’s chat, project or Gem or Library, Memory, connected Drive, desktop folder, Downloads, trash.
• No paperclip in a new chat means you do not have the file, even if the model quotes $4.2M.
• Memory holds facts. Drive and disk hold workbooks. Desktop folders stay on that computer.
• Delete extras on purpose. Re-attach once, into the thread or project you will actually open tomorrow.

Sources

• OpenAI Help: File storage and Library in ChatGPT (uploaded and created files, Library on web, as of writing)
• OpenAI Help: File uploads FAQ (chat vs custom GPT retention)
• OpenAI Help: Memory FAQ (saved facts vs chats, files, and connected apps)
• OpenAI: ChatGPT for macOS (desktop app; local folder behavior depends on the Work-style feature you have)
• Anthropic Help: How can I create and manage projects? (project knowledge vs chats, archive then delete)
• Anthropic Help: Get started with Claude Cowork (desktop local folders you grant)
• Google Help: Use Gems in Gemini Apps (device upload vs Drive, latest Drive version)
• Gemini (app surface; re-check connectors in Settings)
• xAI: Grok website / apps FAQ (chat uploads, grok.com/files, Private Chat, Data Controls)
• Grok (consumer app; grok.com vs Grok-in-X are different doors)
• AMS: Memory, projects, and files across AI tools

Merch on Etsy

Open store →

Boxplot Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Box Plot, Whisker Plot View on Etsy → Y Hat Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Y Pred Mouse Pad View on Etsy → Good Cheap Fast White Ceramic Coffee Mug, Data Science Mug, Data Mug, Analytics Mug, Statistics Mug, Programming Mug, Gift Mug, Coffee Mug View on Etsy → Naive Bayes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Bayesian Mouse Pad View on Etsy →