Five agents.
One knowledge.
Pathrule connects to Claude Code, Codex, Cursor, GitHub Copilot and Windsurf. It reaches Claude Code and Codex through hooks and the other three through MCP, so delivery is not the same for all five.
On Claude Code
- files it reads: yesfiles it reads
- .claude/rules/pathrule and .claude/settings.json
- before each prompt: yesbefore each prompt
- Prompt hook
- around tool calls: yesaround tool calls
- Tool hooks
- when it asks: yeswhen it asks
- Local, or Remote MCP
in short Context arrives before Claude Code acts on each prompt, and the knowledge for each file follows it into its tool calls. Setup guide
- files it reads: yesfiles it reads
- AGENTS.md and .codex config, when the repository has Codex files
- before each prompt: yesbefore each prompt
- Prompt hook
- around tool calls: yesaround tool calls
- Tool hooks
- when it asks: yeswhen it asks
- Local, or Remote MCP
in short The same delivery as Claude Code when the repository has Codex files: hooks before each prompt and around tool calls, with AGENTS.md kept current. Setup guide
- files it reads: nofiles it reads
- None: Pathrule writes only its MCP entry
- 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 short No hooks and no files: Cursor reaches the knowledge through Pathrule's MCP tools when the agent asks for it. Setup guide
- 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
in short No hooks and no files: Copilot reaches the knowledge through Pathrule's MCP tools in agent mode and the Copilot CLI. Setup guide
- files it reads: nofiles it reads
- None: Pathrule writes only its MCP entry
- 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 short No hooks and no files: Windsurf reaches the knowledge through Pathrule's MCP tools when the agent asks for it. Setup guide
Not the same for all five.
| Agent | files it reads | before each prompt | around tool calls | MCP |
|---|---|---|---|---|
| files it reads: yes | before each prompt: yes | around tool calls: yes | MCP: yes | |
| files it reads: yes | before each prompt: yes | around tool calls: yes | MCP: yes | |
| files it reads: no | before each prompt: no | around tool calls: no | MCP: yes | |
| files it reads: no | before each prompt: no | around tool calls: no | MCP: yes | |
| files it reads: no | before each prompt: no | around tool calls: no | MCP: yes |
pathrule setup writes the MCP entry for all five, and hooks for Claude Code and Codex. Each is reached the way it allows, and this page never rounds that up.
Before it acts, or after.
A prompt hook puts context in front of the agent before it acts on what you asked. Without hooks, the knowledge arrives when the agent asks for it over MCP.
Three ways in.
Same knowledge.
Remote MCP is documented for Claude Code, Codex and Claude.ai. The other clients use the local server that comes with the CLI or the VS Code extension.