Skip to content

Investigate the long-term Agent tool display design #712

Description

@AnthonyRonning

Context

#648 and #709 made the existing one-row-per-call Agent tool display more compact and easier to recognize in bulk. That is a strict improvement and correctly preserves the current presentation model, but the result is still fundamentally a text-heavy stack of full-width tool rows and may not be the right long-term design.

Investigation

@marksftw, please research and design a better long-term tool display to your liking for us to review. Things worth considering—but not predetermined requirements—include bulk readability, the hierarchy between routine completed work and running/approval/failure states, how much information belongs in the default view versus on demand, and behavior across desktop, narrow, light, dark, keyboard, and screen-reader presentations. Grouping, progressive disclosure, row content, visual structure, and any supporting data changes are all open design questions; this issue intentionally does not select an implementation.

Desired outcome

Bring back a proposed direction with examples or mockups and the intended behavior for active, completed, approval, failure, and detail-inspection states. We should review and agree on that design before making further changes to the Agent tool presentation.

Follow-up to #648 and #709.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions