Skip to content

Document AI Management chat history#25798

Open
enisn wants to merge 1 commit into
devfrom
feature/ai-chat-history-docs
Open

Document AI Management chat history#25798
enisn wants to merge 1 commit into
devfrom
feature/ai-chat-history-docs

Conversation

@enisn

@enisn enisn commented Jul 10, 2026

Copy link
Copy Markdown
Member

Documentation for https://github.com/volosoft/volo/pull/22563.

ABP Studio companion: https://github.com/volosoft/abp-studio/pull/5162

Summary

  • document per-user server-side conversation and Agent Framework session persistence
  • list the conversation application service operations and HTTP endpoints
  • update MVC, Angular, and Blazor component guidance to use server-generated conversation IDs
  • distinguish persisted conversations from explicitly enabled ephemeral chat behavior
  • remove outdated browser and local-storage claims

Validation

  • verified service names, DTOs, routes, and component parameters against the implementation
  • confirmed no stale client-side/local-storage claims remain in the AI Management guide
  • git diff --check

Copilot AI review requested due to automatic review settings July 10, 2026 17:10

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.

Pull request overview

Updates the AI Management module documentation to reflect server-side, per-user persisted chat conversations (including Agent Framework session persistence) and to align the MVC/Angular/Blazor integration guidance with server-generated conversation IDs rather than client-side storage.

Changes:

  • Documented server-side conversation history, ownership/permission expectations, and the IChatConversationAppService + /api/chat-conversations endpoint surface.
  • Updated MVC widget, Angular component, and Blazor component docs to use server-generated conversation IDs and clarified ephemeral chat behavior options.
  • Adjusted the JavaScript API guidance to reflect conversation attachment semantics and clarified that clearing the UI does not delete server history.

OnFirstMessage="@HandleFirstMessage" />
```

Create the conversation before rendering or enabling the component:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants