Path control

Filesystem boundaries for IDE coding agents. Constrain which paths agents can read or write. Keep work inside the repo; keep secrets and infra out of reach.

Why it matters

Agents that can touch .env, SSH keys, or production kube configs turn a coding session into a credential incident. Path rules belong in the execution path, not in chat tips.

Allow and deny examples

Allow

• src/**, tests/**, draft PR files

Deny

• .env*, ~/.ssh, production kube configs

How it works

When an agent proposes a path read or write, Relay evaluates path globs before the filesystem side effect. Denied calls return a structured reason and land in audit.