fix: improve issue-triage prompt robustness to prevent no-output failures#10504
Merged
Conversation
…ures
Three targeted fixes to the Agentic Triage workflow prompt:
1. Add explicit `get_file_contents` tool reference with owner/repo params
for reading the labels configuration file, so the agent knows which
MCP tool to use.
2. Make web-fetch playground verification conditional ("if the tool is
available") since web_fetch may not be registered as an MCP tool in
all environments.
3. Add a fallback "Important" section reinforcing the requirement to call
at least one safe output tool before finishing, with explicit guidance
to call `noop` if errors are encountered.
Agent-Logs-Url: https://github.com/microsoft/typespec/sessions/1a40bdca-9a2a-4fae-bf5f-42d3cc86847c
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Debug Agentic Triage workflow failure
fix: improve issue-triage prompt robustness to prevent no-output failures
Apr 27, 2026
timotheeguerin
requested review from
AlitzelMendez,
bterlson,
chrisradek,
markcowl and
witemple-msft
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agentic Triage workflow (run 24996553319) produced no safe outputs despite the agent running for ~4 minutes. This is the second failure after PR #10502 fixed tool name references — the agent still silently failed to call any safe output tool.
Analysis of the generated prompt and MCP gateway logs revealed three issues:
get_file_contentstool reference: The prompt said "read the fileeng/common/config/labels.ts" without specifying the MCP tool name or parameters. Now explicitly referencesget_file_contentswithowner/repo.web-fetchreference: The prompt unconditionally instructed the agent to "Useweb-fetchto verify the playground link", but onlysafeoutputsandgithubMCP servers were registered —web-fetchwas not available. Changed to conditional: "If theweb_fetchtool is available, use it to verify..."## Importantsection reinforcing the requirement to call at least one safe output tool (add_comment,add_labels, ornoop) before finishing, with guidance to callnoopon errors.