microsoft / microsoft/agent-framework

.NET: [Docmentation]: Unclear how to show reasoning in AG-UI

Open
#8,426 4 comments 0 reactions 1 assignee View on GitHub

@moonbox3 is already working on this.

Since Sep 16, 2026.

.NET likely-fixed
Dominant language
Python
Stars
13.6k
Forks
2.3k
Avg merge
2d 45m
Merged PRs (30d)
358

Description

Description

I created several agents and exposed them using MapAGUIServer.

AG-UI and CopilotKit have support for reasoning messages but Agent Framework does not seem to send them to the frontend.

Update: it turns out that setting the Reasoning property in ChatOptions of HarnessAgents makes this work.
Please interpret this issue as a documentation issue instead of a bug.

Code Sample

I used e.g. a HarnessAgent, both with and without BackgroundAgents, and I used gpt-5.6-luna as LLM

return sp.GetRequiredService<IChatClient>().AsHarnessAgent(new HarnessAgentOptions
        {
            Name = name,
            HarnessInstructions = Instructions,
            ChatOptions = new ChatOptions { Tools = tools },
            AIContextProviders = contextProviders,
            BackgroundAgents = SpecialistAgents.ResolveAll(registry),
            // Keeps the harness re-invoking itself turn-over-turn until every delegated background task reaches a
            // terminal state.
            LoopEvaluators = [new BackgroundTaskCompletionLoopEvaluator()],
            LoopAgentOptions = new LoopAgentOptions { MaxIterations = 10 },
            DisableWebSearch = true,
            OpenTelemetrySourceName = GenAiSourceNames.Agents,
        });
Error Messages / Stack Traces

There is no error, it is just that the REASONING_* messages are not sent to the frontend

Package Versions

Microsoft.Agents.AI.Hosting.AGUI.AspNetCore: 1.21.0-preview.260911.1, Microsoft.Agents.AI.Harness: 1.21.0, Aspire.Azure.AI.OpenAI: 13.5.4-preview.1.26464.4

.NET Version

.NET 10

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.