Pathrule

io.pathrule由 pathrule.io 发布官方发布者v1.0.6更新于 Oct 26, 2026

Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud.

发布方自己的服务：Pathrule

已验证Streamable HTTP可网页运行知识与记忆开发者工具

服务详情

标识符: io.pathrule/pathrule
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Oct 19, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 pathrule.io，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.pathrule%2Fpathrule.svg)](https://sourceweft.com/mcp/io.pathrule%2Fpathrule?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

Pathrule 为编码代理保存按路径划分的记忆、规则和技能，并只向代理提供与即将修改的代码相关的条目。

可以做什么: 按路径检索项目知识，让代理获得针对当前文件的记忆、规则和技能
通过 get_context 工具按需获取上下文，深度随请求而定
把决策、坑点和失败命令的教训记录为简短 markdown 笔记，归档在相关代码旁
让强制规则优先于建议，并把超出单次提示预算的内容按标题列出
在 Claude Code、Codex、Cursor、GitHub Copilot、Windsurf 及其他 MCP 客户端之间共享同一份知识
适用场景: 适合在不同会话和不同工具中反复向编码代理重复同样纠正的场景，或 CLAUDE.md、AGENTS.md 已变得很大且每一步都被完整读取的情况。也适合希望按路径而非单一全局文件下发项目约定的团队。
运行要求: 使用 cloud.pathrule.io 远程端点并需 OAuth 登录，或通过 npx 运行本地 npm 包 @pathrule/mcp；CLI 安装方式需要 macOS、Linux 或 Windows 上的 Node.js 22.14.0 或更高版本。本地模式无需账号、网络或模型。Cloud 工作区为可选，按 AI Credits 计费。

安装前请注意

Cloud 模式会把知识存储到 Pathrule 服务器，并用提示内容对其排序；其模型层可能读取提示以找出需要长期保留的决策，并按 AI Credits 计费。本地模式不运行模型、不发送遥测，源代码不会自动上传。安装过程会修改代理配置，但会先展示计划。

安装

在 SourceWeft 中

打开控制台中的 Pathrule，将其添加到工作区。
连接所需的凭据。它们会被私密存储，绝不会在公开页面上展示。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.pathrule%2Fpathrule/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "pathrule": {
      "type": "http",
      "url": "https://cloud.pathrule.io/mcp"
    }
  }
}

README

[Pathrule]

English · Español · Français · Deutsch · 日本語 · Italiano · Türkçe · Português (Brasil)

Your AI forgets. Pathrule remembers.

The open-source knowledge layer for coding agents. Pathrule keeps what your project has learned as memories, rules and skills scoped to paths in your code, and gives Claude Code, Codex, Cursor, GitHub Copilot and Windsurf only what the task in front of them needs, before they act.

[npm] [License: Apache-2.0] [PathruleBench: Python · Go · TypeScript] [CI] [VS Code Marketplace] [Open VSX]

PathruleBench, 2,000 items: 55% lower cost a chain · 2.7× fewer input tokens · 97% of memory probes passed · the numbers

Website · Docs · Quickstart · Benchmarks · Smarter over time · Changelog

[Same request, same agent. On the right, Pathrule's hook hands over the three notes filed for apps/web/dashboard before the agent writes a line.]

_{Same request, same agent. On the right, Pathrule's hook hands over the three notes filed for apps/web/dashboard before the agent writes a line.}

Works with Claude Code · Codex · Cursor · GitHub Copilot · Windsurf · any MCP client

Quickstart

Node.js 22.14.0 or newer, on macOS, Linux or Windows.

bash

npm i -g @pathrule/clipathrule setup --local    # no account: knowledge stays on this machinepathrule doctor           # see what each agent receives

npm i -g @pathrule/clipathrule setup --local    # no account: knowledge stays on this machinepathrule doctor           # see what each agent receives

Restart your agent. From the next session on, it gets the notes for the path it is about to touch, and writes new ones as it works.

Other ways in	Command	Good for
VS Code extension	`code --install-extension Pathrule.pathrule-vscode`	Knowledge beside the code. Marketplace and Open VSX.
Claude Code / Codex plugin	`/plugin marketplace add pathrule/pathrule` · `codex plugin marketplace add pathrule/pathrule`	Installing from inside the agent. Setup shows a plan before it changes anything.
Cursor plugin	Cursor Marketplace → Pathrule	The same hooks, MCP and skills inside Cursor.
Gemini CLI / OpenCode plugin	`gemini extensions install https://github.com/pathrule/gemini-cli-extension` · `opencode plugin @pathrule/opencode --global`	The same setup in Gemini CLI and OpenCode.
Any MCP client	`npx -y @pathrule/mcp`	Agents without a plugin system. Listed in the official MCP Registry.
Local Console	`pathrule ui`	Browse and edit knowledge on 127.0.0.1. No account.
Remote MCP	`claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp`	Trying it with nothing installed. No hooks, no local mode.
From source	`pnpm install && pnpm cli:bundle`	Hacking on Pathrule. See docs/quickstart.md.

Explain it once

Coding agents start every session blank. So the same correction comes back, day after day, agent after agent:

Day	Agent	What you typed
Mon	Claude Code	“use our api client, not fetch”	1st
Tue	Claude Code	“again: api client, not fetch”	2nd
Wed	Codex	“we use the api client.”	3rd
Thu	Cursor	“I told you yesterday. api client.”	4th
Fri	Claude Code	“API CLIENT. NOT FETCH.”	5th

Five sessions, three agents, nothing remembered. With Pathrule you say it once:

[Explain it once]

You fix it once, the way you normally would.
Pathrule files it next to the code it is about: a memory on features/, not a line in a file every session has to read.
Every agent knows from the next session on, whichever one you open.

Only what matters

A workspace collects hundreds of notes. An agent editing features/orders needs four of them.

[Only what matters]

Knowledge is matched by path, scope and relevance, then fit to a per-prompt budget. Enforced rules are never cut for space. Whatever does not fit is listed by title, so the agent can ask for it. When a prompt names a function or a type, the hook also points the agent to the file and line where it is defined (JS/TS, Python, Go).

Three kinds of knowledge

Kind	What it holds	Example on `features/`
Memory	Decisions, gotchas and incidents, in short markdown.	“Use the api client. It handles auth and retries.”
Rule	Constraints the agent must follow, ranked above advice.	“Data loading goes through React Query.”
Skill	Reusable procedures and checklists an agent can run.	“Run the checks before calling it done.”

Three ways in

Channel	When it reaches the agent	Cost
Path-scoped rule files	Claude Code reads Pathrule's own `.claude/rules/pathrule/` at session start, each file scoped to its paths. Your `CLAUDE.md` and `AGENTS.md` are left as they are.	Cached by the client.
Hooks	Before the agent acts: on session start, on each prompt and on file tools. Only new or changed context is sent again.	Budgeted per prompt.
MCP `get_context`	When the agent asks, at the depth the request needs.	Every MCP client has it.

Why not just CLAUDE.md?

[PathruleBench: Python · Go · TypeScript]

A CLAUDE.md file 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. PathruleBench measured the difference with the same agent, the same prompts and the same hidden checks, from 500 to 2,000 items of team knowledge.

[Cost and input tokens a chain: CLAUDE.md climbs as knowledge grows, Pathrule stays flat]

At 2,000 items of team knowledge	CLAUDE.md	Pathrule
Cost a chain of 8 sessions	$3.89–$4.21	$1.76–$1.89
Input tokens a chain	11.8–12.5 M	4.3–4.7 M
Memory probes passed	89%	97%
Chains that passed every memory probe	0 of 9	5 of 9
A habit said once, followed later	78%	97%
What a failing command taught, kept	33%	78%
The work each prompt asked for	100%	100%

From 500 to 2,000 items, a chain with CLAUDE.md costs 89–98% more. With Pathrule it moves between −1% and +10%. Your knowledge base can grow; the bill does not.

_{Claude Code with claude-sonnet-5-5 in Python, Go and TypeScript; nine chains an arm at 2,000 items (three per language); executable tests decide every pass, no model judges. The Pathrule arm is this repository's open-source CLI in local mode: no Cloud, no model.}

Every condition, chain and check, and how to run it yourself → pathrule/benchmark

Smarter the longer you use it.

Day one needs no account, no network and no model. Everything after builds on what you and your agents already did in this repository.

[Smarter the longer you use it.]

When	What Pathrule does	Where it runs
Day 0 Foundation	Hooks and the local MCP server are wired into your agents. What you write is delivered per path, within a budget, through the hooks and Claude Code's path-scoped rules; your own `CLAUDE.md` and `AGENTS.md` are left as they are.	Open source, this machine
Week 1 Memory	A decision you state in a prompt (“from now on…”, “we decided…”) is saved in your own words. A lesson a failing command taught is saved once. Each note is filed next to the code it is about, and only new or changed context is sent again.	Open source, this machine
Month 1 Your habits	A preference you state lives in a local file of your own. Said once in passing, it waits; said again in another session, it reaches every agent. One you call lasting is in force at once. A project rule always wins over a personal one.	Open source, this machine
Month 3 At scale	Thousands of notes, and a session stays the same size: the root rules file stays around 6k characters and the rest arrives per prompt. A sentence that says where code lives is marked `(as of writing)`, so when a teammate moves the file the agent follows the code. When an edit writes a value a newer decision replaced, the hook quotes the decision at that edit.	Open source, this machine
When you choose Team	The same knowledge on every machine and for every member. For a Cloud workspace, a model also reads the prompts Pathrule's phrase rules found nothing in and keeps the sentence you meant to last, still in your words. It is paid from AI Credits.	Pathrule Cloud, opt-in

_{No model runs on your machine. Everything before Team is the open-source CLI, the same path the benchmark above measured.}

Switch agents. Keep the knowledge.

[Switch agents. Keep the knowledge.]

Agent	Before it acts	Instruction file	MCP
Claude Code	Hooks, prompt hook included	Pathrule's own `.claude/rules/pathrule/`	Local or Remote
Codex	Hooks, prompt hook included	—	Local or Remote
Cursor	—	—	Local
GitHub Copilot	—	—	Local
Windsurf	—	—	Local
Any MCP client	—	—	Local or Remote

Not another rules file

	A rules file	Pathrule
Written	By hand, kept current by hand	Grows as you and your agents work
Reaches	One tool per file	Every connected agent
Delivered	All of it, every session	Only what the path and the task need
Changes	When someone edits it	Versioned; new knowledge replaces old

Keep your CLAUDE.md and AGENTS.md: Pathrule does not edit them. It delivers the rest per path and per task, where a single file cannot.

What's in this repository

This is Pathrule's open-source foundation. It runs with no account and no network service: the store, retrieval and ranking, the MCP server, the hooks, the learning loop and the CLI.

Part	Here	Licence
Foundation: protocol, agent IR, the local knowledge store, host, MCP server, CLI, Pathrule Cloud client, agent integrations, Local Console, VS Code extension	Yes	Apache-2.0
Pathrule Cloud: team workspaces, sync, the web console, Remote MCP, the Cloud model tier	No	Proprietary

The 11 packages

protocol · agent-ir · core · integrations · mcp · host · ui · local-console · cloud · cli · vscode

bash

pnpm installpnpm typecheck      # every packagepnpm test           # every package's testspnpm build          # each package's npm build

pnpm installpnpm typecheck      # every packagepnpm test           # every package's testspnpm build          # each package's npm build

Your code stays yours

Source code is never uploaded automatically.
Local mode has no account, runs no model, and the open CLI sends no telemetry.
Your agent keeps its own model provider. Pathrule is not a model, an agent or an IDE.
Pathrule Cloud is opt-in. Signed in, it stores your knowledge and uses the prompt to rank it, and its model tier may read a prompt to find a decision meant to last.