Your coding agent's worktree is not its security boundary
An agent opens a fresh worktree, completes a task, and hands back a diff. The files are separate. The result is easy to review. It's tempting to call that containment, but the worktree only separates where the task's edits go . It does not decide which other files the process can read, which creden…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-11-02 06:07 · DEV Community — AI
Your coding agent's worktree is not its security boundary