Install the CLI
Most people never run this. Setting up through your agent installs the binary as its first step.
Install it yourself when you would rather drive the setup by hand, when you are running a hub, or when a machine has no agent on it.
BearDrive ships one binary, bdrive. It is the CLI, the sync daemon, and the
web server. macOS and Linux.
Homebrew
Section titled “Homebrew”brew install runbear-io/tap/beardriveWorks on macOS and Linuxbrew.
From source
Section titled “From source”go install github.com/runbear-io/beardrive/cmd/bdrive@latestThe frontend’s built assets are committed to the repository, so building never requires Node.
Release binary
Section titled “Release binary”No Homebrew and no Go? Grab the tarball for your OS and architecture from the releases page.
Verify
Section titled “Verify”bdrive versionUpgrading
Section titled “Upgrading”brew upgrade beardriveClients and hub are the same binary — keep them roughly in step. The sync protocol is append-only journals plus blobs, which old clients read forward.
After upgrading a client, re-run bdrive hooks install once per project to pick
up hook improvements, and bdrive skill install once per machine to refresh the
agent skill.
Set up by hand — sign in and start syncing a folder, command by command.