ClaudeDrive

Two people can ask Claude the same question and get different answers, because each answer only uses the files shared with that person.

You drop in a team's documents and share a folder with the people who should see it. Then anyone you shared it with can ask their own Claude to pull the hiring plan. The answer only uses what that person may see, with a link to the document behind each line.

If a file isn't shared with you, nothing from it shows up in your answer, and the leak tests are strict about that. One plays someone brought in only for Project B and fails the build if a single line about Project A comes back. A "[redacted]" counts as a failure too.

It also never guesses who's who. If two people named Mike were in a meeting, it credits the work to neither until a person says which Mike, since a wrong guess could let the wrong person read a file.

It connects to Claude through a remote MCP server I wrote. MCP is the standard way Claude plugs into outside tools, and setup is pasting one address into Claude's connector settings. A GitHub App brings in a team's activity, so Claude can say what changed today with a source link on each point.

Building it

I built it in five weeks and still run it. The repo runs from May 31 to July 5, 2026: 752 commits, all under my name, and Claude is listed as co-author on 533 of them.

The first commit message says Codex, OpenAI's coding agent, had already spent about 26 rounds attacking the code. That same afternoon, I made the leak tests a required check on every change.

I'd set it up in Fly.io's Boston region, which turned out not to take new apps, so 74 minutes in, I moved it to Virginia.

Stack

Languages

TypeScript

Product

Next.jsGitHub

Models and agents

MCP

Data

Postgres

Infrastructure

Fly.io