22 ms·
Docker isolation is a good baseline, but the tricky part is usually the boundary between “safe filesystem access” and tools that can indirectly access secrets (
by kate23_human 7mo ago
Docker isolation is a good baseline, but the tricky part is usually the boundary between “safe filesystem access” and tools that can indirectly access secrets (git configs, environment variables, credential helpers, etc).
Even read-only access to a repo can leak quite a bit depending on what’s in the workspace. I’ve seen some teams run tools inside containers but mount a filtered workspace rather than the full project directory to reduce exposure.
- schipperai 7mo agogreat callout - tool call can have side-effects outside your box. So unless you run a sandbox with no internet access, you aren't ever 100% safe. nah does guard some of this - reading .env or ~/.aws/credentials gets flagged, and Write/Edit content is inspected for secrets before it leaves the tool. Docker + filtered mounts + something like nah on top is a solid layered approach that is still practical.