better prompt, updated conversation history display

app.py

@@ -55,10 +55,21 @@ with gr.Blocks() as demo:
             history[-1]["content"] = partial_resp
             yield history
 
+    """
     def handle_save(history, chat_id):
         # Saves the chat and returns the updated list for the sidebar
         new_id = save_chat(chat_id, history)
         return new_id, load_history()
+    """
+    def handle_save(history, chat_id):
+        # 1. Save the actual data
+        new_id = save_chat(chat_id, history)
+        # 2. Get the latest from hub
+        current_list = load_history()
+        # 3. Ensure the current one is definitely at the top
+        if [new_id] not in current_list:
+            current_list.insert(0, [new_id])
+        return new_id, gr.update(samples=current_list)
 
     def load_past_chat(selected_list):
         # selected_list comes as [ 'chat_id' ]
@@ -93,4 +104,16 @@ with gr.Blocks() as demo:
         [chatbot, chat_id_state, history_list]
     )
 
+    # 4. "Force Refresh" 
+    # In Gradio, a component's samples are often cached at the moment of the initial load. To ensure the sidebar is truly dynamic, we need to update the gr.Dataset definition and the refresh logic
+    # To update history_list definition, we add samples_per_page explicitly, ensuring it's not cutting off the list early
+    history_list = gr.Dataset(
+        components=[gr.Textbox(visible=False)], 
+        label="Recent Conversations", 
+        samples=load_history(),
+        type="values",
+        samples_per_page=20 # Increase this to see more at once
+    )
+
+
 demo.launch(theme=gr.themes.Soft(), css="styles.css")

core_logic.py

@@ -28,11 +28,9 @@ CORE DIRECTIVES:
 5. RESEARCH: If the user asks about new tech, use your Web Search capability to provide factual, up-to-date documentation.
 
 PERSONALITY:
-1.  "Act as a sarcastic technical editor. Summarize your response as cynical, funny, in few but highly-effective and precise words. No introductory filler. Example: "Explain NFTs." -> "It's a digital receipt for a JPG that tells the world you own the right to be ignored"
-2. So, humor is your way without losing sight of the actual context, and apt responses to all the concerns and queries
-3. FRANK/POLITE: Disagree with the user, if needed; never resort to sycophancy, and suggest better alternatives
-4. HUMBLE: Apologize when mistaken
-
+1. FRANK/POLITE: Disagree with the user, if needed; never resort to sycophancy, and suggest better alternatives
+2. HUMBLE: Apologize when mistaken
+3. FIRST PRINCIPLES: Base your responses and reasoning in Richard Feynman’s first principles thinking. Break down complex problems into fundamental truths and reason up from there
 
 When a user provides files, analyze the code structure and logic before proposing changes.
 """