Your AI forgets. Pathrule remembers.

The intelligence layer for your coding agents. Pathrule keeps what your project has learned and gives each agent only what the task needs.

Start free How it works

works with

Claude Code
Codex
Cursor
Copilot
Windsurf

New chatexamplesame request, same agent

Load the user's orders on the dashboard.

Without

Done!

useEffect(() => { fetch('/api/orders')... })

YouNo, use our api client and React Query. I told you yesterday.

Explained again, third time.2 tries

With Pathrule

3 notes for apps/web/dashboard

Use the api client, not fetch
Data loading goes through React Query
Run the checks

Done with the api client and React Query. Checks pass.

useQuery(['orders'], () => api.get('/orders'))

Right the first time.1 try

Same rule. Every day.

Monclaude code
"use our api client, not fetch"
Tueclaude code
"again: api client, not fetch"
Wedcodex
"we use the api client."
Thucursor
"I told you yesterday. api client."
Friclaude code
"API CLIENT. NOT FETCH."

5 sessions3 assistants0 remembered

Explain once.

You fix it once

as you normally would

features/orders/useOrders.ts

export async function loadOrders() {- const res = await fetch('/api/orders')+ const res = await api.get('/orders')}

Saved use the api client, not fetch memory

Pathrule files it
next to the code it's about
- src/
- features/api client, not fetch
- orders/
- auth/sessions expire in 24h
- ui/shared buttons
Every AI knows
from the next session on
claude · a week later
1. $ claude
2. > add an orders page
3. ● pathrule · 3 notesbefore it starts
4. api client, not fetch
5. React Query for data
6. run the checks
7. ● Write features/orders/OrdersPage.tsx
8. + useQuery(['orders'], () => api.get('/orders'))follows the notes
9. ● checks passed ✓

Only what matters.

Example task "Add an orders page"

96 notes
path: features/orders
4 relevant
4 sent, within budget

notes sent: 4
tokens: ~600
left out: 92

api client, not fetch
React Query for data
run the checks
shared buttons from ui/

Knowledge is matched by path, scope and relevance, then fit to a per-prompt budget. Enforced rules are never cut for space. Anything that does not fit is listed by title, so the agent can ask for it.

New beats old.

marchWe use REST for the API.replaced

juneWe moved to tRPC.now sent instead

every assistant gets

Claude CodetRPC
CodextRPC
CursortRPC
CopilottRPC
WindsurftRPC

Update a note once and every agent gets the new version. Edits are versioned, learned claims are held back when the code they came from changes, and conflicts wait for a person to decide.

Not another rules file.

CLAUDE.md412 lines · loaded every time

Written and kept current by hand
One file per tool
All of it, every session
Changes when someone edits it

pathrule3 notes · for this file

Use the api client, not fetchmemory
Data loading via React Queryrule
Run the checks before doneskill
src/features/orders/OrderList.tsx

Grows as you work
Every connected assistant
Only what the path needs
Versioned as it changes

Keep your CLAUDE.md and AGENTS.md for the repository-wide basics. Pathrule delivers the rest per path and per task, where a single file cannot.

Not just memory. Intelligence.

Memory

stores

api client, not fetch
we use REST
React Query for data
old deploy steps
shared buttons
tabs vs spaces
...

Everything, always, until you clean it up.

Pathrule Intelligence

decides

Learnsfrom what you fix and decideapi client, not fetch
Scopeseach note to the code it's aboutfeatures/
Ranksrules first, then team, then yourule, team, you
Picksonly what this task needsthis task

Memory is what was saved. Intelligence decides what it means for this task: where it applies, what outranks what, and what to leave out.

Three kinds of intelligence.

Your project. You. Your team.

Project. Lives with the repository, scoped to paths. Local or in Cloud.

Use the api client. It handles auth and retries.features/
No new REST routes. We use tRPC.api/
Check the database before changing tables.migrations/
Login broke from token refresh once. Use useSession().auth/
Shared buttons live in ui/. Don't restyle them.components/
Dates are stored in UTC, formatted on the client.lib/date

You. Your preferences, across every repository. A project rule always wins.

Small changes, tests next to them.your preference
pnpm, never npm.you said so
Short answers, code first.your preference
Test before the fix.you confirmed
Explain the why in commit messages.your preference
Ask before adding a dependency.you confirmed

Team. Organization guidance in Pathrule Cloud. Team plans, off until your organization turns it on.

Validate input at every service edge.team rule
Security rules beat personal ones.precedence
New features ship behind a flag.team rule
Every release gets a changelog line.team rule
No secrets in code. Use the vault.security
Two reviewers for anything in billing/.billing/

Switch assistants. Keep the memory.

Today,Claude Code

pathrule memoryunchanged

api client, not fetch
React Query for data
run the checks

how it connects Claude Code hooks before it acts, .claude/rules and MCP

Assistants with hooks get knowledge before they act. MCP-only clients ask for it when they need it. See every integration

Your code stays put. Your knowledge reaches the team.

your machine

your codeNot uploaded automatically
pathruleConnects this folder to your workspace
your coding agentKeeps its own provider

Pathrule Cloud

connected

one workspace for the whole team
the same knowledge on every machine
versioned, restorable after a delete
Team Intelligence on team plans

your code: Not uploaded automatically
roles: Owners, admins and members
history: Versioned and restorable
hosted: Remote MCP, nothing to install

Pathrule Cloud stores your knowledge and uses your prompt to rank what applies. Your source code is not uploaded automatically, and your coding agent keeps its own provider. Security

Explain it once.
That's it.

Start free For teams