[BUG] Tool or toolset has been renamed in agent.md tools front matter

[o-hook]

Describe the bug
After installing an APM package with a *.agents.md file with --target copilot option, there is a warning (underline in the file): E.g.: "Tool or toolset 'XYZ' has been renamed, use 'vscode/XYZ' instead.".

This occurs for the following "tools" specified in the front matter of an agent.md file:

• askQuestions (--> vscode/askQuestions)
• runInTerminal (--> execute/runInTerminal)
• getTerminalOutput (--> execute/getTerminalOutput)
• createFile (--> edit/createFile)
• fetch (--> web/fetch)
• listDirectory (--> search/listDirectory)

To Reproduce
Steps to reproduce the behavior:

1. Run command 'apm install repo/apm-package'
2. With parameters ' --target copilot'
3. Open *.agents.md in VSCODE
4. See error

Expected behavior
Paths/references to tools are correct in VSCODE

Environment (please complete the following information):

• OS: macOS
• Python Version: 3.14.5
• APM Version: 0.27.0
• VSCode Version: 1.121.0

Logs

Additional context
Add any other context about the problem here.

[github-actions]

Triage Panel Verdict -- #2465

Thanks for the report, @o-hook.

Summary

When APM installs a package with --target copilot, the generated *.agents.md files contain tool references using old, unnamespaced names (e.g. askQuestions, runInTerminal, fetch). VSCode Copilot now expects namespaced names (vscode/askQuestions, execute/runInTerminal, web/fetch), so it flags every affected file with "Tool or toolset has been renamed" warnings. The tool name table in APM's copilot target generator has not been updated to match the current VSCode schema.

Panel Findings

DevX UX Expert: A user installing an APM package and immediately seeing editor warnings in every generated file reads as broken output, even if the tools still work at runtime. First-run quality matters; stale tool names should not land in generated files.

Python Architect: The fix is a lookup-table update in the copilot target integration layer -- map old unnamespaced tool names to their current namespaced equivalents. The list from the issue (askQuestions -> vscode/askQuestions, runInTerminal -> execute/runInTerminal, getTerminalOutput -> execute/getTerminalOutput, createFile -> edit/createFile, fetch -> web/fetch, listDirectory -> search/listDirectory) is the complete set reported.

APM CEO: Quality bug affecting copilot target output. The fix is bounded and well-specified. Accepted.

Decision

Dimension	Value
Type	type/bug
Theme	theme/portability
Area	area/distribution
Priority	priority/low
Milestone	(omitted -- maintainer call)

Suggested next action: Update the tool name mapping table in the copilot target generator to use the current namespaced names for the six tools listed in the issue. Add a regression test that asserts the generated *.agents.md content uses namespaced tool names for known renames.

---

Triage status: agentic proposal pending human ratification.
Silence is approval. Maintainers can:

• Override any label or milestone above by editing it directly --
  human edits are authoritative and will not be reverted on
  subsequent runs.
• Re-trigger triage by applying the status/needs-triage label, or
  by removing status/triaged to enroll the issue in the next
  daily sweep.

Posted by the Triage Panel workflow. See .apm/skills/apm-triage-panel for the panel skill.

Generated by Triage Panel · 88.9 AIC · ⌖ 9.15 AIC · ⊞ 9.2K · ◷