F-01
Familiar commands
init, status, diff, push and pull behave the way your muscle memory expects, so there is almost nothing new to learn.
$ cd ../services
Developer sync
CLI Sync
Sync folders the way you push commits.
CLI Sync brings a git-style workflow to any folder. Initialize a directory, check its status, diff against the cloud, then push or pull. It runs on your laptop, your server or your CI runner, and only moves the blocks that changed.
$ cloudeee sync ./project --watch
~/services/cli-sync
$ cloudeee cli-sync --features
What you get.
F-02
Watch mode
Leave one command running and every save is synced within seconds, with a quiet log of what moved.
F-03
Block-level deltas
Only the changed parts of a file travel over the wire, which keeps huge folders and slow connections practical.
F-04
Ignore rules
A .cloudeeeignore file uses glob patterns to keep node_modules, build output and secrets out of the sync.
F-05
Readable conflicts
When two machines edit the same file, both versions are kept and clearly marked so nothing is silently overwritten.
F-06
Scriptable output
Stable exit codes and a JSON output mode make CLI Sync easy to drop into build pipelines and cron jobs.
$ cloudeee cli-sync --how
Four steps, zero fuss.
Step 01
Install and log in
Install the CLI, then authenticate with a device login on your machine or a token in your CI environment.
Step 02
Link a folder
Run init inside any directory to connect it to a workspace. Nothing is uploaded until you say so.
Step 03
Push or watch
Push once for a clean snapshot of the folder, or start watch mode to keep it in step automatically.
Step 04
Pull anywhere
On another machine, pull the folder down and keep working. Status and diff show exactly what changed.
$ cat specs.txt
The specs.
~/services/cli-sync/specs.txt
| Platforms | macOS, Linux and Windows |
|---|---|
| Core commands | init, status, diff, push, pull, watch |
| Transfer method | Block-level deltas |
| Ignore rules | .cloudeeeignore glob patterns |
| Output | Human-readable or JSON |
| Authentication | Device login or CI token |
$ man cli-sync
Quick answers.
Q01Is CLI Sync a replacement for git?
> No. Git tracks source history. CLI Sync keeps whole folders, including large binaries and build output, in step across machines, using a similar command style.
Q02What happens if I lose my connection mid-sync?
> The transfer resumes from the last completed block when you reconnect, so a dropped Wi-Fi signal never means starting over.
Q03Can I run it in CI?
> Yes. Use a CI token for authentication, call push or pull in a step, and read the JSON output or exit code to decide what happens next.
$ cloudeee signup --free
Start with CLI Sync.
Create a free account, get 20 GB of encrypted storage and try it in minutes.