microsoft / microsoft/Power-CAT-Copilot-Studio-Kit

Bug: Agent Review Tool - Review actions and finding navigation can be difficult to use (Standard Harness)

Open
#876 0 comments 0 reactions 1 assignee View on GitHub

@Ramakrishnan24689 is already working on this.

Since Sep 18, 2026.

bug
Dominant language
TypeScript
Stars
450
Forks
95
Avg merge
26m
Merged PRs (30d)
5

Description

Description

A review with many affected items can be difficult to navigate. Starting another review can require extra steps, and the result summary can show unnecessary technical information.

Example

A test finding affects ten inputs. The details view shows a long list and more than one set of Previous and Next controls. A maker must use an indirect menu to review the connected agent Returns Helper. The result summary also shows processing details that do not help the maker understand the score.

Steps to reproduce

Steps to reproduce

  1. Open a test review with several affected items.

  2. Move through the finding details.

  3. Start a review for a connected agent or an agent from an uploaded test solution.

  4. Inspect the review summary.

Expected behavior

Show one complete affected item at a time. Provide a searchable item selector and one clear criterion pager. Provide a direct Review action where possible. Keep the normal summary focused on Overall, Pattern, Instructions, Agent, Reviewed, and Reviewed by.

Actual behavior

In the evaluated version, findings with many affected items created long content, and repeated navigation controls made it unclear what would change. Reviewing connected agents required extra steps. The summary repeated score information and showed technical processing details instead of useful reviewer context.

Environment

No response

Additional context or logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.