Skip to content

Bug: ChatHistory management is not supported for thinking model #12276

@HuskyDanny

Description

@HuskyDanny

I am using AzureChatCompletion as agent client which uses o3-mini to use function calling. Since I am using Service selector, which could move from 4o to o3-mini, the inconsistency of the two models is the root cause, but SK didn't handle automatic convert system message to developer message for thinking models, leading unexpected behavior. I thought this is the fundamental issue and surprised no one raised it, are there any workarounds or best practices for this?

For ChatCompletionAgent class:

Image

I think it might need to check what the service selector returns, and to decide to add developer message or system message.

Metadata

Metadata

Assignees

Labels

agentsbugSomething isn't working

Type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions