Problem
The content.outside_boundary rule blocks any file access outside the repo's CWD. This breaks all colony infrastructure agents (Spiral, Vector, etc.) that legitimately access sibling repos under ~/source/.
Examples blocked:
git log --all in ~/source/ when CWD is a subrepo- File reads in sibling repos by infrastructure agents
Fix
Options (in order of preference):
- Allow
~/source/* sibling paths via .bashguard.yaml allowed_paths config
- Make
outside_boundary opt-in (disabled by default, enabled per-project)
- Allowlist colony sibling repos explicitly
The rule intent is sound (prevent agents reading sensitive files outside their project) but the implementation is too broad for multi-repo environments.
Problem
The
content.outside_boundaryrule blocks any file access outside the repo's CWD. This breaks all colony infrastructure agents (Spiral, Vector, etc.) that legitimately access sibling repos under~/source/.Examples blocked:
git log --allin~/source/when CWD is a subrepoFix
Options (in order of preference):
~/source/*sibling paths via.bashguard.yamlallowed_pathsconfigoutside_boundaryopt-in (disabled by default, enabled per-project)The rule intent is sound (prevent agents reading sensitive files outside their project) but the implementation is too broad for multi-repo environments.