Skip to content

Conversation

@westey-m
Copy link
Contributor

@westey-m westey-m commented Jan 22, 2026

Motivation and Context

Currently there is confusion about ChatMessageStore. Many people assume based on the name that it is a full CRUD abstraction for storing chat history. The intention though is to just provide ChatHistory to an Agent per run and store the results of the agent.

A ChatHistoryProvider implementation may of course use a full CRUD abstraction for loading and saving messages, and we may considering providing something like that in future.

#1712

Description

  • Rename ChatMessageStore to ChatHistoryProvider

Contribution Checklist

  • The code builds clean without any errors or warnings
  • The PR follows the Contribution Guidelines
  • All unit tests pass, and I have added new tests where possible
  • Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

Copilot AI review requested due to automatic review settings January 22, 2026 14:36
@markwallace-microsoft markwallace-microsoft added .NET workflows Related to Workflows in agent-framework labels Jan 22, 2026
@github-actions github-actions bot changed the title Rename ChatMessageStore to ChatHistoryProvider .NET: Rename ChatMessageStore to ChatHistoryProvider Jan 22, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request renames ChatMessageStore to ChatHistoryProvider throughout the codebase to better reflect its purpose. The name ChatMessageStore implied it was a full CRUD abstraction for storing chat history, when the actual intention is to provide chat history to an agent per run and store the results of the agent's execution.

Changes:

  • Renamed the core abstraction class from ChatMessageStore to ChatHistoryProvider
  • Renamed all implementations: InMemoryChatMessageStoreInMemoryChatHistoryProvider, CosmosChatMessageStoreCosmosChatHistoryProvider, WorkflowMessageStoreWorkflowChatHistoryProvider
  • Updated all properties, parameters, variables, and factory methods to use the new naming convention
  • Updated all unit tests, integration tests, and samples to reflect the new naming
  • Updated XML documentation and comments throughout

Reviewed changes

Copilot reviewed 43 out of 43 changed files in this pull request and generated 9 comments.

Show a summary per file
File Description
ChatHistoryProvider.cs Core abstraction class renamed with updated documentation
InMemoryChatHistoryProvider.cs In-memory implementation renamed with updated documentation
CosmosChatHistoryProvider.cs Cosmos DB implementation renamed with updated documentation
WorkflowChatHistoryProvider.cs Workflow implementation renamed
ChatClientAgent.cs Updated to use ChatHistoryProvider throughout
ChatClientAgentThread.cs Updated property names and documentation
ChatClientAgentOptions.cs Updated factory property name
Extension files Renamed extension classes and methods
Test files Updated all test classes and methods
Sample files Updated all sample code

@westey-m westey-m added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@westey-m westey-m added this pull request to the merge queue Jan 23, 2026
Merged via the queue into microsoft:main with commit 21e00c0 Jan 23, 2026
14 checks passed
@westey-m westey-m changed the title .NET: Rename ChatMessageStore to ChatHistoryProvider .NET: [BREAKING] Rename ChatMessageStore to ChatHistoryProvider Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

.NET workflows Related to Workflows in agent-framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants