dotnet / dotnet/aspnetcore

Components.AI: Implement explicit per-call tool display modes

Open
#68,416 0 comments 0 reactions 0 assignees View on GitHub
api-proposal 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.

Tool calls currently render nothing accidentally, and there is no explicit contract for built-in or custom presentation.

### Describe the solution you'd like

Support exactly three modes resolved per call: hidden by default, an opt-in collapsed built-in view showing name/arguments/result/status, or a custom renderer keyed by tool name. Update pending/running/succeeded/failed/cancelled state in place. Approval wrappers must still render when the underlying call is hidden.

### Additional context

Leaf task for #68227 requirements F11 and J7 and decision D14. Public API review is required.

See: https://github.com/dotnet/aspnetcore/pull/68333#issuecomment-5413299117

Contributor guide

Open the contributing guide

Research direction

Start with parent issue #68227, requirements F11 and J7, and decision D14, then review the linked pull-request discussion. Confirm the public API for the three per-call display modes, state transitions, custom renderers, and approval wrappers. Done means each mode and pending/running/succeeded/failed/cancelled update behavior is specified and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
ai, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.