Sorry, I meant that’s not desirable behavior that the user might expect. I understand that coding agent tools tend to play fast and loose with access because it’s not their own privacy/security at stake.
Not sure what that's about, I was just copying the wording from OP. Their harness probably has the same restrictions as most other coding harnesses. That is, the read tool gives all project files by default without prompting, and everything else requires manual approval (or opting into auto-run all). If you decide to run it from your home directory however, then your "project" is all your files.
> The repo you’re working on, sure. But all files?
Yes, any tool, including any coding agent, has access to all files $USER has access to.
Sandbox it explicitly to give access to only the current directory - https://github.com/ashishb/amazing-sandbox
Sorry, I meant that’s not desirable behavior that the user might expect. I understand that coding agent tools tend to play fast and loose with access because it’s not their own privacy/security at stake.
This is true for all CLI tools on Mac and Linux (and other operating systems from that era).
Historically, everything you ran was trustworthy.
Android and iOS were invented in an era that does not allow this because the risks became evident by then.
Not sure what that's about, I was just copying the wording from OP. Their harness probably has the same restrictions as most other coding harnesses. That is, the read tool gives all project files by default without prompting, and everything else requires manual approval (or opting into auto-run all). If you decide to run it from your home directory however, then your "project" is all your files.