PathruleCopilot suggests.
Pathrule remembers.
Scoped team context for GitHub Copilot, through Pathrule's MCP tools in VS Code agent mode and the Copilot CLI. In VS Code the extension registers it for agent mode.
GitHub CopilotexampleWithout
Done. The page fetches /api/orders in a useEffect.
Uses fetch where the team uses the api client.2 tries
With Pathrule
when Copilot asks over MCP: 3 notes for features/orders
- Use the api client, not fetch
- React Query for data
- Shared buttons from ui/
Done. Orders load through the api client with React Query.
Matches what the team already decided.1 try
How Pathrule reaches GitHub Copilot.
- files it reads: nofiles it reads
- None: Pathrule writes only its MCP entries
- before each prompt: nobefore each prompt
- No prompt hook
- around tool calls: noaround tool calls
- No hooks
- when it asks: yeswhen it asks
- Local, in VS Code and the Copilot CLI
No hooks and no files: Copilot reaches the knowledge through Pathrule's MCP tools in agent mode and the Copilot CLI.
copilot-instructions.md vs Pathrule
- Native instruction files can be scoped by path and shared through version control.
- Changes follow repository permissions and its Git or pull-request history.
- Context depends on the files and guidance the client loads.
- Lives with Copilot; other tools need their own files.
- Onboarding follows the repository’s instruction setup.
- Path-scoped slice for the directory the model is working in.
- Reviewable rules and skills with server-enforced workspace access and a self-audit.
- Token cost scales with the relevant slice, not the whole rule set.
- Same content reaches Claude Code, Codex, Cursor and Windsurf.
- Onboarding = "join the workspace; the right rules show up on the right paths".
Long read: One knowledge layer across AI coding agents.
What Pathrule adds to Copilot
- MCP deliveryWhen Copilot asksCopilot calls Pathrule's MCP tools and gets the slice for the folder it is working in. Pathrule installs no Copilot hook, so a strict rule arrives as guidance, not as a block.
- Path-scoped graphRules where they applyA rule attached to
/services/billingonly comes back when Copilot asks about work under that path.copilot-instructions.mdkeeps the global constants; Pathrule keeps the scoped ones. - MCP and skillsMemories, rules, skillsPathrule registers as an MCP server, so Copilot can read and save memories, rules and skills through its tools. Three reviewable node types, the same ones every other agent reads.
- VS Code agent modeRegistered by the extensionIn VS Code, the Pathrule extension registers the MCP server for Copilot agent mode, with no config file to edit by hand. Your own
.github/instructions stay yours: Pathrule writes nothing there.
Questions.
What does Pathrule add to GitHub Copilot?
A path-scoped knowledge layer that Copilot reaches through Pathrule's MCP tools. When the agent asks, it gets the team memories, rules and skills scoped to the directory being worked in.
Which Copilot surfaces does Pathrule support?
VS Code agent mode and the Copilot CLI: pathrule install copilot writes the MCP entry for both, and in VS Code the Pathrule extension can register the server for agent mode. Pathrule writes no .github/ files, so setup does not connect the coding agent on github.com, which works from the committed repository; the Copilot integration docs cover each surface.
Is Pathrule a replacement for copilot-instructions.md?
No. Copilot already supports path-specific instructions and Copilot Memory can retain repository facts and private preferences in its preview. Pathrule adds one shared workspace source across supported agent vendors, task-specific selection and typed requirements.
Does the same content work across my other tools?
Yes. Claude Code, Codex, Cursor and Windsurf receive the same knowledge: Claude Code and Codex through hooks and MCP, Cursor and Windsurf through MCP. One pathrule setup writes the MCP entry for all five.
Does Pathrule see my source code?
No. Pathrule does not automatically upload your repository source code. In local mode there is no account and knowledge stays on your machine. In cloud mode, Pathrule Cloud stores the memories, rules and skills your team writes, and the start of each prompt is sent to rank what applies. Full breakdown on the Security page.