beardrive/plugin/commands/status.md at feat/knowledge-init-flows

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

Files

T

Snow LeeandClaude Fable 5 f12710d527 docs(plugin): retire the "mount" framing; /beardrive:mount -> /beardrive:init

bdrive mnt was replaced by bdrive init, but the plugin still taught the
old model — /beardrive:mount even instructed Claude to run a command
that no longer exists.

- /beardrive:mount -> /beardrive:init: login-aware, uses bdrive init
  (resume/create/connect, --shared), points at /beardrive:install for
  the full team setup.
- Skill description reframed around "start syncing a project"; "mount a
  folder" kept as a trigger phrase since people still say it.
- status command, marketplace manifest, README plugin section, and
  CLAUDE.md updated to match.

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

2026-07-08 15:09:11 -07:00

708 B

Raw Permalink Blame History

description, argument-hint

description

argument-hint

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

folder

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

Run bdrive status $ARGUMENTS and show the output.
If anything looks wrong, diagnose using the beardrive skill:
- daemon: stopped → restart with bdrive init <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.

708 B Raw Permalink Blame History

708 B

Raw Permalink Blame History