Vibe coding: Too many “Yes, proceed” confirmations

Codex keeps asking me to confirm commands (Yes, proceed) nonstop during vibe coding. Super breaks the flow.

Do you see the same thing? How do you avoid it / make it auto-run + auto-test (or approve once per session)?

2 Likes

Welcome to the forum!

Yes—many do. Some know how to nip it in the bud; others seem to live with it, unsure of what to do next.

I do think the changes OpenAI is making to Codex should help address this issue, although I haven’t had a chance to use Codex recently.

If you’re comfortable tracking GitHub commits, it may be worth keeping an eye on them.

Since I don’t strictly need to use Codex at the moment, I’m waiting for the Plan skill (or Plan mode) to mature a bit more before giving it a try.

It’s also worth checking the issue trackers on some of the OpenAI GitHub repositories, as users occasionally post workarounds or solutions that later show up—sometimes in modified form—in production code.

While not all OpenAI repositories have Discussions enabled, some do:

2 Likes

Hi, and welcome to the community!

You can adjust this setting mid-session using /approval. Please note that changing it to Full-Auto may introduce additional risks.

2 Likes

@vb

Don’t shoot the messenger.

They just changed it.

1 Like

Is this git now recommended reading?
I think so.

1 Like