PathruleTeam knowledge,
not one big file.
Pathrule is the intelligence layer for coding agents. It keeps what a project, a developer and a team have learned, and gives each agent only what the task needs, without replacing the agent anyone already uses.
- 01CaptureAgents save memories, rules and skills as they work. People write and edit them too.
- 02ScopeEvery item belongs to a path, so a folder's rule applies in that folder.
- 03SelectRules first, then team knowledge, then preferences, within a budget.
- 04DeliverThrough hooks where the agent allows, its own files, and MCP.
- 05Keep currentVersioned edits. Findings stay advisory until a person acts.
Why it exists.
Every team that adopts an AI coding assistant hits the same wall: the CLAUDE.md that worked while the conventions fit on a page stops working as they grow. Team knowledge was being modelled as one giant file, when the work itself is path-scoped. Pathrule started as one question: what if rules lived next to the paths they apply to, and the model only saw the ones it needed?
The long version: Introducing Pathrule Intelligence
What Pathrule is not.
- Not your coding agentIt works with the agent you already use, which keeps its own model provider.
- Not a code indexerIt does not automatically upload your repository source code.
- Not another AI subscriptionIt does not resell AI access or charge per model token.
- Not a coding modelIt does not write your software or train models on your content.
- Not just a memory toolA memory is one input. Deciding what a task needs is the work.
Who builds it.
Sertan Helvacı Founder
Years of writing code, then years as a product designer. Pathrule comes out of both sides of that path.
Design has always had a design-system principle: shared tokens, shared components, shared rules that travel with the work. The first wave of AI coding assistants broke the quieter version of that system teams had for code. Pathrule takes those principles seriously again.
sertan@pathrule.ioLocal first. Cloud when you choose.
- local mode
- No account. Nothing goes to Pathrule Cloud.
- signed in
- Knowledge stored in Cloud, the prompt's start ranks it
- snapshot
- Only when you or your agent run it
- verify
- Hooks in your agent's settings, tools via tools/list
What is sent, when, and how to check each claim on your own machine: Security
Questions.
What is Pathrule?
Pathrule is the intelligence layer for your coding agents. It keeps what a project, a developer and a team have learned as memories, rules and skills, scopes that knowledge to paths in the code, and delivers what each task needs to the coding agent you already use. It is not a desktop app, an IDE, an agent runtime or a coding model.
Who is Pathrule for?
Engineering teams that already use AI coding agents and feel the pain of AGENTS.md or CLAUDE.md files growing past the point where the model can follow them. Small teams, startups and agencies who want shared rules and memory across tools. Pathrule does not automatically upload repository source code.
How is Pathrule different from CLAUDE.md or AGENTS.md?
AGENTS.md and CLAUDE.md are instruction files read by individual tools. Pathrule keeps knowledge as memories, rules and skills scoped to paths, and for each task delivers what applies at that path, ranked and within a per-prompt budget, through the agent's own instruction files, hooks and MCP. What does not fit is listed by title so the agent can ask for it. What Pathrule learns about how you work is not in the repository at all. Long read: AGENTS.md vs Pathrule.
Does Pathrule replace my coding agent's model?
No. Pathrule is not a coding model and not an agent runtime: your coding agent keeps its own model provider. In Cloud mode, knowledge is stored in Pathrule Cloud and the start of your prompt (about the first 1,000 characters) is sent to rank which knowledge to deliver. In local mode there is no account and knowledge is stored on your machine. See Security.
What is User Intelligence?
What Pathrule learns about how one developer works: your working preferences. It is scoped to you rather than to a repository, so it comes with you to the next project, and it is stored locally; without an account it stays on your machine. A learned preference is a candidate until it becomes active, and it can be retired or rejected. See User Intelligence.
Does Pathrule see my source code?
Pathrule does not automatically upload your repository source code. In Cloud mode it stores the memories, rules and skills you and your agents write, and uses the start of each prompt to rank knowledge. If you or your agent run pathrule snapshot, it uploads a project overview: the file tree, manifests, short documentation samples and recent git metadata. In local mode, knowledge is stored on your machine. See Security.
Which AI coding tools does Pathrule support?
Claude Code, Codex, Cursor, GitHub Copilot and Windsurf, each reached its own way. The CLI or the VS Code extension writes the tool's instruction files and MCP entry. Claude Code and Codex also get a prompt-submit hook that delivers context before the agent acts, Cursor and Copilot get session and tool hooks, and Windsurf uses rules and MCP without hooks. Any other client that supports MCP over Streamable HTTP with OAuth can use Remote MCP. See integrations.
How do I get started?
Install the CLI with npm i -g @pathrule/cli and run pathrule setup in your repository, or install the VS Code extension. pathrule setup --local works without an account. Read the quickstart. The Solo plan is free.