3 ms·
Why not let it delete stuff in the current working folder and in tmp, but give it read-only access elsewhere?
by energy123 2mo ago
Why not let it delete stuff in the current working folder and in tmp, but give it read-only access elsewhere?
- jawiggins 2mo agoBecause I often want it to write and execute scripts in it's thinking loop in order to test assumptions or fetch data to come up with better solutions.
- energy123 2mo agoCan't it write `/tmp/test.sh` or `./test.sh` and execute it under my approach? This is what I've been doing as my status quo workflow with Codex, and I make sure I run Codex from a place where `.` happens to be a folder I'm okay with it messing up in.
- imtringued 2mo agoThat's how codex already works so you're not suggesting anything new, but it doesn't give write access at all of you set it to read only.
- yencabulator 2mo agoAnd when "it" is an arbitrary bash/python/javascript command, what then?