# GPT-5 responses cut short: add option to re-generate last agentic response **URL:** \ **Category:** Feature Requests\ **Created:** [October 4, 2025, 8:18am UTC](https://forum.cursor.com/t/gpt-5-responses-cut-short-add-option-to-re-generate-last-agentic-response/136077 "2025-10-04T08:18:22Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![leventov](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/leventov/32/26188_2.png) [@leventov](https://forum.cursor.com/u/leventov)\ **Post date:** [October 4, 2025, 8:18am UTC](https://forum.cursor.com/t/gpt-5-responses-cut-short-add-option-to-re-generate-last-agentic-response/136077/1 "2025-10-04T08:18:22Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Since about 5 days ago, gpt-5 responses are regularly cut short mid response. From Cursor’s perspective, this is a complete, successful response. This is nasty because this might be at the end of a long agentic chain of tool calls and generations with non-idempontent and/or expensive tool calls. The only way forward in Cursor is to restart since the last user message, which might be long ago. ### Steps to Reproduce Use cursor IDE ### Expected Behavior **Please add an option to restart generation since the last well-formed tool call, not just the last user message.** ### Operating System MacOS ### Current Cursor Version (Menu → About Cursor → Copy) Version: 1.7.33 (Universal) VSCode Version: 1.99.3 Commit: a84f941711ad680a635c8a3456002833186c4840 Date: 2025-10-03T03:28:06.574Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Darwin x64 21.6.0 ### For AI issues: which model did you use? gpt-5, gpt-5-high ### Does this stop you from using Cursor Sometimes - I can sometimes use Cursor ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [October 5, 2025, 8:42pm UTC](https://forum.cursor.com/t/gpt-5-responses-cut-short-add-option-to-re-generate-last-agentic-response/136077/2 "2025-10-05T20:42:14Z")
Hey, thanks for the report. I’m not seeing this issue on my side. Could you share the request ID? You’ll need to turn off privacy mode first. > **[Getting a Request ID | Cursor Docs](https://cursor.com/docs/troubleshooting/request-reporting)** > > Report issues and track request IDs for debugging with support. ---
**Author:** ![leventov](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/leventov/32/26188_2.png) [@leventov](https://forum.cursor.com/u/leventov)\ **Post date:** [October 5, 2025, 9:49pm UTC](https://forum.cursor.com/t/gpt-5-responses-cut-short-add-option-to-re-generate-last-agentic-response/136077/3 "2025-10-05T21:49:10Z")
I’m pretty sure this is OpenAI’s inference problem Cursor can do nothing about, yet the fix that I’ve suggested would be useful anyway. Besides, often the model goes off the rail with terminal command syntax somewhere mid-rollout and it would also be great to stop right there and intercept with a user message “call such and such tool with such and such syntax”, instead of passively observing the model stumbling. Again, “in the previous paradigm” when model’s rollout contained a single or a few tool calls it would be fine to edit my previous message, but in the new paradigm with models doing dozens of research tool calls before generating terminal commands and stumbling with their syntax (for example) that is too costly. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [October 27, 2025, 9:50pm UTC](https://forum.cursor.com/t/gpt-5-responses-cut-short-add-option-to-re-generate-last-agentic-response/136077/4 "2025-10-27T21:50:00Z")
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.