Pathrule connects to Claude Code and Codex through their native plugin channels or settings-based hooks. Your existing agent continues to do the coding work. The integration delivers Pathrule knowledge and exposes its MCP tools.

## Preview and connect

```bash
pathrule integrations
pathrule integrations add claude codex --local --dry-run
pathrule integrations add claude codex --local
```

The interactive command shows the proposed changes before you approve them. `--dry-run` previews without writing. For unattended setup, use `--yes` only after reviewing the plan.

Choose `--cloud` for a signed-in Cloud workspace. Use `--scope project --project <folder>` for a project-specific setup; the default user scope applies across your projects on this machine.

## Choose the channel

```bash
pathrule integrations add claude --channel plugin --local
pathrule integrations add codex --channel settings --local
```

Both channels use the same Pathrule runtime. Native plugins use the provider's plugin mechanism; settings mode registers Pathrule in the agent's settings. Client versions and available channels are reported during setup.

## Inspect, repair and remove

```bash
pathrule integrations list
pathrule integrations doctor
pathrule integrations repair
pathrule integrations remove claude
```

`list` and `doctor` are read-only. Repair reapplies recorded Pathrule integrations, and removal targets the integration Pathrule recorded. Other servers and unrelated settings are preserved.

For Cursor, Windsurf and GitHub Copilot, use [the CLI](/docs/surfaces/cli) or [VS Code extension](/docs/surfaces/vscode). Their supported delivery channels differ from Claude Code and Codex's native plugins.