Introduction

Pathrule is the team knowledge layer for AI coding assistants. It lets a team write down what their assistant should know about a repo once, and then routes that knowledge into Claude Code, Cursor, Codex, Windsurf, GitHub Copilot, or any MCP compatible client at the moment the assistant needs it.

The unit of value is not a prompt file or a CLAUDE.md. It is a small, typed piece of content that lives at a path in your workspace: a memory, a rule, or a skill.

What Pathrule stores

Pathrule stores three kinds of content your team writes intentionally.

• Memory: a short markdown note that captures a decision, a schema gotcha, a postmortem, or a convention. Attached to a workspace path so it only surfaces when work happens nearby.
• Rule: a constraint the assistant must follow when working in a scope. Rules carry a priority (high, medium, low) that ranks how strongly they surface and an enforcement mode (advisory or strict); a strict rule can block a matching change before it lands, while an advisory rule rides along as context.
• Skill: a named procedure the assistant can invoke instead of re deriving the steps. Useful for recurring jobs like replaying a webhook, regenerating a fixture, or running a release checklist.

What Pathrule does not store: your source code. The cloud never indexes the repo, never reads files on disk, and never sends code to an LLM. Your codebase stays on your machine.

Surfaces, one cloud

Pathrule ships as two local runtimes against a single cloud workspace, plus a browser management console and a hosted Remote MCP endpoint for clients that cannot run a local runtime.

• Pathrule Studio (macOS). The native desktop app where you code with Claude Code, Codex and OpenCode, author memories, rules and skills, and get path-scoped context delivered natively. Bundles the MCP server, the hook supervisor and the local cache.
• Pathrule CLI. The terminal first surface for macOS, Linux, and Windows. SSH friendly and scriptable, it runs the local MCP server, the hook supervisor and the local cache for agents you drive from a shell.
• Pathrule Web at app.pathrule.io. The browser management console for your organization, members and roles, plans and billing, workspaces and usage. Cloud only, with no filesystem access; you write knowledge and run agents in Studio, not here.
• Remote MCP. A hosted endpoint at mcp.pathrule.io/mcp for cloud-only AI clients that cannot run a local runtime. They connect directly over streamable-http, with no install. It has no hooks, so it delivers context only.

They share the same workspace tree and the same MCP surface (and, on the local runtimes, the same hooks). The content you write in any of them is the same content the assistant reads in any of them.

How a session feels

1. Your team writes a memory at a workspace path, for example /apps/api/payments.
2. You open Claude Code in ~/repos/main/apps/api/payments.
3. The hook supervisor reads the cached slice for that path and hands it to the editor before the first tool call.
4. The assistant sees the memory, the relevant rules, and any skills attached to that scope, and behaves like it already knew them.

There is no extra prompt to write, no extra MCP round trip mid task, and no global file that grows forever.

What to read next

• Quickstart walks through installing a runtime, creating a workspace, writing your first memory, and watching the hook fire.
• Core concepts explains the difference between memories, rules, and skills, plus how path scope and priority work.
• MCP overview covers the MCP tools the assistant uses to read and write content.