[flagged]
A way to exclude sensitive files issue still open for OpenAI Codex
131–140 of 157 posts
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#132Wouldn’t implementing this just give a false sense of security? As long as an agent can execute arbitrary code it can access anything it has access to. Adding a dont-access-my-secrets-pretty-please.yml file isn’t going to help any
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#133Look at agent-vault and 1password. There's not really any reason to be storing sensitive keys in plaintext on your local disk that the agent can access.
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#134You can do this now: change the file permissions such that the user you run codex as can't read them, or run codex in a container without those files mounted. If you don't do that, the agent will be able to incidentally upload them. What if the model runs "rg foo", and one of those files contains the string "foo"? It uploads the tool output, which includes the file contents. And so, the only solution is to make it so…
> people also expect those files to still be accessible i.e. if the agent invokes "make", which makes it impossible to solve perfectly
You could always use setuid to allow the agent to run designated commands whose operation depends on the files, without the agent itself being able to access the files.
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#135Earlier quoted context omitted.
Yes.
lol I don’t you realize how tech illiterate most normies are
It's not that I don't understand, it's that I don't care. Normies routinely hurt themselves trying to do professional work. We don't blame the tools when that happens, we blame the normies.
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#136just use bwrap?
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#137should be using pi-mono tbh. all vendor provided harnesses are complete trash
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#138Earlier quoted context omitted.
Thanks so much for building smolvm! I liked it so much that I vibe coded a little bash wrapper around it to handle creating ephemeral VMs for Pi: https://github.com/neuroblaze/smol-pi Consists of two scripts, one to build an OCI image (customizable by editing the Dockerfile that comes with it) and another to handle smolvm invocation. The invocation script mounts the current working directory under /workspace in the V…
smolpi looks great! and smolvm does clean up ephemeral runs if the machine run exits gracefully. I'll take a deeper look into this edge case and fix it today.
Fixed and released in v1.3.1: https://github.com/smol-machines/smolvm/pull/497
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#139Earlier quoted context omitted.
The Codex bug tracker is a great insight into how wide the knowledge gap seem to be between users. The issue where people ask them to add back /undo or whatever it is instead of just learning to use git, probably reached 100 comments at least by now. People seemingly don't really understand the computers they use on a daily basis, and refuse to learn too.
I suspect most people don't even know there's a there there. For instance, while I now know that file systems have permissions, before I became a programmer, I spent maybe ten years thinking of permissions as a special, obscure system thing that you should never touch. For that matter, I suspect many people don't know basic things like that a file system isn't inherently the operating system. And, where would you go…
Nit: Your Mac does ship with a manual. Tips.app and of course the man pages. Point stands.
Re: A way to exclude sensitive files issue still open for OpenAI Codex
#140I've contributed to https://github.com/0xferrous/agent-box which allows you to bind-mount git repositories into containers that agents operate in, preventing the agents from accessing files that aren't bind-mounted. Your usual .gitignore can then be used to also ignore files within the repo to be bind-mounted, which prevents agents from accessing them at all, essentially working as a sandbox.
I also maintain https://github.com/nothingnesses/agent-images which allows you to use Nix to reproducibly spin up OCI containers containing agents and any other tools you need and use these with agent-box.
I use both at the moment to work on some personal projects with agents, where I set up multiple separate git worktrees for the agents to work in, preventing them from accessing anything outside of the worktrees and from trampling over each other's work.