I am fine with this, and I will go as far as to say this is how most devs will be using agents soon (the big companies have already been using agents like this for 6-12 months.)

I don't want my agent to pause on some inane question once I let it loose. I might not even be at my computer for that. Usually it makes the right decision anyways. If it doesn't I can always undo what it did.

If you're worried about it getting the architecture wrong, this is what Plan mode is for BTW. It gets architectural questions out of the way first, and just let the agent build from there.

▲

TSiege 11 hours ago | parent | next [-]

"I love lax security features therefore you should too." Defaults should be safe and risky action should be done at the user's own discretion

	▲	apetresc 11 hours ago \| parent \| next [-]
		This isn't really security-related. The "AskUserQuestion" hook in question here is not the one that gets used for authorizing actions. That's a completely separate mechanism that is unaffected by this 60-second timer thing. What this is referring to are those follow-up "here's two plausible alternative ways to do this, which one do you prefer?" questions you sometimes get, and usually at the beginning of a planning session when presumably you're still actively involved in the session. They get exponentially less likely as the turn goes on. Maybe it's a good default, maybe it's not, I'll wait to pass judgment. But it's not security-related except in contrived scenarios you could construct where one side of an A-or-B UserQuestion has security implications that aren't caught by any other safeguard. I haven't ever really experienced that in practice.
	▲	solenoid0937 11 hours ago \| parent \| prev [-]
		It's not security related. If you aren't running agents in a sandbox today, that's a "you" problem. It's purely architecture/design related and the last thing anyone wants is coming back at the end of the day to find their agent didn't make progress because it was stuck on a response. You can always redirect the agent or scrap its work, you can't undo the lost time.

▲

cyclopeanutopia 11 hours ago | parent | prev | next [-]

There are people who like to be pissed on, it doesn't mean it should be a default behavior.

▲

cameronsjo 5 hours ago | parent | prev | next [-]

I couldn't be the polar opposite. If my agent is asking a question, that means I didn't do a good enough job building enough context (not necessarily a good prompt, but context).

I have a hook that checks for a 'non-answer' from AskUserQuestion from when there was a different bug. It just so happens to be an accidental safeguard for me in this case.

▲

NikxDa 11 hours ago | parent | prev | next [-]

And yet other people rely on it doing exactly the opposite. Aside from whether this behavior is useful, it is never warranted to change such an important thing unannounced.

▲

Sharlin 11 hours ago | parent | prev | next [-]

You only live once, right?!

▲

grosswait 11 hours ago | parent | prev [-]

I’m pretty sure I used plan mode today and it continued when I didn’t respond quickly enough. Though now I can’t recall whether it was Claude or Codex. In either case terrible default.

	▲	nsingh2 10 hours ago \| parent [-]
		Codex apparently added this too, I only noticed a few days ago: https://github.com/openai/codex/issues/28969 I'm usually at my desk, and get a notification when it stops to ask a question, so I've never accidentally had it timeout yet. Still an annoying change.