Skip to content
How it learnsFrom coding sessions, reviews, Slack and docs.Only what fitsEach session gets the few rules its task needs.Pull request reviewEvery PR checked against your team’s rules.Keep it trueA gate, conflicts, disputes and stale rules, handled.HandoffsCarry the work to another session or a teammate.SecurityWhat it sends, what it changes and how to leave.
Engineering teamsOne agent or several: what one person learns, every session uses.PR review onlyInstall the GitHub App. Nothing on anyone’s machine.Teams that mix agentsClaude Code, Cursor, Codex and Copilot, the same rules.On your ownYour corrections follow you across repos, machines and agents.Book a call30 minutes with Roei, if you want a hand. Never required.
DocsPricingSign in
Connect your agents →
For teamsOn your ownPR review onlyHow it learnsOnly what fitsPull request reviewKeep it trueSecurityDocsPricingSign inConnect your agents →
Home/Answers

Answers

Ignores its rule file

  • HTML comments in CLAUDE.md
  • "Read AGENTS.md" does not import
  • Antigravity ignores AGENTS.md
  • Windsurf ignores rules

Rule file too long

  • AGENTS.md too long for Codex
  • Antigravity rule size limit
  • Copilot instructions length
  • Cursor rules too long

Rules drift from the code

  • CLAUDE.md and AGENTS.md drift
  • Directory trees in rule files

Share rules across repos and agents

  • Share CLAUDE.md across repos
  • Share AGENTS.md in Codex
  • Copilot org instructions
  • Gemini CLI and AGENTS.md
  • Share Windsurf rules

Memory between sessions

  • Gemini CLI memory

Answers

Copilot organization instructions reach every repo, but only on GitHub.com and in code review

Published November 18, 2026

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.md or 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

MeasureValueSource
Surfaces that use organization instructionsGitHub.com sessions (cloud sandboxes or Actions) and code reviewGitHub organization instructions docs
Local client sessionsNot supportedGitHub organization instructions docs
Instruction layers sent together3: personal, repository, organizationGitHub 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.

Your team’s rules, in every agent, checked on every PR.

Harbor is shared memory for your team’s Claude Code, Cursor, Codex and Copilot. Free for you and one teammate. No card. No end date.

Start free →

Product

  • How it learns
  • Only what fits
  • Pull request review
  • Keep it true
  • Handoffs
  • The result
  • Security
  • For coding agents
  • Pricing

Developers

  • Docs
  • Quickstart
  • Install
  • CLI
  • MCP server
  • Served and cited
  • Rule-file checker
  • Blog

Guides

  • Why Claude ignores CLAUDE.md
  • AGENTS.md vs CLAUDE.md
  • Share Claude Code memory with a team
  • Why Codex ignores AGENTS.md
  • Why Cursor ignores rules
  • Copilot instructions vs AGENTS.md
  • Shared memory across agents
  • Copilot Memory and Dreaming

Compare

  • All comparisons
  • vs Mem0
  • vs Zep
  • vs Unblocked
  • vs ByteRover
  • vs Cognee
  • vs Hindsight
  • vs OpenViking
  • vs Supermemory
  • vs Glen
  • vs MemPalace
  • vs Sentra
  • vs Trail-code

Company

  • Questions
  • Contact
  • X
  • LinkedIn
  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Refund Policy
© 2026 HarborConnect your agents