Skip to content
Pathrule

pathrule.iomain

Pathrule

Overview

DocsGet started
PathruleBench55% cheaper. 97% remembered.

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 freeHow 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.

  1. Monclaude code

    "use our api client, not fetch"

  2. Tueclaude code

    "again: api client, not fetch"

  3. Wedcodex

    "we use the api client."

  4. Thucursor

    "I told you yesterday. api client."

  5. Friclaude code

    "API CLIENT. NOT FETCH."

5 sessions3 assistants0 remembered

Explain once.

  1. 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

  2. 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

  3. 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"
  1. 96 notes
  2. path: features/orders
  3. 4 relevant
  4. 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. Measured.

A CLAUDE.md is read whole on every step, so every note your team adds makes every session cost more. Pathrule sends each prompt only what the path and the task need.

PathruleBenchsame agent, same prompts, same hidden checks
cost a chain
−55%
at 2,000 items
fewer input tokens
2.7×
at 2,000 items
memory probes passed
97%
CLAUDE.md 88%, no memory 16%

Cost a chain of 8 sessions

as the team's knowledge grows
Cost a chain of 8 sessions, Python
CLAUDE.mdPathrule
500 items$2.06$1.70 (−17.5%)
1,000 items$2.62$1.71 (−34.8%)
2,000 items$3.89$1.76 (−54.7%)
  • CLAUDE.md read whole on every step
  • Pathrule learns, scopes and ranks, then sends only what the task needs

Where the gap opens

memory probes passed, every published chain
  • Lessons from a failing command
    Pathrule 78%CLAUDE.md 31%
  • Habits said once, in passing
    Pathrule 96%CLAUDE.md 79%
  • Following the code past a stale note
    Pathrule 98%CLAUDE.md 84%
  • Changed decisions applied
    Pathrule 90%CLAUDE.md 83%

Nothing traded away: the work each prompt asked for passed in every chain, with or without Pathrule.

Claude Code with claude-sonnet-5-5, in Python, Go and TypeScript, from 500 to 2,000 items of team knowledge. Executable checks decide every pass; no model judges. Pathrule ran as the open-source CLI in local mode.

Full results on GitHub

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 freeFor teams