Confirming Bug 1 (questionnaire timeout treated as a skip) still reproduces on a much newer build than the original report.
Environment
- Cursor 3.7.19 (arm64)
- macOS 26.5.1 (build 25F80)
@mohitjain you asked the OP to retest after the post–April-28 improvements — I can confirm it is still happening on 3.7.19. In an Agent session today the AskQuestion prompt resolved with the synthetic “Questions skipped by the user, continue with the information you already have” string while I was still deciding how to answer. The questionnaire was still visible on screen, but the agent had already received the skip and would have proceeded on an uninformed default path had I not intervened.
This matches the root cause confirmed in the related (now-closed) thread AskQuestion tool can return synthetic skip string with highly variable, unpredictable delay — the orphaned gRPC promise resolving to an empty result that is byte-identical to a deliberate skip. The most damaging part is that the agent cannot tell a timeout from a real skip, so for any consequential prompt it silently treats the timeout as user consent.
Happy to provide more detail if useful.