Skip to content
Pathrule

integrations

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

Not the same for all five.

Agentfiles it readsbefore each promptaround tool callsMCP
Claude Codefiles it reads: yesbefore each prompt: yesaround tool calls: yesMCP: yes
Codexfiles it reads: yesbefore each prompt: yesaround tool calls: yesMCP: yes
Cursorfiles it reads: nobefore each prompt: noaround tool calls: noMCP: yes
GitHub Copilotfiles it reads: nobefore each prompt: noaround tool calls: noMCP: yes
Windsurffiles it reads: nobefore each prompt: noaround tool calls: noMCP: 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.

Claude Code, Codexsession start: deliveredyou send a prompt: deliveredfirst tool call: deliveredagent asks: delivered
Cursor, Copilot, Windsurfsession start: nothingyou send a prompt: nothingfirst tool call: nothingagent asks: delivered

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.