Path-scoped context routing
Stores team knowledge as memories, rules, and skills, then routes only the relevant pieces into an AI session based on the path you are working in.
Pathrule
Pathrule routes team rules, decisions, conventions, memories, and skills into AI coding assistants like Claude Code, Cursor, Codex, Windsurf, and GitHub Copilot.
Overview
Pathrule is a context layer for AI coding assistants. It routes a team’s rules, decisions, conventions, memories, and skills into tools like Claude Code, Cursor, Codex, Windsurf, and GitHub Copilot, scoped to the files and folders being worked on.
The product is built to keep project knowledge close to the code without storing source code itself. Teams can capture context once, attach it to paths in a workspace tree, and let Pathrule deliver the most relevant pieces at hook time before an agent starts working.
Features
Multi-assistant delivery
Supports Claude Code, Cursor, Codex, Windsurf, and GitHub Copilot, with the docs describing hook-time delivery before the first tool call.
Context retrieval and ranking
Ranks candidate context by location, recent changes, semantic meaning, and how files change together, so the assistant gets a smaller, more relevant slice.
Workspace tree inheritance
Lets you pin knowledge to folders and inherit context from parent paths, so shared conventions can apply across a repo without one global file.
Curated patterns catalog
Includes patterns, which are curated packages of pre-scoped memories, rules, and skills for common stacks and workflows.
Team collaboration controls
Supports real-time collaboration with version-aware writes, presence, and conflict handling so multiple teammates or agents can work on the same knowledge safely.
Use Cases
Share coding conventions across a repository
Use Pathrule when a team wants the same architecture notes, naming conventions, or review rules delivered to every AI session that touches a particular folder or service.
Scope knowledge by code area
Use the workspace tree and inherited context when different parts of a monorepo need different guidance, such as frontend, backend, billing, or infra paths.
Start a workspace with a curated bundle
Use patterns to seed a new project with pre-scoped memories, rules, and skills for a known stack instead of writing everything from scratch.
Coordinate team-authored context
Use real-time collaboration and version-aware writes when multiple developers or agents are editing the same knowledge and need conflict detection instead of silent overwrites.
Run a local context engine
Use the open-source core locally when an individual developer wants path-scoped context delivery without adopting the full cloud collaboration layer.
Pros and Cons
Pros
- Routes context into several major AI coding assistants from the same knowledge layer.
- Uses path scope and inheritance so context can be targeted instead of kept in one global file.
- Offers patterns for quickly seeding a workspace with pre-scoped knowledge packages.
- Supports collaboration features such as presence, version-aware writes, and conflict handling.
- Has a free Solo plan for individual developers and an open-source core.
Cons
- The public sources do not fully spell out setup steps, output formats, or all workflow details for every surface.
- Enterprise details are higher level on the pricing page; exact commercial terms are not public.
FAQ
What does Pathrule route into AI coding assistants?
Pathrule is designed to route path-scoped memories, rules, and skills into Claude Code, Cursor, Codex, Windsurf, and GitHub Copilot at hook time, before the first tool call. Its docs and product pages describe Quickstart, core concepts, and MCP tools for getting started.
Does Pathrule have a free plan and paid plans?
The pricing page says Solo is free for individual developers. Team and Business are paid plans, and Enterprise is sold through sales with higher limits, SSO, audit logs, dedicated support, and self-hosted deployment in your own VPC.
How do you get started with Pathrule?
Pathrule is built around memories, rules, and skills that are scoped to paths in a workspace tree. The docs point to a quickstart that installs a runtime, creates a workspace, and writes the first memory so Claude Code can pick it up through the hook.
What are Pathrule patterns?
Pathrule’s patterns are curated bundles of memories, rules, and skills. The patterns catalog says they are pre-scoped to the right paths, free, Apache-2.0, and importable by token into a workspace.
Does Pathrule store source code?
The pricing FAQ says memories and rules are the team-authored context objects Pathrule routes into AI sessions, and source code is not stored.
Quick Facts
- Category
- Developer Tool
- Primary use
- Context routing for AI coding assistants
- Supported assistants
- Claude Code, Cursor, Codex, Windsurf, GitHub Copilot
- Pricing model
- Free Solo plan, paid Team and Business plans, Enterprise sales
- Open source
- Core is open source under Apache-2.0
- Source domain
- pathrule.io
Pathrule Alternatives
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
Goldfish
Goldfish is an AI memory app for macOS that helps you reply, write, summarize, and continue with context already on your Mac. It stores memory locally and writes in your tone.
garden-md
garden-md is an open-source Node.js CLI that turns meeting transcripts into a local company wiki, linking entities and preserving the original text.
Ghost
Ghost is a terminal-based AI assistant for chatting, code generation, and CLI tasks. Includes free models, supports Linux, macOS, Windows, and is open source.
Dcyde
Dcyde is a shared decision log for product teams to capture what was decided, why, and the source, with searchable records from Slack, Figma, or Dcyde.
Lasso
Lasso is an ecommerce product data platform for enriching catalog records, processing supplier files, generating product content, and tracking competitors. It includes a web app, REST API, SDK, and MCP server.