Does GitHub Copilot support AGENTS.md?
Partly. The Copilot cloud agent, code review, the Copilot CLI and VS Code chat read AGENTS.md. Copilot Chat on GitHub.com, Visual Studio and JetBrains chat do not, so keep a copilot-instructions.md too.
GitHub Copilot reads copilot-instructions.md everywhere it supports instructions, but reads AGENTS.md only in some places. So Copilot users need both files, with AGENTS.md as the source and a short copilot-instructions.md.
Last verified 2026-11-13 against the vendor documentation. From GitHub's custom instructions support matrix:
| Copilot surface | copilot-instructions.md | AGENTS.md |
|---|---|---|
| Chat on GitHub.com | Yes | No |
| Cloud agent | Yes | Yes |
| Code review on GitHub.com | Yes | Yes |
| VS Code chat | Yes | Yes |
| Visual Studio chat | Yes | No |
| JetBrains chat | Yes | No |
| Copilot CLI | Yes | Yes |
So copilot-instructions.md is the only file every surface sees, and AGENTS.md is the only file other agents see.
If nobody uses anything but Copilot, copilot-instructions.md alone covers every surface. If nobody uses Copilot, AGENTS.md alone covers the rest. Most teams mix tools, though, and then a pointer-only Copilot file fails: Copilot Chat on GitHub.com cannot follow it to AGENTS.md.
Accept a small, deliberate overlap. The Copilot file repeats only the essentials: the stack, the commands and the working rules. Everything else lives in AGENTS.md. This is what the 2prompt generator writes:
# Copilot instructions
Project: shop-api. Order and checkout API for the storefront.
The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.
## Stack
- Language: TypeScript
- Framework: Fastify
- Database: PostgreSQL
- Tests: Vitest
- Package manager: pnpm
## Commands
- Install dependencies: `pnpm install`
- Run locally: `pnpm dev`
- Run all tests: `pnpm test`
- Lint: `pnpm lint`
- Type-check: `pnpm tsc --noEmit`
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
Instruction files are configuration, and configuration without an owner decays. Give both files the same owner as the build and CI configuration, because they describe the same things: how to install, build and test the project, and what a change must satisfy before it merges.
Teams that skip this step usually find the Copilot file months out of date, because nobody using another agent ever reads it. Keeping the Copilot file short makes the job small enough to actually happen.
When the build changes, the order of updates matters. Change AGENTS.md first, because it is the source, then copy the affected essentials into the Copilot file in the same commit. Reviewers then see both edits together, and a missing update in either file is easy to catch. A simple checklist item in the pull request template, asking whether the agent instruction files need an update, is often enough to keep both files honest over time.
Formats in detail: copilot-instructions.md and AGENTS.md.
Partly. The Copilot cloud agent, code review, the Copilot CLI and VS Code chat read AGENTS.md. Copilot Chat on GitHub.com, Visual Studio and JetBrains chat do not, so keep a copilot-instructions.md too.
Do not rely on an order. Say in copilot-instructions.md that AGENTS.md wins on conflict, keep the overlap small, and change both files in the same pull request.
We did not find an import syntax for copilot-instructions.md in GitHub documentation, so treat it as a standalone file. That is why the essentials are repeated inline.
In .github/instructions as NAME.instructions.md files with an applyTo glob in frontmatter. Copilot Chat on GitHub.com does not read these, so keep must-follow rules in the main file.