Hi Gerard,
Was your invocation exactly as you shared?
--restrict-paths file: path-restrictions.json
It looks like there's a space after the "file:". As a result, the command is trying to handle a file named "".
The CLI options which use these multimodal inputs with the <prefix>:<value> syntax are consuming a single string with both parts.
I'd recommend quoting it too, which clarifies a bit:
--restrict-paths "file:path-restrictions.json"
If that's not the issue, please let us know. But from the command and the error output it looks like that's what happened.
(I'll look into ways we can improve the error behavior in the future as well.)
Best,
-Stephen