Feature / UX Request
Mark rclone-based cloud sync/bisync commands as Personal-workspace local mirror commands in CLI help and docs.
Problem
The old rclone sync/bisync commands are still useful for Personal workspace local mirror workflows, but their help text does not clearly say that they are not a general Cloud/Teams sync facility.
With Team workspaces, users may reasonably expect bm cloud sync or bm cloud bisync to work for shared workspaces, but multi-user rclone bisync is not supported there.
Proposed Documentation/Help Updates
Update command help and relevant docs to say something like:
Personal workspace local mirror only. Not supported for Team workspaces.
Team workspaces are accessed through cloud API/MCP routing.
This should appear in:
bm cloud sync-setup --help
bm cloud sync --help
bm cloud bisync --help
bm cloud check --help
bm cloud bisync-reset --help
- Any docs pages that describe cloud sync/bisync
Acceptance Criteria
- Users can tell from
--help that rclone sync/bisync is Personal-workspace-only.
- Team workspace docs point users toward cloud API/MCP routing rather than local sync setup.
- Existing Personal workspace rclone workflows remain documented.
Feature / UX Request
Mark rclone-based cloud sync/bisync commands as Personal-workspace local mirror commands in CLI help and docs.
Problem
The old rclone sync/bisync commands are still useful for Personal workspace local mirror workflows, but their help text does not clearly say that they are not a general Cloud/Teams sync facility.
With Team workspaces, users may reasonably expect
bm cloud syncorbm cloud bisyncto work for shared workspaces, but multi-user rclone bisync is not supported there.Proposed Documentation/Help Updates
Update command help and relevant docs to say something like:
This should appear in:
bm cloud sync-setup --helpbm cloud sync --helpbm cloud bisync --helpbm cloud check --helpbm cloud bisync-reset --helpAcceptance Criteria
--helpthat rclone sync/bisync is Personal-workspace-only.