Answers
Copilot organization instructions reach every repo, but only on GitHub.com and in code review
Published
GitHub Copilot can share instructions across every repository in an organization with organization custom instructions, set under Settings, Copilot, Custom instructions, but only sessions on the GitHub website and Copilot code review use them. GitHub says they are not supported in local client sessions, so Copilot in VS Code and the CLI still need the rules in each repo.
For GitHub Copilot. Vendor facts are from the pages linked below, read on November 18, 2026.
Cover every surface
- Set organization instructions: organization Settings, Copilot, Custom instructions, then Save changes. They reach GitHub.com sessions and code review.
- For local sessions, keep
.github/copilot-instructions.mdor AGENTS.md in each repo, synced from one source. - Do not repeat the same rule in both places with different wording: personal, repository and organization instructions are all sent, and a conflict reaches the model whole.
- Personal instructions take priority over repository ones, which take priority over organization ones, but all are provided.
The numbers
| Measure | Value | Source |
|---|---|---|
| Surfaces that use organization instructions | GitHub.com sessions (cloud sandboxes or Actions) and code review | GitHub organization instructions docs |
| Local client sessions | Not supported | GitHub organization instructions docs |
| Instruction layers sent together | 3: personal, repository, organization | GitHub repository instructions docs |
What the docs say
- GitHub: Adding organization custom instructions: Currently supported for sessions running on the GitHub website (in cloud sandboxes or on GitHub Actions) and for Copilot code review. They are not supported in local client sessions.
- GitHub: Adding repository custom instructions: Personal instructions take the highest priority, then repository, then organization; all sets of relevant instructions are provided to Copilot.
Where Harbor fits
Harbor connects Claude Code, Codex, Cursor and GitHub Copilot (the CLI and VS Code agent mode; the cloud agent is not supported yet) through hooks and an MCP server. It serves the same team rules to Copilot CLI and VS Code agent mode, the local sessions organization instructions skip, and to teammates on Claude Code, Codex and Cursor. Each rule shows how often it was served and how often an answer cited it. A citation is evidence a rule was used, not proof it was obeyed.
Read next
- How to write copilot-instructions.md
- Sync AGENTS.md across repos
- Copilot instructions length
- Share CLAUDE.md rules across repos with ~/.claude/rules, a symlinked .claude/rules, or a managed CLAUDE.md
- Codex shares instructions across repos only through ~/.codex/AGENTS.md, one person at a time
- Gemini CLI reads AGENTS.md only if context.fileName lists it; Antigravity CLI reads it by default
- Share Windsurf rules across repos with ~/.devin/rules, and with other agents through AGENTS.md
- Every answer, by agent and problem
Questions
Do Copilot organization instructions work in VS Code?
GitHub’s page says organization instructions are not supported in local client sessions. They apply to sessions on the GitHub website and to Copilot code review.
How do I share Copilot instructions across all repositories?
Set organization custom instructions for GitHub.com and code review, and sync a .github/copilot-instructions.md or AGENTS.md into each repo for VS Code and the CLI.
What wins when organization and repository instructions conflict?
GitHub ranks personal first, then repository, then organization, but sends all of them. Both sides of a conflict reach the model, so remove one.