The shipped CLI's relayfile mount takes --remote-path as a single string flag (last one wins, not repeatable) and rejects --local-layout (flag provided but not defined: -local-layout). One mount per workspace is enforced.
The README documents repeated allowlists (--remote-path /github --remote-path /slack/channels/x), but that surface belongs to the separate relayfile-mount daemon binary, which the npm package does not ship.
Consequence: a consumer wanting an agent to see a few tight subtrees (e.g. /github/repos/Org/** + two Slack channels + /notion) must choose between one broad subtree or multiple workspaces. Hit while scoping the chief agent's senses mount (relayfile 0.10.37, macOS).
Expected: expose repeated --remote-path (and/or a --paths-file) plus the scoped local layout through the shipped CLI.
🤖 Generated with Claude Code
The shipped CLI's
relayfile mounttakes--remote-pathas a single string flag (last one wins, not repeatable) and rejects--local-layout(flag provided but not defined: -local-layout). One mount per workspace is enforced.The README documents repeated allowlists (
--remote-path /github --remote-path /slack/channels/x), but that surface belongs to the separaterelayfile-mountdaemon binary, which the npm package does not ship.Consequence: a consumer wanting an agent to see a few tight subtrees (e.g.
/github/repos/Org/**+ two Slack channels +/notion) must choose between one broad subtree or multiple workspaces. Hit while scoping the chief agent's senses mount (relayfile 0.10.37, macOS).Expected: expose repeated
--remote-path(and/or a--paths-file) plus the scoped local layout through the shipped CLI.🤖 Generated with Claude Code