Please note that in my OP, I never mentioned containers. Let's say, as a developer, I need to do some API interactions with GitHub. So, in a terminal, using 1

Please note that in my OP, I never mentioned containers. Let's say, as a developer, I need to do some API interactions with GitHub. So, in a terminal, using 1Password's cli tool `op`, I load my GH API token and pass it to my Python script that is doing the API calls. Presumably, the reason I use that process is because I want to keep that token's exposure isolated to that script and I don't want the token exposed on the filesystem in plaintext. There is no reason for every process running as my user on my laptop to have access to that token. But, that's not how things work. The Claude agent running in a different CLI session (as an example) also now has access to my GitHub token. Or, any extension I've ever loaded in VS Code also has access. Etc. It's better than having it in plain text on the file system but not by much. Additionally, unless I've misunderstood the systemd docs, if you are passing secrets through environment variables using unit's `Environment` config, ANY USER on a server can read those values. So now, we don't even have user isolation in effect. My reasoning is pretty plain. It could be wrong, but it's hardly specious.