Grok Build prompt resumes old one

[Wraient]

Describe the bug

In Grok Build explicitly stopping a thread and sending a new prompt just resumes the old thread, which keeps executing until it completes the original prompt, and the new prompt sits queued the whole time.

To Reproduce

1. Send a prompt that takes a while to complete.
2. Explicitly stop the thread (terminate the run).
3. Send a new prompt.
4. The old thread resumes and keeps processing the original prompt to completion.
5. The new prompt stays queued until then — even though the thread was terminated before it was sent.

Expected behavior

• Stopping a thread should genuinely cancel the current run so subsequent prompts start immediately.
• There should be a way to choose between steering the in-flight model vs queueing the message — currently neither option is exposed.

Environment

• Client: Grok Build (t3-code MCP)
• Observed consistently: yes — every time a stopped thread is followed by a new prompt