Remove invalid tools list from whats-new-from-release-notes agent#36984
Merged
wadepickett merged 2 commits intomainfrom Apr 13, 2026
Merged
Remove invalid tools list from whats-new-from-release-notes agent#36984wadepickett merged 2 commits intomainfrom
wadepickett merged 2 commits intomainfrom
Conversation
Agent-Logs-Url: https://github.com/dotnet/AspNetCore.Docs/sessions/3e0ae18e-31ba-4964-875e-cc73813abad8 Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix invalid tools property in whats-new-from-release-notes agent
Remove invalid tools list from whats-new-from-release-notes agent
Apr 13, 2026
Contributor
|
@tdykstra, Need your review/approval: I needed to remove the tools section. The tools were named incorrectly so they didn't load, but by default if zero tools were specified, all tools available would have loaded anyway which is what was needed. So removing the tool list from this agent for creating the What's New articles. |
tdykstra
approved these changes
Apr 13, 2026
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.
The
toolsproperty in the agent frontmatter listed unrecognized aliases (githubread,lexical-code-search,semantic-code-search). Unrecognized names are silently ignored, so the agent launched with no tools at all — unable to read, edit, create, or search files. This caused PR #36983 to fail.toolsblock from.github/agents/whats-new-from-release-notes.agent.mdtoolsis omitted, the agent gets all available tools by default (read,edit,search,execute,github/*)[Added by WadePickett]
The tools that were needed but not loaded are listed in this error that was returning when the agent was run:
""Status: Blocked — agent environment misconfigured. This session only has report_progress and skill tools available. File I/O (bash, view, edit, create), GitHub API (get_file_contents), and code search tools are all missing. No changes were made.
Original prompt
The custom agent at
.github/agents/whats-new-from-release-notes.agent.mdhas an invalidtoolsproperty in its YAML frontmatter that prevents the agent from having any file operation tools when it runs.The current frontmatter includes:
These tool names (
githubread,lexical-code-search,semantic-code-search) are not recognized tool aliases for the Copilot cloud agent. The valid tool aliases areread,edit,search,execute, andgithub/*. Unrecognized tool names are silently ignored, which means the agent launches with no tools at all — it can't read, edit, create, or search files.This caused PR #36983 to fail completely — the agent reported: "session had no file operation tools (bash, edit, view, grep, glob) available. Only
report_progressandskillwere provisioned."Fix: Remove the
toolsproperty entirely from the YAML frontmatter in.github/agents/whats-new-from-release-notes.agent.md. Whentoolsis omitted, the agent gets access to all available tools by default, which is the desired behavior since the agent needs to read files fromdotnet/core, create include files, edit the What's New article, and search the repository.The corrected frontmatter should be:
Only remove lines 10-13 (the
tools:block). Do not change anything else in the file.The following is the prior conversation context from the user's chat exploration (may be truncated):
User: The tools needed for this agent to run were not loaded. what lines should be added to the agent and where so that next time it has all the tools it needs? Or is there a different way this should be done and not done as an agent?
Assistant:
Let me investigate the PR and the agent configuration to understand what's going on here.
Assistant: Now let me look at how the Copilot coding agent is configured in this repository:
Assistant: Now I can see the issue clearly. Let me look at what tools the agent declares vs. what it actually needs:
Assistant: Now I have a clear picture. Let me look at the PR's description more carefully and check the agent file's
toolsproperty.The issue is clear from both the PR description and the agent configuration. Here's the analysis:
The Problem
The PR description states exactly what went wrong:
The agent file at
.github/agents/whats-new-from-release-notes.agent.mdhas this in its YAML frontmatter:The
toolslist only includes read-only tools. The Copilot coding agent (cloud agent) needs file operation tools to actually create and edit files in the repository. Because thetoolsproperty was explicitly set to a restrictive list, the agent was denied access to the tools it needs to write files —edit,read,search, andexecute(shell/bash).The Fix
According to the Custom agents configuration docs, the available tool aliases for cloud agent are:
executebashorpowershellreadvieweditstr_replace,str_replace_editorsearchsearchLine 10-13 in
.github/agents/whats-new-from-release-notes.agent.mdshould be changed from:to one of these options:
Option A: Remove the
toolsproperty entirely (recommended)Simply delete lines 10-13. When
toolsis omitted, the agent gets access to all available tools by default, including file editing, shell execution, search, and the built-in GitHub MCP server. This is the simplest and most robust fix.Option B: Explicitly list the needed tools