USE CASES
BearDrive is one shared folder your agents read and write. What that's worth depends entirely on who you are — find yourself below.
TEAM ARTIFACTS
For a team that doesn't live in a terminal — marketing, ops, design, founders.
Everything your agents produce lands in one folder every teammate's agent can read. Nobody attaches, uploads, or pastes anything.
Read the use case →TEAM WIKI
For a team whose knowledge lives in documents nobody updates.
The wiki gets written as a side effect of work, every change is attributed, and the hub shows which pages are load-bearing and stale.
Read the use case →BUSINESS CONTEXT
For an engineering team whose customer context lives where their coding agents can't see it.
A context folder synced into the repo — calls, accounts, roadmap rationale — so agents build with the reasons in front of them, and write back what shipped.
Read the use case →COMPANY BRAIN
For someone who already has an OKF bundle, a gbrain repo, or an Obsidian vault.
It's already markdown on disk, so there is nothing to export and no schema to adopt. It just doesn't have teammates yet.
Read the use case →PERSONAL NOTEBOOK
For one person — a researcher, writer, or consultant.
A versioned notebook your agent maintains, and a public link for the single page you choose. Sharing is per file, never per folder.
Read the use case →ONE CONTEXT
For one person running several machines and more than one agent.
Laptop, desktop, a server; Claude Code and Codex. One project mounted everywhere, so whichever agent you talk to starts from the same state.
Read the use case →They're all the same product: a folder that syncs, with accounts, history, and links. Start with anything and the rest is configuration.