One shared folderEvery agent reads and writes the same files.
Nothing is lostEvery version kept, attributed, restorable.
Yours to runOpen source, on your own storage.
Share by linkNo account needed on the other end.
ChatGPTChatGPT
ABCD
dealoutcomereasoncompetitor
northwindwonchampion + speed—
acmelostno security reviewgbrain
initechwonexec sponsor—
globexlostbudget froze—
hooliwonagent workflownotion
soylentlostno championgbrain
CodexCodex
4 agents · 3 files · all at once
synced just now · 0 ops
One shared folder, multiple agents. Nobody pasted anything.
Nothing to integrate. If it can write a file, it already works:
Claude CodeClaude CoworkCodexHermesGeminiObsidianGoogle OKFgbrain
…and anything else that writes a file.
Stop pasting files at each other.
It's the Dropbox moment for AI agents. Before Dropbox, you emailed yourself the file. Your agent and your teammate's agent still do.
Without BearDrive26 hours
9:14amQ3 report for Acme report.html
1:47pmNumbers are a month stale.
4:02pmFixed the numbers report-v2.html
9:31pmStill opens with our roadmap.
10:58amReordered it report-final.html
a week later — which one did we send?
With BearDrive90 seconds
9:14amQ3 report for Acme beardrive.ai/acme/report
9:15amMy agent fixed it in place.
same file, on both machines — every version kept
Stop losing versions.Stop hunting for files.Stop waiting on someone else to edit it.
WHAT YOU GET
It's a folder. That's the whole trick.
Real files at real paths, in the folder you already work in — a place to see who changed what, hand someone a link, and get any version back. Your agent starts every task already knowing what your team knows — instead of from an empty folder.
Every change is attributed — the person, the machine, and the agent session when an agent did it. Kept for good.
A link for anyone
Share any file as a public URL — no account needed on the other end. Revoke it whenever.
Works offline
Keep editing on a train. Everything converges when you're back, without a merge conversation.
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 — Claude3:42pm
Just got off the Northwind call — update the deal page.
ClaudeUpdated wiki/deals/northwind.md🔗 — added the call notes, moved the stage to Negotiation, pushed the close date to Aug 29.
by default
🔒app.beardrive.ai/p-b12fd122/…/northwind.md
Everyone on the project, nobody else.
when you publish it
🌐app.beardrive.ai/s/1aad3327224e408d
Anyone with the link opens the page — no account. Gone when you revoke.
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.
wiki/runbooks/incident-response.md214
⚠wiki/runbooks/hotfix-process.md194
wiki/onboarding/support-rotation.md152
⚠notes/meetings/2026-05-19-retro.md123
⚠wiki/architecture/system-overview.md113
⚠notes/meetings/2026-03-11-incident-review.md110
wiki/architecture/storage-layout.md109
⚠wiki/architecture/background-jobs.md81
⚠shared/reports/churn-analysis.md72
⚠shared/reports/partner-review.md72
shared/reports/security-review.md59
shared/reports/cost-breakdown.md59
wiki/runbooks/load-shedding.md47
agent readshuman reads
claude-snow
codex-mia
claude-ci
claude-priya
codex-sam
claude-marco
claude-ana
gemini-doc
wiki
notes
shared
docs
Cell size is reads, color is freshness. Red is hot and rotting.
Every file plotted. The top-right quadrant is the danger zone.
The files everything depends on — agent reads against human reads.
Which agents read which areas of the folder.
No names, ever. Heat is counts and dates, never the person who read a file — agent reads by device, the same ids History already shows. Every project member sees the same view.
WHY NOT JUST…
Only one of these is a folder.
Each of these does a job BearDrive doesn't try to do — and pairs with it. None of them is the shared folder your team's agents work in.
final-v2-FINAL.html was your version control. This keeps every version, forever.
Every change that syncs is a 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.
SnowMon 9:02am
Snow's ClaudeTue 4:41pm
PriyaWed 11:20am
Priya's ClaudeThu 8:15am
Snow's Claudetoday 2:14pm
Five versions of q3-findings.md. View or restore any of them, in one click.
Nothing is a black box.
No cloud credentials ever touch a laptop — and self-hosted, the storage is yours.
Real files — a normal folder on disk. Stop syncing any time; the files stay.
Offline-safe — work on a plane. Concurrent edits keep both versions.
Open source — AGPL-3.0. Server, teams, history, links — nothing held back.
Portable — bdrive export moves a whole project — every version, every file — to any other hub.
Public links — sandboxed and rate-limited, and dead the moment you revoke.
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.
Follow beardrive.ai/setup to set up BearDrive. Ask me which folder to sync.
Claude
Installing the CLI and signing this machine in — I'll hand you one link to approve. I'd create shared/ here and sync just that. Or a folder you already have?
You
shared/ is good.
Claude
It's empty — want a structure to start from? Docs + decision records, an LLM wiki, or PARA.
You
Docs.
Claude
Done.shared/ is syncing withdocs/ and decisions/, the hooks that keep it current are registered, and here's the project link.