Stop hunting through folders.

Stop hunting through folders. Ask for the file by what it is.

• "Where is the Acme proposal I wrote last summer?"
• "Pull up the latest version of the pricing sheet."
• "Find me the doc where we listed the Q3 priorities."
• "Read the brief and tell me what we promised."
• "Has anyone shared anything with me about the Meridian project?"

Google Drive is a great filing cabinet and a terrible search engine. Presence searches across file names and the text inside your documents — so the proposal you remember as "the Acme one" comes back even if it is titled "Q3 strategy collab v3 final FINAL."

Once Presence finds the right file, it can read the contents. Google Docs come back as structured text. Sheets come back as tables it can reason about ("which clients have unpaid invoices?" against a billing sheet). PDFs are extracted. Slide decks have their text pulled out.

This makes Drive a first-class part of cross-tool synthesis — when Presence prepares a meeting brief, it pulls the relevant Drive docs alongside email and calendar, and weaves the whole picture together.

Found something worth keeping? Ask Presence to save it and the file comes across into your vault — a Doc as an editable document, a Sheet as a spreadsheet, a deck as a PDF — with a plain-text copy alongside, so it stays searchable and Presence can find it again later.

Presence reads from Drive and, on request, can create a plain-text file there. Day to day, though, it writes into your vault by default — plain markdown is easier to keep tidy and easier to take with you. Richer formatted write-back into Drive is something we may add for teams who live there; for most people, vault-first is the better pattern.

Authentication is through Google OAuth. The token is stored encrypted and revocable in one tap. Scope is read-only across your Drive — Presence cannot delete or move anything. The first time an agent reaches for your Drive it asks; you grant once, it remembers, and you can withdraw access any time from the Access tab.