The depressing truth is most I know just run all these tools in /yolo mode or equivalents.
replyBecause your coworkers definitely are, and we're stack ranked, so it's a race (literally) to the bottom. Just send it...
(All this actually seems to do is push the burden on to their coworkers as reviewers, for what it's worth)
Who has time for that? This is how I run codex: `codex --sandbox danger-full-access --dangerously-bypass-approvals-and-sandbox --search exec "$PROMPT"`, having to approve each change would effectively destroy the entire point of using an agent, at least for me.
replyEdit: obviously inside something so it doesn't have access to the rest of my system, but enough access to be useful.
>Who has time for that?
replyPeople that don't put out slop, mostly.
That's another thing entirely, I still review and manually decide the exact design and architecture of the code, with more care now than before. Doesn't mean I want the UI of the agent to need manual approval of each small change it does.
replyI wouldn't even think of letting an agent work in that made. Even the best of them produce garbage code unless I keep them on a tight leash. And no, not a skill issue.
replyWhat I don't have time to do is debug obvious slop.
I ended up running codex with all the "danger" flags, but in a throw-away VM with copy-on-write access to code folders.
replyBuilt-in approval thing sounds like a good idea, but in practice it's unusable. Typical session for me was like:
About to run "sed -n '1,100p' example.cpp", approve?
About to run "sed -n '100,200p' example.cpp", approve?
About to run "sed -n '200,300p' example.cpp", approve?
I keep it on a tight leash too, not sure how that's related. What gets edited on disk is very different from what gets committed.
replyAsk mode exists, I think the models work on the assumption that if you're allowing edits then of course you must want edits.
reply