pi: am I sandboxed?

♠ Problem statement: asking a coding agent whether it runs in a sandbox returns a confident answer derived from its system prompt, not from the machine it is actually running on. I asked Pi exactly that. The reply was assured: No — pi itself doesn’t sandbox tool execution. When I run bash, edit, or write, they execute directly on your machine with your user’s permissions, in the current working directory (/Users/thiago.perrotta/.pi). […] But there’s no OS-level sandbox (no container, no seccomp, no filesystem jail). It’s plausible, well-formatted, and…wrong!. One typo-ridden command was enough to break the illusion: % ls ~/worksppace ls: cannot access '/home/hostuser/worksppace': No such file or directory ~ is not /Users/thiago.perrotta. The follow-up probe: % pwd; uname -a; whoami; cat /etc/os-release /Users/thiago.perrotta/.pi Linux lima-rancher-desktop 6.18.37-0-virt #1-Alpine SMP PREEMPT_DYNAMIC 2026-06-29 10:52:25 aarch64 GNU/Linux hostuser PRETTY_NAME="Debian GNU/Linux 12…