[Bug]: Cannot stop a running turn, edit the last prompt, and restart #11083

Before submitting

• I searched existing issues and did not find an exact duplicate.
• I included enough detail to reproduce the problem.

Summary

A workflow I regularly use in Cursor and Codex is:

1. Send a message and let the agent start working.
2. Notice immediately that the prompt is incorrect or incomplete.
3. Press Stop to interrupt the running generation.
4. Return to the last user message and edit or revert it.
5. Send the corrected prompt and restart from there.

I cannot complete this workflow in T3 Code.

While the turn is running, Revert to this message is unavailable. After trying to stop the turn, I cannot reliably return to the message that started it, edit or revert that message, and immediately retry with a corrected prompt.

Earlier user messages may have a Revert to this message action, but the message that started the current generation does not provide the stop → edit/revert → retry workflow.

Steps to reproduce

1. Start a thread and send a prompt that causes the agent to begin working.
2. While it is generating, notice that the prompt contains a mistake.
3. Press Stop.
4. Try to return to the last user message.
5. Try to edit or revert that message and send a corrected version.

Expected behavior

After pressing Stop, I can return to the last user message, correct it, and restart the turn.

If the agent already modified the repository, T3 Code should either restore the previous checkpoint or let me choose whether to keep the partial changes.

Actual behavior

I cannot perform the complete stop → edit/revert last message → retry workflow.

The revert action is available for some previous messages, but not for the latest message that started the interrupted or running turn.

Setup

• T3 Code Alpha desktop app on macOS
• T3 server running on a remote Nebius machine
• Desktop connected to the remote server through T3 Connect
• Cursor agent/provider
• Repository and agent processes are running on the remote machine
• The same T3 setup is also accessed from the iOS app

Related issues

These appear related, but none describes the complete user workflow above:

• [Bug]: Provider finish_reason network_error hides revert button #7982 — the revert button can be missing after a failed turn
• [Bug]: Provider turn interrupt failures are silently swallowed — Stop generation looks successful while the turn keeps running #4524 — interrupt failures can be hidden while Stop appears successful
• [Bug]: Remote stop button gives no feedback and leaves thread stuck in Thinking #8618 — reliability and feedback problems when stopping a remote turn
• No keyboard shortcut to interrupt a running turn #5667 — discusses the common “notice a turn going wrong, stop, and clarify” workflow, but focuses on the missing keyboard shortcut

Impact

Frequent workflow disruption