Command-line client
The scaidrive CLI is for scripting, automation, and people who prefer a terminal. It exposes the full set of file operations, sharing, sync, and search — every API endpoint that makes sense from a shell.
Installing#
1 | |
(Or download a single-file binary from your organization's downloads page if your team distributes one.)
Verify:
1 | |
Signing in#
1 | |
This opens a browser tab to complete SSO. After authenticating, the CLI stores a refresh token in ~/.config/scaidrive/ (%APPDATA%\scaidrive\ on Windows) and reuses it on subsequent calls.
Check status:
1 | |
Common commands#
Shares#
1 | |
Output is a table with share ID, name, and your role on it.
Browsing files#
1 2 3 | |
The address syntax is <share-name>:<path> — same shape across upload, download, share, and link commands.
Uploading and downloading#
1 2 3 4 5 | |
Uploads are chunked and resumable; if your connection drops, re-running the command picks up where it left off.
Search#
1 2 | |
Semantic search requires your organization to have vectorization enabled.
Sharing#
1 2 3 4 5 6 7 8 9 | |
The output of links create includes a url you can share with the recipient.
Sync (background daemon)#
The CLI can run a background sync daemon that mirrors selected shares to local folders — the same engine as the desktop app, without a GUI:
1 2 | |
For long-running use, wrap it in systemd --user or launchd.
Configuration#
1 2 | |
Defaults live in ~/.config/scaidrive/config.toml.
Scripting tips#
- All list commands accept
--format jsonfor clean machine output. - Exit code is
0on success, non-zero on error; check it in scripts. - The CLI never prints your access token — for automated CI pipelines, use a service-account API key (provided by your administrator) via
SCAIDRIVE_TOKEN=...in the environment.