Google Drive for AI agents open source · works with Claude Code & Cowork

Your agent knowswhat their agent knows.

One shared folder for your whole team's agents. What your Claude writes, their Claude reads — in seconds, as real files.

No credit card. You won't touch a terminal — your agent sets it up.

Snow — Claude 2:14pm

Write up the Q3 findings in the team wiki.

Claude Saved to wiki/research/q3-findings.md 🔗

Priya — Claude 2:18pm

What did we learn from Q3?

Claude Per q3-findings.md — churn is concentrated in self-serve.

Marco — Claude 2:31pm

Draft the board update.

Claude Pulling the churn numbers from q3-findings.md

One file. Three machines. Nobody pasted anything.

Works with

Claude CodeClaude CoworkCodexHermesGeminiObsidianGoogle OKFgbrain

…and anything else that writes a file.

WHAT YOU GET · SHARED BRAIN

A shared brain your team's agents maintain.

Written as a side effect of working. Read before every task. It gets better every time anyone works.

🔒 app.beardrive.ai/p-b12fd122/wiki/research/q3-findings.md
wiki / research / q3-findings.md Claude on Snow's machine · 2:14pm · 14 reads (3 agents) / 30d

Q3 findings

Written by Claude on Snow's machine · reviewed by Priya

Churn is concentrated in self-serve accounts that never reach a second seat. Everything below follows from that one fact.

Headline numbers

METRICQ2Q3CHANGE
Net revenue retention104%97%−7 pts
Self-serve churn4.1%6.8%+2.7 pts
Median seats at churn1.01.0

What we learned

  1. Single-seat accounts churn 4× faster. Accounts that never invite a teammate leave within 40 days on average.
  2. Price is not the driver. Only 6% of exit surveys mention cost; 41% say they never really got started.

The file from the hero, opened in the hub — with who wrote it, when, and how many agents have read it since.

Same loop for research, client deliverables, and sales docs.

WHAT YOU GET · SHARING

The link is born with the file.

Your agent hands you a link the moment it writes. Gated to your team by default — or public, in one more sentence.

Snow — Claude 3:42pm

Just got off the Northwind call — update the deal page.

Claude Updated wiki/deals/northwind.md🔗 — added the call notes, moved the stage to Negotiation, pushed the close date to Aug 29.

🔒 Team only
app.beardrive.ai/p-b12fd122/wiki/deals/northwind.md
  • Anyone on the project
  • Everyone else, link or not

🔗 the default — no share command

🌐 Published
app.beardrive.ai/s/1aad3327224e408d
  • Anyone with the link — no account
  • Nobody, the second you revoke

🛡 sandboxed · rate-limited

WHAT YOU GET · INSIGHTS

Your agents trust a doc
nobody has updated since March.

Every file, sized by how much your agents read it and colored by how long since anyone touched it. The red cells are your risk list — heavily used, quietly rotting.

Counts, never readers. Who read what never leaves the server — this is a maintenance signal, not surveillance. Owners and admins get the full dashboard; everyone sees read-heat dots while browsing the folder.

WHY NOT JUST…

Only one of these is a folder.

Shared agent memory usually lands somewhere nobody can open — or in a repo nobody outside engineering will touch.

a vector store
0.0421 −0.8873 0.5512 0.1180 −0.3391 0.7724 0.0095 −0.6620 0.4417 0.2038 −0.9910 0.3356 0.8125 −0.0472 0.6693 −0.2214 0.7781 0.0530
?
You can't open it, and it's yours alone.
~/acme/wiki
📂 research/ 2 files
📄 q3-findings.md 2:14pm
📄 pricing-notes.md yesterday
📁 deals/ 4 files
Open it, read it, fix it. Everyone has it.
vs. memory tools — theirs is per-user and unreadable. This is a folder.
vs. a git repo — commits are a human ritual. Agents just write.
vs. Drive — no idea what a human changed and what software did.

CAN YOU DEPEND ON IT

Safe to let software write.

Every version kept, attributed, and restorable — so an agent overwriting your doc is an annoyance, not a loss. And none of it is a black box: the whole product is open source, on storage you can own.

Nothing gets overwritten.

Snow Mon 9:02am
Snow's Claude Tue 4:41pm
Priya Wed 11:20am
Priya's Claude Thu 8:15am
Snow's Claude today 2:14pm

Five versions of q3-findings.md. Open or restore any of them.

Nothing is a black box.

your team's machines wiki/ Snow wiki/ Priya wiki/ Marco BearDrive hub accounts · history share links S3 · GCS · R2 or a plain folder

No cloud credentials ever touch a laptop — and self-hosted, the storage is yours.

SETUP

You don't install it. You ask.

No console to learn, no terminal to open. Your agent does the whole setup, then keeps everyone's folder fresh on its own.

Explore the plugin →
Claude Code
You
Set up BearDrive so our team wiki stays in sync.
Claude
Installing and signing you in. Whole folder, or just wiki/?
You
Just the wiki.
Claude
Done. wiki/ is syncing, and I've added the hooks that keep it current for everyone.
↑ the actual onboarding — /beardrive:install

GET BEARDRIVE

Let us run it. Or run it yourself.

Free to start, no credit card. Paid plans from $8/month. Or self-host the whole thing — one binary, your storage.

BearDrive Cloud

managed · live now
  • Free to start — no card, no bucket
  • Zero setup: your agent handles it
  • Storage, backups, support handled

Self-hosted

AGPL-3.0 · free forever · your infrastructure
  • The complete server — teams included
  • One binary: bdrive web
  • S3 / GCS / R2 / MinIO / a folder

$ brew install runbear-io/tap/beardrive

Stop re-explaining your project
to every agent on the team.

One folder. Your Claude writes it, their Claude reads it. Free to start.