Pathrule

About

About Pathrule: the context layer for AI coding teams

Pathrule Studio is a workspace for building products with AI agents, where Chat, Tasks, Design and Signals work from the same evolving understanding of the product. Underneath it, a path-scoped Context Layer routes the team's memories, rules and skills to the work that needs them, before the first tool call, so an agent starts from what the team already knows rather than the whole rulebook.

What Pathrule is

Pathrule Studio is a workspace for building products with AI agents. Chat, Tasks, Design and Signals work from the same evolving understanding of the product, so a decision made in one place does not have to be explained again in the next.

What makes that possible is a path-scoped Context Layer underneath. It holds three kinds of product knowledge, attached to the paths they belong to: memories (what the team has learned), rules (what to do or avoid) and skills (how to perform multi-step work).

When an agent is about to act on a file, Pathrule delivers only the slice that governs that path, before the first tool call. Studio runs Claude Code, Codex, Grok, Kimi, Antigravity and OpenCode itself. Pathrule CLI is the lighter integration path for Cursor, Windsurf and GitHub Copilot. The model never sees the parts of your team's rulebook that do not apply.

Same knowledge, every agent. A rule written for /apps/mobile applies whether the developer is using Claude Code today, switches to Grok tomorrow, or runs Codex next. Pathrule is the layer that survives agent churn.

Why we built it

Every team that adopts an AI coding assistant eventually hits the same wall. The CLAUDE.md, AGENTS.md or .cursorrules file that worked while the team's conventions fit on a page starts breaking down as unrelated instructions accumulate. The model ignores parts of it. Token budgets balloon. New teammates do not know what is in it, and old teammates do not know what is stale.

The pattern shows up in very different shapes: a one-developer side project, a backend monorepo adding its tenth service, an agency juggling client work. The team changes; the problem does not. Team knowledge was being modelled as one giant file when the work itself is path-scoped.

Pathrule started as the answer to one question: what if rules lived next to the paths they apply to, and the model only saw the ones it needed?

How it works

  • Author. Write memories, rules and skills in the web app, desktop app or CLI. Each is attached to a path in your workspace.
  • Route. Pathrule indexes the graph by path. The relevant subtree is precomputed for fast lookup at hook time.
  • Inject. When your AI tool fires a PreToolUse or UserPromptSubmit hook, Pathrule emits the path-scoped slice as JSON.
  • Survive agent churn. The same content works across Claude Code, Codex, Grok, Kimi, Antigravity and OpenCode in Studio. Cursor, Windsurf and GitHub Copilot receive it through Pathrule CLI. New tools do not reset team memory.

For the technical version, see the core concepts and the how hooks work docs.

What Pathrule is not

  • Not a replacement for your coding agent. Studio runs the agents you already use rather than shipping a model of its own, and what it adds is the product knowledge they work from.
  • Not a code indexer. Pathrule does not read, scan or upload your source files. It stores the typed content your team writes.
  • Not another AI subscription. Studio does have a Chat surface, but the agent answering in it is the one you already pay for. Pathrule does not resell AI access or charge per model token.
  • Not a model provider. Pathrule does not run inference on your codebase or train models on your content.

Founder

Sertan Helvacı, Founder

Sertan spent years writing code, then moved into product design and worked formally as a product designer. Pathrule comes out of both sides of that path. It is not a vibe-coding side project.

Design has always had a design-system principle: shared tokens, shared components, shared rules that travel with the work. Pre-AI software teams had a quieter version of the same thing in shared conventions, shared review and shared memory. The first wave of AI coding assistants broke that quiet system. The rules a team used to share with itself collapsed into a single instruction file that the model half-followed and the team half-trusted.

Pathrule is what comes out of taking those older principles seriously again, for the AI coding era. He writes about the problem from a team's point of view in the Pathrule writing.

[email protected]

Trust and privacy

Pathrule never reads, scans or uploads your source code. The cloud stores the typed memories, rules and skills your team writes, plus the structural metadata needed to route them. Everything else stays on your disk.

Every claim on that boundary is independently verifiable in a couple of minutes. The hook script is a single unobfuscated Node.js file. The MCP tool surface is enumerable with a single tools/list call, so you can confirm there is no file-reading tool. The network surface is short and auditable. The full breakdown lives on the Security page.

FAQ

What is Pathrule? Pathrule Studio is a workspace for building products with AI agents. It runs Claude Code, Codex, Grok, Kimi, Antigravity and OpenCode while Chat, Tasks, Design and Signals work from the same understanding of the product. The path-scoped Context Layer delivers the memories, rules and skills that govern the path being worked on before the first tool call.

Who is Pathrule for? Engineering teams that already use AI coding assistants and feel the pain of AGENTS.md or CLAUDE.md files growing past the point where the model can follow them. Small teams, startups and agencies who want shared rules and memory across tools without uploading source code.

How is Pathrule different from CLAUDE.md or AGENTS.md? AGENTS.md and CLAUDE.md are instruction files read by individual tools. Pathrule is a routing layer above them: you store knowledge once, in a path-indexed graph, and only the relevant subtree is delivered into the model's context for the current task. Long read: AGENTS.md vs Pathrule.

Does Pathrule see my source code? No. Pathrule never reads, scans or uploads your source files. The cloud stores only the typed content your team writes (memories, rules and skills) and structural metadata. Source code stays on your disk. See Security for verifiable details.

Which AI coding tools does Pathrule support? Pathrule Studio runs Claude Code, Codex, Grok, Kimi, Antigravity and OpenCode natively. Pathrule CLI connects Cursor, Windsurf and GitHub Copilot as lighter external integrations over MCP.

How do I get started? Read the quickstart, then install Pathrule Studio or CLI. Solo developers can use Pathrule for free.

Contact