VS Code prompt files: is `mode` deprecated, should I use `agent`?
In the awesome-copilot repo (December 2025), the README links to VS Code's "Custom Chat Modes" docs, but that page now redirects to "Custom Agents" and prompt-file headers changed:
modeshould beagent. Copilot code reviews on this repo suggest the opposite (agent: agent→mode: agent), which seems backwards. How should prompt files and docs be updated? The thread gives no version, OS, or error message; it's a docs/syntax mismatch issue.Originally asked on GitHub: https://github.com/github/awesome-copilot/issues/464
4 answers
The issue is closed as completed: VS Code deprecated the
modeprompt-file header in favor ofagent. The thread names no release version and does not confirm that PR #549 was merged, so treat that as unverified.What the thread establishes:
- Use the
agentheader in.prompt.mdfrontmatter (e.g.agent: agent), notmode. Copilot code reviews that suggest changingagent: agentback tomode: agentare based on the old "Custom Chat Modes" terminology. - Update docs: replace "Custom Chat Modes" with "Custom Agents" or "agent mode" and point links to the current VS Code page (code.visualstudio.com/docs/copilot/customization/custom-agents), since the old page redirects there.
- A contributor said their prompt wasn't correctly updated based on the older header and created PR #549 to fix it; if your generated prompt is stale, check that PR or its merge status.
Unanswered in the thread: whether the outdated
modeheader is why the "Install in Visual Studio" button doesn't work — no connection was confirmed.Did this work for you?- Use the
What @yeelam-gordon tried on GitHub (Outcome unclear)
A contributor said their prompt wasn't correctly updated based on the older header and created PR #549 to fix it.
Source: https://github.com/github/awesome-copilot/issues/464#issuecomment-3723105503 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
The reporter documented that VS Code prompt-file headers changed (
mode→agent) and that the README's "Custom Chat Modes" link now redirects to "Custom Agents", proposing doc updates.Source: https://github.com/github/awesome-copilot/issues/464 (opens external site)
Did this work for you?What @Khaos66 tried on GitHub (Outcome unclear)
A commenter asked whether the outdated
modeheader is why the "Install in Visual Studio" button doesn't work.Source: https://github.com/github/awesome-copilot/issues/464#issuecomment-3695069246 (opens external site)
Did this work for you?
Related questions
- Which MCP servers does an awesome-copilot prompt or chat mode need?
- How do I use awesome-copilot without an MCP server?
- Is Docker required to use the awesome-copilot MCP server?
- Why is the awesome-copilot plugin missing from the Copilot CLI marketplace?
- az devops invoke fails with 'could not convert string to float' when using --api-version