File storage for your agent, or an assistant that reads your files?

It is storage built for programs, not for people clicking through folders. Blaxel describes its Agent Drive as "A distributed filesystem for trillions of files" that lets agents "store and share files across sessions concurrently", and lists it as a private preview. agentdrive.sh calls itself "The artifact workspace your agents share", says it is in "Private beta", and lists a free tier of 1 GB. Fast.io says you can "Connect your agents over MCP, keep the files they work on in one place, and share the results with your team", from $9.99 a month. All checked on 14 October 2026.

What this kind of storage does well: agents write and read files through code, each agent gets its own space so they do not overwrite each other, and the results can pass to the next agent or to a person. One warning: at least three different products use the name AgentDrive, so read the company's own page before you sign up. The same split exists for email, covered in an inbox for your agent, or an assistant in your inbox.

Ask whose files they are. Agent storage holds new files that an agent makes. A reading tool works on files you already own, where they already live, through a permission you grant on Google's or Microsoft's own screen.

Google itself offers the reading kind for developers: its Drive MCP server, a Developer Preview whose page was updated on 9 October 2026, gives a program tools such as search_files and read_file_content.

If you are building an agent that writes reports and passes files along, you need agent storage: access through code, a space per agent, and a way to share results.

If your contracts, notes and records sit in Google Drive or OneDrive and you want answers you can check, you need a tool connected to your Drive. Ask it "Can we end the cleaning contract early?" and a good answer says "Yes, with 60 days' notice", then opens the contract at the clause: "Either party may end this contract with 60 days' written notice."

If you need both, keep them apart. One is the agent's workbench; the other reads your own files. Mixing them leaves copies of your documents in places you will forget to check.

Google's Drive permissions page (updated 3 September 2026) lists two you will meet. drive.file is non-sensitive: it covers files "that you open with an app or that the user shares with an app". drive.readonly is restricted: "View and download all your Drive files." Google tells developers to prefer the narrower one when it is enough, and an app that reaches restricted data through its own servers must go through a security assessment every year, with some exceptions.

The choice sets how far a mistake can reach. Whole-Drive reading is what makes "search all my files" work, and it also puts every file within reach. A careful tool reads only what the question needs, names what it used, and asks before it deletes anything.

A good answer names the file and shows the passage. You click, the document opens at that spot, and the words are marked. If a tool only says the answer came from your Drive, with nothing to open, treat the answer as a draft and check the file yourself.

There is a second reason to check. A file you did not write can contain text placed there to mislead a program. Google's Drive MCP page warns: "When you expose a language model to untrusted data, there is a risk of an indirect prompt injection attack." OWASP ranks prompt injection first among risks for applications built on language models (2025 list). Opening the cited passage is the simple check; more in citations you can open.

Tatsulok works on your own files, where they already live. You connect Google Drive or OneDrive under Extensions, on the Drives card; the connection is in Beta, and Google shows its unverified-app screen first, where you choose Advanced to continue. Tatsu searches, lists and reads your files and cites the ones it used. You can bring a file or a folder (up to 200 files per run) into your Tatsulok library; there, a citation opens the document at the page with the passage highlighted. Tatsu can also create files and folders, and it moves a file to the trash only after you confirm.

Said plainly: Tatsulok asks Google for drive.readonly and drive.file, so it can read your whole Drive and change only files it creates with you. For OneDrive it asks Microsoft for Files.ReadWrite. You can disconnect in Extensions at any time; for Microsoft, also remove Tatsulok in your Microsoft account, because Microsoft does not let an app withdraw its own permission.

Tatsulok is not a drive for agents. It keeps no storage for agents' output and offers no API for programs you build; for that, use one of the products above. To connect your files, see how to let an assistant answer from your Google Drive.