BearDrive

the "syncs to your team in seconds" part is what gives me pause rather than the storage question everyone else is asking. an agent working on something sensitive - a customer contract draft, a research doc that accidentally captured an API key or PII from a scraped page - now propagates to the whole team's synced folder before any human looks at it, since there's no workspace-level review step like a PR or a Slack post someone has to actually send. is there any per-file or per-folder gate before something syncs, or is the model "everything your agent writes locally is now everyone's by default" and you're expected to gitignore-style exclude the sensitive stuff yourself?

I’ve been waiting for this product to exist!
BearDrive will hopefully let me retire the rclone + jujutsu based system I cobbled together to enable context to be synced with provenance across my various development machines.
My one question is about BearDrive’s ability to handle large files. I use a LadybugDB based memory system for my agents, and the .lbdb files can be quite large (100 MB+). Will that be an issue?

Maker here. What changed for me: I stopped being the middleman between my teammates' agent and mine.

My teammate's agent writes a research doc, my agent reads it from the same folder an hour later - with the authorship and history attached, so I don't have to narrate the context first. Humans and agents on both sides just stay in sync.

Small mechanic, but it quietly removed most of the "let me catch you up" overhead from our week.

Nice launch and glad this streamlined your team's productivity. :)I'm still unsure why this should replace workspace setups like Notion/ClickUp connecting via MCP or a team Shared Drive folder though. At my previous company we were particularly concerned about the same docs centralization problem you're describing, which is why we would have still chosen Notion/ClickUp over an extra drive to store key resources and collaborate on docs.

Congrats on the launch guys!! 🎉 Great to see BearDrive out in the wild!

May be I am missing some thing here, we use Notion for this now. How do you differ from that approch ?

Disclosure: I'm a friend of Snow's. That said, the framing here is sharp — "your filesystem is the shared surface" is a much better bet than asking teams to migrate into yet another workspace. The versioning + authorship layer is what makes it more than a sync tool. Congrats on the launch!

Regarding your question, how teammate’s output reach me today: through Notion. Agents write there via mcp, the team already lives there, and it works. What’s the specific reasons to migrate?

Having a shared folder for each customer has made working together so much easier for our team. So excited that we got to build this together! Thank you so much for your support! 🐻🚀

So happy this is finally out 🎉 It's already changed how our team works.

Maker here. Really proud of the team for bringing BearDrive to life🔥AI agents are having their Dropbox moment!Our agents can produce dozens of HTML pages and PDFs in a day: quick dashboards, analysis reports, launch docs.Creating useful files is easy now.Finding them again is not.A week later, I know the report exists. I just don’t know whether it’s on someone’s laptop, attached in Slack, or buried under a filename nobody remembers.And when I do find it, I’m not always sure it’s the latest version.That’s the Dropbox moment: not another place to dump files, but a way to stop agent-made work from feeling scattered and disposable.The part I care about most is the handoff. One agent creates something, and another teammate’s agent can actually find it and build on it later.When an agent creates a useful file on your team, how does the next person find it a week later?

Hey Product Hunt, I'm Snow, founder of Runbear.

Here's the moment that made us build BearDrive: everyone on our team uses Claude Code daily. Each of us had an agent producing genuinely good work: competitive research, launch plans, analytics reports, decks. And every one of those files lived and died on one person's laptop. My co-worker would re-research something my agent had already figured out, because neither he nor his agent had any way to know the file existed.

The obvious fixes all failed us. Pasting into Notion was a manual chore nobody kept up. Git is wrong for research and ops artifacts, and non-engineers won't touch it. Dropbox syncs bytes but tells you nothing about who made what, when, or whether it's still current.

So we built the thing we wanted: a shared folder that is actually built for how agent teams work.

- Your agents keep working where they already work: your local filesystem, any file format, any tool.
- BearDrive syncs that folder to your team in seconds, with full change history: who, when, from which device.
- Every file gets a link you can drop in Slack, and a web view teammates can read without installing anything.
- Other people's agents read from the same folder, so context moves between agents without a human re-explaining it.

We run our whole company on it. Our strategy wiki, sales collateral, and research sync across the CEO, marketing, dev, and support projects through BearDrive, and each team's agents read and write it every day. This launch was planned in it.

What it's not: it's not an agent memory system and not another workspace to migrate into. It's your files, made team-owned.

I'd love brutal feedback on one question in particular: when your teammate's agent produces something useful, how does it reach you today? That answer shapes what we build next.