What. You don't have yours ask for edit approval?

▲ embedding-shape 3 hours ago | parent | next [-]

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.

Edit: obviously inside something so it doesn't have access to the rest of my system, but enough access to be useful.

▲ well_ackshually 34 minutes ago | parent | next [-]

>Who has time for that?

People that don't put out slop, mostly.

▲ quotemstr 2 hours ago | parent | prev [-]

I 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.

What I don't have time to do is debug obvious slop.

	▲	kees99 2 hours ago \| parent [-]
		I ended up running codex with all the "danger" flags, but in a throw-away VM with copy-on-write access to code folders. Built-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?` Could very well be a skill issue, but that was mighty annoying, and with no obvious fix (options "don't ask again for ...." were not helping).

▲ mullingitover an hour ago | parent | prev [-]

Ask mode exists, I think the models work on the assumption that if you're allowing edits then of course you must want edits.