Skip to content

Thinking Task: Improve Tool Content in Human-in-the-Middle #120

Description

@Asaf-prog

Thinking Task: Improve Tool Content in Human-in-the-Middle

Context

Today, when a tool requires Human-in-the-Middle approval, the content shown to the user is not always clear or useful enough.

I would like us to think about what should be displayed there so the user can understand, in a simple and natural way, what the tool is about and what they are approving.

The goal is not necessarily to expose all tool arguments or technical details.

Goal

Come up with a better, more human-friendly representation of a tool in the approval UI.

It should be:

  • Clear.
  • Concise.
  • Easy for a non-technical user to understand.
  • Generic enough to work across different tools.
  • Helpful for making an informed Approve / Deny decision.

Open Question

What is the right content and structure to show for a tool in Human-in-the-Middle?

I’d like to hear different ideas and approaches before deciding on an implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    advanceenhancementNew feature or requesthelp wantedExtra attention is neededquestionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions