Merge pull request #2079 from danielaskdd/fix-cot-render-fall-back

Fix assistant message display with content fallback

Author: danielaskdd

lightrag/api/__init__.py

@@ -1 +1 @@
-__api_version__ = "0216"
+__api_version__ = "0217"

…bui/assets/feature-retrieval-Cz5issgY.js …bui/assets/feature-retrieval-CUau_fDY.jslightrag/api/webui/assets/feature-retrieval-Cz5issgY.js renamed to lightrag/api/webui/assets/feature-retrieval-CUau_fDY.js lightrag/api/webui/assets/feature-retrieval-Cz5issgY.js renamed to lightrag/api/webui/assets/feature-retrieval-CUau_fDY.js

@@ -50,10 +50,10 @@ export const ChatMessage = ({ message }: { message: MessageWithError }) => { //
   // The content to display is now non-ambiguous.
   const finalThinkingContent = thinkingContent
   // For user messages, displayContent will be undefined, so we fall back to content.
-  // For assistant messages, we prefer displayContent and don't fallback to avoid content leakage during thinking
+  // For assistant messages, we prefer displayContent but fallback to content for backward compatibility
   const finalDisplayContent = message.role === 'user'
     ? message.content
-    : displayContent || ''
+    : displayContent || message.content || ''
 
   // Load KaTeX dynamically
   useEffect(() => {