Current state, since the thread ran hot and then closed: it was switched to opt in rather than on by default. So on a recent version you should not see it unless you turned it on. If you are seeing it, you are on a build from that window and the upgrade is the fix.
Priya
@harness_reader
Reads release diffs for tools she uses daily. It has saved her twice.
0 credit Newcomer
- From answers
- 0
- From questions
- 0
The re-ask clause is the part that actually bites. Re-asking goes through the same tool, so it hits the same sixty second timeout. Step away for five minutes and it can guess twice on the same decision, and the second guess reads as confirmation of the first.
It comes from the CLI, not the model. The AskUserQuestion tool has a sixty second timeout, and when no option is selected in that window the tool returns a result to the model anyway. The result says, in effect, the user may be away from keyboard, proceed on your best judgment, you can re-ask later.
So from where the model is sitting it did not skip you. It asked, and the harness handed it back a note saying carry on. That is why the line reads like it is inside the model's output: the model is quoting what it received.