镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

.NET: Explain DevUI session persistence across requests - #9006

Open
Naveen Chatlapalli (1aifanatic) wants to merge 2 commits into
microsoft:mainfrom
1aifanatic:contrib/7435-devui-session-guide
Open

Naveen Chatlapalli (1aifanatic) wants to merge 2 commits into
microsoft:mainfrom
1aifanatic:contrib/7435-devui-session-guide

Conversation

@1aifanatic

Copy link
Copy Markdown
Contributor

Motivation & Context

A custom ChatHistoryProvider does not persist the enclosing AgentSession between DevUI HTTP requests. The setup guide currently mentions session stores only for function approval, leaving users with stateful history providers to discover the same requirement themselves.

Description & Review Guide

  • What are the major changes? Add an in-memory session store to the usage registration and explain conversation IDs, agent session state, custom history providers, protocol conversation storage, and persistent stores.
  • What is the impact of these changes? The development setup now preserves session state across turns. Documentation only; guidance was checked against the hosted Responses executor's session-store branch and existing session-store APIs. The relative hosting-guide link resolves.
  • What do you want reviewers to focus on? The distinction between history storage and agent session storage for the configuration reported in the issue.

Related Issue

Fixes #7435

Contribution Checklist

  • The code builds clean without any errors or warnings
  • All unit tests pass, and I have added new tests where possible
  • The PR follows the Contribution Guidelines
  • This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
  • This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and the title prefix in sync automatically.

Copilot AI balanced review requested due to automatic review settings October 3, 2026 04:46
@agent-framework-automation agent-framework-automation Bot added documentation Usage: [Issues, PRs], Target: documentation in the code base and learn docs .NET Usage: [Issues, PRs], Target: .Net labels Oct 3, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

The updated sample enables strict isolation without configuring the required isolation-key provider, causing session requests to fail.

Review effort: Balanced
Findings: 1 Medium severity

Open (1)
What changed in this PR

Documents how DevUI persists agent sessions across HTTP requests and clarifies session storage responsibilities.

Changes:

  • Adds an in-memory session store to the setup example.
  • Distinguishes agent sessions, chat history, and protocol conversation storage.
  • Links production persistence and isolation guidance.
File Description
dotnet/​src/​Microsoft.Agents.AI.DevUI/​README.md Adds DevUI session-persistence setup and guidance.

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

Comment thread dotnet/src/Microsoft.Agents.AI.DevUI/README.md Outdated

This branch was successfully deployed

1 active deployment
github-app-auth — 8b1f47ce Deployed Oct 3, 2026 by 1aifanatic via add_label #24361
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Usage: [Issues, PRs], Target: documentation in the code base and learn docs .NET Usage: [Issues, PRs], Target: .Net

Projects

None yet

Development

Successfully merging this pull request may close these issues.

.NET: [Bug]: DevUI always sends new session

2 participants