Regenerate agent conversation message
Regenerate the AI response for a specific message in an agent conversation and stream the new answer over Server-Sent Events.
Constraints:
- Only the last message in the conversation can be regenerated.
- The target message must be of type bot_response.
Request body:
All request-body fields are optional. When omitted, the server reuses the original model/context. The body supports:
- filters
- chatMode
- modelKey
- modelName
- modelFriendlyName
- timezone
- currentTime
- tools
Streaming behavior:
The response is delivered as text/event-stream. Stable events are connected, complete, and error. Additional agent/tool lifecycle events may be forwarded by the backend and should be treated as informational updates.
Validation failures on params/body are returned as normal HTTP 400 responses before the stream starts. Valid-shape requests that fail conversation lookup or regenerate rules are reported as SSE error events after stream initialization.
Path parameters
Stable key identifying the agent that owns this conversation.
ID of the agent conversation containing the target message.
ID of the bot-response message to regenerate.
Request body
Example request
{
"modelKey": "05438a37-68f2-4641-a8dc-6c47e63278ca",
"modelName": "gpt-5.4-mini",
"modelFriendlyName": "mini",
"chatMode": "internal_search",
"timezone": "Asia/Calcutta",
"currentTime": "2026-05-11T15:43:21+05:30",
"tools": [
"jira.create_issue",
"confluence.search_content"
]
}Response
SSE stream established.
Stable event names:
- connected — confirms the stream is open
- complete — returns the updated conversation plus metadata
- error — reports lookup failures, authorization failures on the conversation, or regenerate-rule failures after the stream has started
Additional backend-defined agent/tool events may be emitted. Clients should ignore unknown event names.