Stop and Regenerate Controls
Let users halt a bad answer and ask again without losing the conversation.
What it adds
Stop and regenerate actions on an in-progress or completed AI response, with the prior context preserved.
What your agent is told to do
5
What your agent is told to do
5-
1
Wire stop to an actual cancellation of the server-side run, propagated to the provider request, so generation ends rather than continuing invisibly.
-
2
Keep whatever text arrived before the stop, store it marked as stopped by the user, and make that state visible in the transcript rather than deleting it.
-
3
Build regenerate from the conversation state as it stood before the response being replaced, never from the abandoned partial output.
-
4
Retain previous attempts and let the user move between them, so regenerating does not destroy an answer that was better than its replacement.
-
5
Streaming AI Responses owns transport and incremental rendering. This entry owns the user-facing controls and the run lifecycle around them. Do not reimplement stream handling here.
Edge cases it handles
8
Edge cases it handles
8- Hiding incoming text without aborting the request leaves the model generating and the account paying. Stop must cancel the run at the server and at the provider where the provider supports it.
- Partial output that is silently discarded looks like a bug, and partial output shown as if complete is worse. Keep it, label it as stopped, and disable any action that treats it as a finished answer.
- Regenerating from the unfinished response feeds the model its own truncated text and produces a continuation rather than a fresh answer. Rebuild the request from the ancestor messages only.
- Usage accounting must reflect what actually happened: a stopped run consumes what it generated, and a regeneration is a new run, not a free retry. Reconcile against the provider's reported usage rather than assuming.
- A tool call that already wrote data, sent a message, or charged something cannot be undone by stopping. Detect completed side effects, surface them to the user, and never replay them on regenerate.
- Rapid repeated presses of regenerate must not launch parallel runs against the same message. Disable the control while a run is in flight.
- Stopping must leave the conversation in a state the user can continue from, with the input available and no orphaned pending row in the transcript.
- A run that has already finished server-side when stop is pressed should complete cleanly rather than being recorded as stopped.
Definition of done
8
Definition of done
8- Stop cancels the run at the server and the provider, and generation verifiably ends.
- Partial output is retained in the transcript, clearly marked as stopped, and cannot be mistaken for a complete answer.
- Regeneration rebuilds the request from prior context and never includes the abandoned partial response.
- Stopped runs and regenerations are accounted for accurately against real reported usage.
- Tool calls with completed side effects are surfaced and never re-executed by a regeneration.
- Repeated presses cannot start parallel runs, and previous attempts remain reachable.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Chat Attachments
AI Chat Attachments
Attach files to a conversation and let the assistant use what it is allowed to read.
What it does
File upload on an AI conversation, with parsing, retrieval of relevant sections, and per-conversation access scoping.
How it works
- 1 Reuse the app's existing upload, storage, and virus-scanning path rather than adding a second one, and declare an explicit list of accepted file types and a size ceiling per file and per conversation.
- 2 Parse each attachment into text and structure in a background job, store the result, and show the attachment as pending until parsing succeeds so the user is never told the assistant has read something it has not.
- 3 Retrieve and send only the sections relevant to the current question. Sending whole documents on every turn burns the context window and the budget for no gain.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-chat-attachments
AI Suggested Support Answers
AI Suggested Support Answers
Give support agents a grounded first draft instead of a blank reply box.
What it does
A draft reply composed for the agent from the ticket, the customer's account state, and the approved internal knowledge, with sources attached and no ability to send itself.
How it works
- 1 Ground every draft in retrieved material: the ticket thread, the account's real state, and articles from the approved knowledge set. Attach the sources used to the draft so the agent can open and check each one.
- 2 Load the draft into the agent's normal reply editor, unsent and fully editable. There is no path in this feature that sends a message to a customer without an agent pressing send.
- 3 Define the commitments the app is not allowed to make in a draft — refunds, credits, delivery dates, guarantees of a fix — and strip or refuse any draft containing them, leaving that part for the agent to write.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-suggested-support-answers
AI Conversation Branching
AI Conversation Branching
Explore an alternate path from an earlier message without losing the original.
What it does
A message graph that lets a conversation fork at any point, with each branch keeping its own history and active state.
How it works
- 1 Change the conversation's storage from an ordered list to a graph where every message names its parent, and migrate existing conversations into that shape as single-path graphs.
- 2 Define the active branch as a stored pointer to a leaf message, and derive everything rendered from the path between the root and that pointer.
- 3 Give each branch its own summary, memory, and derived context. Carrying one summary across siblings leaks the abandoned path back into the new one.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-conversation-branching
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.