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.