You can now continue a Chat or AssemblyChat conversation by using a “sticky” URL (?sticky=<guid>). The same task ID is reused, preserving the conversation history across requests.
PDF files generated from chat responses include a generation number in their filename (e.g., report_g2.pdf), giving each turn a unique, stable download link.
Improvements
Chat output files are now saved with a generation suffix (e.g., assembly_chat_g3.txt), preventing previous results from being overwritten.
Every chat turn is automatically appended to the conversation history, so follow‑up queries have full context.
The chat result now includes the original question, the answer, alternative suggestions, and a flag for history, giving you more detailed information in the UI.
Bug Fixes
Fixed sticky‑ID handling for Chat plugins so the ?sticky= parameter works consistently.