Gentle bump on this one — it’s been quiet for about a month and I wanted to flag that it’s still live and still, in my view, a safety issue rather than a cosmetic one.
To recap the core of it: when the AskQuestion / questionnaire prompt times out, the model receives a return string that is byte-identical to a deliberate user skip (“Questions skipped by the user, continue with the information you already have”). The agent therefore cannot distinguish “the user ran out of time” from “the user consciously opted out”, so on a high-consequence prompt it will proceed on an uninformed default as if it had consent. I most recently reproduced this on 3.7.19 (macOS).
This is the confirmed-bug counterpart to the feature request in Increase the timeout for Ask Questions, which now has 10 likes and several users describing the same pain.
Is this one on the tracker yet? If it’d help, I’m happy to pull fresh logs/session IDs from a current build. The single highest-value fix would be to make the timeout return a distinct string (e.g. “prompt timed out; user did not respond”) so the agent can stop and wait rather than guess.