PathruleYour agent,
with your knowledge.
Claude Code and Codex stay the agents you work with. Pathrule connects through their native plugin channels or settings hooks, so each starts with the project knowledge it needs. Choose Local or Cloud for the workspace behind it.
connect
$ pathrule integrations add claude codex --local --dry-run# preview the files and settings Pathrule would change$ pathrule integrations add claude codex --local# review and approve the plan before it is applied$ pathrule integrations doctor
One source. Two ways to connect.
Native pluginUse the provider’s plugin mechanism to connect Pathrule’s hooks and MCP tools.Settings hooksRegister Pathrule in the agent’s own settings. Other servers and unrelated settings are preserved.Task-scoped knowledgeMemories, rules and skills stay attached to their paths. Each agent receives what applies through the channels it supports.
The channel changes how the integration is installed, not what the workspace knows.
See the change before it lands.
- Preview--dry-run shows the proposed setup without writing.
- ApproveChoose the agents, Local or Cloud mode, and user or project scope.
- Inspectlist and doctor show the recorded integration and any setup problems.
- Maintainrepair reapplies recorded Pathrule entries; remove takes the recorded integration out.
Each client, reached its own way.
- Native integration guideCommands, scope, channels and removal.
- All integrationsWhat files, hooks and MCP each client supports.
- Local or CloudChoose a local workspace or shared Cloud knowledge.
Native plugin channels are for Claude Code and Codex. Cursor, Copilot and Windsurf use their supported CLI or VS Code integrations. Delivery and blocking capabilities differ by client.