dotnet / dotnet/aspnetcore

Components.AI: Render and manage pending follow-up messages

Open
#68,402 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-blazor-builtin-components Priority:0
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is your feature request related to a problem? Please describe the problem.

Pending follow-ups need a visible, stable UI outside the composer while an answer is streaming.

### Describe the solution you'd like

Render ordered pending messages at the end of the conversation, outside the composer, with an individually accessible remove action and clear distinction from already-dispatched messages.

### Additional context

Leaf task for #68227 requirement C11. Depends on queue state and stable message identity.

Contributor guide

Open the contributing guide

Research direction

Start from the Components.AI implementation and requirement C11 in issue #68227, then trace the queue state and stable message identity used during streaming. Confirm where conversation messages are rendered and how removal actions are exposed. Done means pending follow-ups appear in order outside the composer, remain distinct from dispatched messages, and each has an accessible remove action.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.