To be fair, protecting credentials and important data is the company and individual’s responsibility. The building blocks to restrict access are there, but are often not leveraged (even by large companies with the ability to invest)
Sandboxing is one of them: Both Codex & Claude’s sandboxing is reasonable (sandbox-exec, Linux cgroups & seccomp). Many others are lacking, sometimes deliberately.
I do most coding with Pi these days, and I have it heavily sandboxed. I expose sensitive services via a localhost network service with auth (typically for running scripts outside the sandbox). Reads are limited to the system binaries/libs, nad writes to the project dir & Pi’s own dirs. If I choose to give a particular session creds, then I have to be very deliberate. I also force egress traffic through a proxy (just logging for now, but I have plans)
To be fair, protecting credentials and important data is the company and individual’s responsibility. The building blocks to restrict access are there, but are often not leveraged (even by large companies with the ability to invest)
Sandboxing is one of them: Both Codex & Claude’s sandboxing is reasonable (sandbox-exec, Linux cgroups & seccomp). Many others are lacking, sometimes deliberately.
I do most coding with Pi these days, and I have it heavily sandboxed. I expose sensitive services via a localhost network service with auth (typically for running scripts outside the sandbox). Reads are limited to the system binaries/libs, nad writes to the project dir & Pi’s own dirs. If I choose to give a particular session creds, then I have to be very deliberate. I also force egress traffic through a proxy (just logging for now, but I have plans)