monitor-with-permissions
Windows only
Like upload-folder-with-permissions, this command only runs on the Windows build of the CLI.
Continuous version of upload-folder-with-permissions. Performs the initial permissioned sync, then keeps watching the folder and re-syncing — both file content and ACL changes — until you stop the process.
Usage
curiosity-cli monitor-with-permissions \
--server https://my-workspace.example.com/ \
--token $CURIOSITY_TOKEN \
--path \\\\fileserver\\Shared \
--permissions-cache C:\\curiosity\\acl-cache.json \
--fetch-server-state true
Options
Same set as monitor, plus:
| Flag | Alias | Required | Description |
|---|---|---|---|
--permissions-cache |
-c |
yes | Path to a .json file used to cache resolved ACL → user/group mappings between runs. |
As with the one-shot variant:
--upload-tois forced toCustom.- The CLI invokes
graph.MapPermissionsAsyncfor new/changed files andgraph.CheckPermissionsChangedto re-evaluate ACLs on files that already exist in the graph.
Running it as a service
The same systemd / NSSM / Windows Service pattern from monitor applies — wrap the command in your platform's service supervisor so it restarts on failure and starts on boot. On Windows specifically:
nssm install CuriosityMonitor "C:\Users\svc\.dotnet\tools\curiosity-cli.exe"
nssm set CuriosityMonitor AppParameters monitor-with-permissions ^
--server http://localhost:8080 ^
--token %CURIOSITY_TOKEN% ^
--path \\fileserver\Shared ^
--permissions-cache C:\curiosity\acl-cache.json ^
--fetch-server-state true
nssm set CuriosityMonitor AppEnvironmentExtra CURIOSITY_TOKEN=...
nssm start CuriosityMonitor
See also
upload-folder-with-permissions— one-shot equivalent.monitor— non-permissioned continuous sync.- Access control — how the workspace stores and enforces those permissions.