So vne is a small cli that helps agents to operate with .env files which were the only thing left I really open a code editor for. It is not a sandbox. And it is optimized for "safety" only to the extent that agents will use them freely without worrying about premature leaking, compared to allowing them operating on the .env files directly.
With vne the agents can
- locate .envs themselves
- run commands with env injection enabled
- duplicate a secret to another file within the same folder
- or hand you a vne command to run for copying a secret in from another folder
- hand you a command to add a new secret
So vne is a small cli that helps agents to operate with .env files which were the only thing left I really open a code editor for. It is not a sandbox. And it is optimized for "safety" only to the extent that agents will use them freely without worrying about premature leaking, compared to allowing them operating on the .env files directly.
With vne the agents can
- locate .envs themselves - run commands with env injection enabled - duplicate a secret to another file within the same folder - or hand you a vne command to run for copying a secret in from another folder - hand you a command to add a new secret