AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoNeeds helpSolved

    Agent file errors "deprecated infer" / "unknown tool reference" after VS Code 1.113 update

    After updating VS Code to 1.113.0 on Windows 11 (10.0.22631) with the microsoft/mcp extension 1.0.4, the Problems panel shows 14 errors in managed agent files: deprecated infer attributes in azure-cost-optimize.agent.md, azqr-cost-optimize.agent.md, and azure-iac-generator.agent.md, plus unknown tool references in Plan.agent.md, Ask.agent.md, and Explore.agent.md. These are system files, not user code. Why did this happen and how do I fix it?

    Originally asked on GitHub: https://github.com/microsoft/mcp/issues/2237

    1 answer

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: fixed upstream — the maintainer confirmed none of the errors came from the microsoft/mcp VSIX. They were two separate issues in other components, both resolved.

      The three Azure agent files (azure-cost-optimize.agent.md, azqr-cost-optimize.agent.md, azure-iac-generator.agent.md) were bundled by GitHub Copilot for Azure; the deprecated infer attributes were fixed in microsoft/GitHub-Copilot-for-Azure#1455, released in GitHub Copilot for Azure 1.0.188.

      The Ask.agent.md, Explore.agent.md, and Plan.agent.md files are generated by GitHub Copilot Chat under globalStorage; the diagnostics regression that flagged unknown tool references there was fixed in Copilot Chat 0.41.2 and VS Code 1.114.

      The maintainer states that current packages no longer contain the reported deprecated infer metadata or stale frontmatter tool names.

      What to do:

      1. Update GitHub Copilot for Azure to 1.0.188 or newer.
      2. Update GitHub Copilot Chat to 0.41.2 or newer, and VS Code to 1.114 or newer.
      3. Do not manually edit these files — extension agent files are overwritten on update, and user agent files are managed by VS Code/Copilot.

      If the errors still reproduce with current VS Code and GitHub Copilot for Azure, open a new issue in the owning repository for the component that still shows the errors, with current versions and the diagnostics. General advice: after a VS Code update, update related extensions too before troubleshooting agent file warnings, since these errors came from stale bundled metadata rather than from the mcp extension itself.

      Did this work for you?

    Add your answer or comment