Turn the team's Google Drive into a searchable, linked knowledge base that Claude can read in full, scoped automatically to what each person is allowed to see.
Everything the team knows is scattered across hundreds of documents. Asking an AI assistant to search Drive gets you one keyword query at a time and a few snippets. Nobody has read all of it, and nobody ever will.
The tool reads every document once and writes short, linked notes. That reading is the expensive part, and it happens a single time for the whole team.
Every claim points back to the document it came from. Nothing is invented, and disagreements between documents are flagged rather than smoothed over.
When a teammate installs it, it checks their own Google permissions and keeps only what they can already open.
Four steps. The first three happen once, on the team lead's machine.
Every document becomes a plain text file on the computer. Read-only: nothing in Drive is ever changed.
Hundreds of readers work in parallel, one document each, turning it into a handful of short notes. Meeting invitations and logistics get skipped.
One librarian files every note, merges the duplicates, and links what belongs together. This is what turns a pile of notes into knowledge.
Each teammate installs it and signs in. The tool checks what they can open in Drive and keeps only that. It then updates itself every night.
Open Claude Code in a terminal, paste this, and it will do the rest: fetch the tool, install what it needs, and open your browser to sign in to Google.
No. One paste into Claude Code, one Google sign-in, and a few clicks in a browser.
No. Your copy is built from your own Drive permissions, checked file by file.
It syncs each night and adds anything new you can see, so it stays current on its own.
The reading is the only real cost, and the team lead pays it once. Installing is free.