Add further chat history docs updates. (#785)

Author: westey-m

agent-framework/user-guide/agents/TOC.yml

@@ -10,7 +10,7 @@
   href: agent-middleware.md
 - name: Agent Retrieval Augmented Generation (RAG)
   href: agent-rag.md
-- name: Agent Memory
+- name: Agent Chat History and Memory
   href: agent-memory.md
 - name: Agent Observability
   href: agent-observability.md

agent-framework/user-guide/agents/agent-memory.md

@@ -1,6 +1,6 @@
 ---
-title: Agent Memory
-description: Learn how to use memory with Agent Framework
+title: Agent Chat History and Memory
+description: Learn how to use chat history and memory with Agent Framework
 zone_pivot_groups: programming-languages
 author: markwallace
 ms.topic: reference
@@ -9,15 +9,13 @@ ms.date: 09/24/2025
 ms.service: agent-framework
 ---
 
-# Agent Memory
+# Agent Chat History and Memory
 
-Agent memory is a crucial capability that allows agents to maintain context across conversations, remember user preferences, and provide personalized experiences. The Agent Framework provides multiple memory mechanisms to suit different use cases, from simple in-memory storage to persistent databases and specialized memory services.
+Agent chat history and memory are crucial capabilities that allow agents to maintain context across conversations, remember user preferences, and provide personalized experiences. The Agent Framework provides multiple features to suit different use cases, from simple in-memory chat message storage to persistent databases and specialized memory services.
 
 ::: zone pivot="programming-language-csharp"
 
-The Agent Framework supports several types of memory to accommodate different use cases, including managing chat history as part of short term memory and providing extension points for extracting, storing and injecting long term memories into agents.
-
-## Chat History (short term memory)
+## Chat History
 
 Various chat history storage options are supported by the Agent Framework. The available options vary by agent type and the underlying service(s) used to build the agent.
 

agent-framework/user-guide/agents/agent-rag.md

@@ -297,4 +297,4 @@ Each connector provides the same `create_search_function` method that can be bri
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Agent Memory](./agent-memory.md)
+> [Agent Chat History and Memory](./agent-memory.md)

agent-framework/user-guide/agents/multi-turn-conversation.md

@@ -17,7 +17,14 @@ The Microsoft Agent Framework provides built-in support for managing multi-turn
 
 For example, when using a ChatClientAgent based on a foundry agent, the conversation history is persisted in the service. While, when using a ChatClientAgent based on chat completion with gpt-4.1 the conversation history is in-memory and managed by the agent.
 
-The differences between the underlying threading models are abstracted away via the `AgentThread` type.
+The `AgentThread` type is the abstraction that represents a conversation thread with an agent.
+`AIAgent` instances are stateless and the same agent instance can be used with multiple `AgentThread` instances. All state is therefore preserved in the `AgentThread`.
+An `AgentThread` can both represent chat history plus any other state that the agent needs to preserve across multiple interactions.
+The chat history may be stored in the thread itself, or remotely, with the `AgentThread` only containing a reference to the remote chat history.
+The `AgentThread` state may also include memories or references to memories stored remotely.
+
+> [!TIP]
+> To learn more about Chat History and Memory in the Agent Framework, see [Agent Chat History and Memory](./agent-memory.md).
 
 ### AgentThread Creation
 
@@ -42,7 +49,6 @@ response = await agent.RunAsync("Hello, how are you?");
 
 ::: zone-end
 
-
 ### AgentThread Storage
 
 `AgentThread` instances can be serialized and stored for later use. This allows for the preservation of conversation context across different sessions or service calls.
@@ -215,7 +221,6 @@ async def multi_turn_example():
         print(f"Agent: {response3.text}")  # Should remember previous context
 ```
 
-
 ::: zone-end
 
 ## Next steps