beardrive/plugin/commands/status.md at fafb7fe24d24e5fb6abdf0cf88728eec6b28607e

mirror of https://github.com/runbear-io/beardrive.git synced 2026-08-25 08:08:08 +02:00

Files

T

Snow LeeandClaude Fable 5 1ac128db2c rename: sfs -> BearDrive everywhere; CLI becomes bdrive

Product and project are BearDrive; the CLI binary is bdrive (bdrive mnt,
bdrive sync, ...), the web viewer is bdrive-web. All conventions follow
the full name: .beardrive settings file, .beardriveignore, ~/.beardrive
home, BEARDRIVE_HOME, .beardrive-conflict-* / .beardrive-tmp-* files.
Plugin/skill/marketplace renamed to beardrive (/beardrive:mount).

Module path is now github.com/runbear-io/beardrive — merge only after
renaming the GitHub repo, or go install breaks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HHEUaYfFHhmDvqLYw74Ehz

2026-07-07 15:02:40 -07:00

703 B

Raw Blame History

description, argument-hint

description

argument-hint

Show bdrive sync status — mounts, daemon state, pending changes — and diagnose any sync problems

folder

Show the bdrive sync status. Argument: $ARGUMENTS (optional folder; default all mounts).

Run bdrive status $ARGUMENTS and show the output.
If anything looks wrong, diagnose using the beardrive skill:
- daemon: stopped → restart with bdrive mnt <folder>
- pending stuck above 0 → run bdrive sync <folder> and read the error; it usually points at credentials or the remote
- changes not appearing from another device → run bdrive log <folder> to see whether the ops arrived
Summarize the state in one or two sentences.

703 B Raw Blame History

703 B

Raw Blame History