Skip to content
Pathrule

compare

Pathrule vs Cursor rules

Cursor rules scope by glob, team rules can be pushed centrally, Projects share context across Cursor agents, and hooks can block actions. Pathrule adds one workspace knowledge source selected for tasks across supported agent vendors.

What Cursor rules already do well

Cursor rules are not a flat file. Cursor also has user memories and Projects with shared context across the agents working inside a Project. Projects have rollout and plan limits, so check availability for your account.

Project rules are version-controlled .mdc files in .cursor/rules and can be organised into folders. A rule can target files with a glob like src/**/*.tsx, and four application modes decide when it fires: always, applied intelligently from its description, applied to matching files, or invoked manually in chat. There are user rules for your own environment, team rules pushed from the dashboard on Team and Enterprise plans, and nested AGENTS.md files in subdirectories.

If you work only in Cursor and your conventions fit that model, this is a good system and you do not need another one.

Side by side

Cursor rulesPathrule
ScopingGlobs, folders, nested AGENTS.mdThe repository path the agent is working in
When it arrivesAlways, by glob match, or when the agent decides from a descriptionIn Cursor, when the agent asks Pathrule's MCP server for the path it works on
Which tools read itCursorClaude Code and Codex through hooks and files; Cursor, GitHub Copilot and Windsurf through MCP
EnforcementRules are guidance; separate Cursor hooks can blockIn Claude Code and Codex, a strict Pathrule rule can block through the hook
Team distributionCommitted to the repo, or team rules on paid plansShared workspace, no commit needed
Written by handYesBy you, or saved by your agent over MCP; learned findings stay advisory
Stale rulesYours to noticeFlagged, with a proposed edit you approve

Sources, versions and review date appear below. Cursor has blocking hooks; the distinction here is whether enforcement is connected to the same workspace rule.

The three differences

  • A glob describes files. A path describes work.. A glob matches on the shape of a filename, so **/*.ts fires in every package that has TypeScript. Pathrule keys on where the work is happening, so a rule pinned at /services/billing never surfaces while an agent edits /apps/mobile, even though both are TypeScript.

  • Guidance versus a gate. Cursor rules are context, and Cursor's separate hooks can genuinely block an action. A Pathrule rule carries scope, priority and enforcement in one workspace object, and a strict one is held by the local Pathrule hook in Claude Code and Codex; in Cursor, which Pathrule reaches over MCP, it arrives as guidance.

  • One tool versus every tool. Rules in .cursor/rules are Cursor-specific, while AGENTS.md can travel to other tools that load it. Pathrule keeps workspace knowledge in one source and delivers it to Claude Code, Codex, Cursor, GitHub Copilot and Windsurf, with the same task selection model.

You do not have to choose

Keep your Cursor rules. They are good at repository-wide constants and at editor-specific behaviour, and nothing about installing Pathrule removes them. What Pathrule adds is the long tail that a per-tool rule file models badly: the decisions attached to one directory, the conventions a second engine also needs, and the constraints that should stop a change rather than suggest against it.

The Pathrule for Cursor page covers how the two sit together, and why Cursor rules get silently ignored covers the failure modes worth knowing about either way: frontmatter errors, the legacy file, and too many always-apply rules.

Sources and verification

Official documentation verified 1 October 2026. Cursor product version was not available in the reviewed docs and was not locally tested. Pathrule claims reviewed against the Pathrule v1 CLI on 19 October 2026.

  • Cursor: rules

    Official project, user and team rule behavior, including file scoping.

  • Cursor: Projects

    Official shared project context and availability limits.

  • Cursor: hooks

    Official blocking pre-tool and permission hooks.

Frequently asked questions

Do I have to delete my Cursor rules to use Pathrule?

No. They keep working. Cursor rules are good at repo-wide constants and editor behaviour; Pathrule carries the path-scoped long tail and the constraints that need enforcing, and delivers both to every supported agent rather than to Cursor alone.

Cursor rules already support globs. Is that not path scoping?

It is close, and it is the best version of that idea in an editor. The difference is what the key describes: a glob matches filenames, so a TypeScript glob fires in every package that has TypeScript. Pathrule keys on the directory the work is happening in, so knowledge pinned to one service stays out of another.

Why would a rule I wrote get ignored?

Usually a syntax or a scope problem, and it fails quietly: frontmatter errors, mixing the legacy .cursorrules file with the newer .cursor/rules directory, or so many always-apply rules that each new one dilutes the rest. Cursor's own guidance is to keep a rule under 500 lines and split large ones.

Does Pathrule work inside Cursor?

Yes, over MCP. Pathrule CLI writes its entry into Cursor's MCP config, and the VS Code extension installs in Cursor from Open VSX. It installs no Cursor hook and writes no .cursor/rules file. The same team knowledge reaches Claude Code, Codex, GitHub Copilot and Windsurf.

Get started with Pathrule.