One product, every surface.
Pathrule is a path-scoped knowledge layer for AI coding assistants. It is one product. The surfaces below are different ways into it: a native app, your editor, the terminal, any MCP agent, your own infrastructure, or the open source core. Your team's cloud content is shared across all of them. Local runtime state stays scoped to the current user and machine.
macOS app
Native menubar app for your workspace. The most complete surface.
iOS app
The companion on your phone. Follow and answer live runs from anywhere.
CLI
Drive Pathrule from your terminal, on macOS, Windows and Linux.
VS Code extension
A full client in VS Code, Cursor and Windsurf.
MCP server
Connect any MCP-capable agent over one typed tool surface.
Self-hosted
Run the full product inside your own VPC.
Open source core
The engine, free and inspectable, under Apache-2.0.
Patterns
Ready-to-use memory, rule and skill bundles, pre-scoped to the paths they belong to.
How to choose
Every surface speaks the same MCP tool contract, so the AI client sees the same tools and the same path-scoped context whichever one you run. Pick a surface by where you work and what you need to control, not by features. The table below lines them up side by side; the list under it maps common workflows to a surface.
| Surface | Account needed | Local repo access | Bundled MCP server | AI clients | Works offline | Best for |
|---|---|---|---|---|---|---|
| macOS app | For the team layer | Yes | Yes | Claude Code, Cursor, Codex, Windsurf, Copilot | Yes (local cache) | The most complete surface, wired on install. |
| VS Code extension | Optional (local mode) | Yes (open folder) | Connects your clients | Copilot, Claude Code, Cursor, Codex, Windsurf | Local mode, no account | Working inside VS Code, Cursor or Windsurf. |
| CLI | For the team layer | Yes | Yes | Materializes the hook for your clients | Yes | Terminal-first setup, headless boxes, CI. |
| MCP server | Depends on client | No | n/a | Any MCP-capable agent | Local stdio | Connecting any agent over one typed tool surface. |
| Self-hosted | Your SSO | Per client | Per client | Any MCP-capable agent | On your infra | Running the full team product inside your VPC. |
| Open source core | None | Yes | Yes | Any MCP-capable agent | Yes | Reading the code and running the engine locally. |
Pick by workflow
Same product, same tools. Start from the surface that matches how you work.
macOS app
Everything wired on install: the bundled MCP server, the hook installed into your AI clients, and a local cache that keeps context instant and offline.
Learn moreVS Code extension
You live in VS Code, Cursor or Windsurf. The open folder is the workspace and the active file is the path. Start in local mode with no account, and sign in later for the team layer.
Learn moreCLI
Terminal-first setup, headless boxes, or CI. Sign in over SSH with a device code, and emit JSON from the doctor, repair and status commands.
Learn moreMCP server
You just need to connect an agent. It exposes memories, rules and skills only, with no exec and no arbitrary filesystem reads, local over stdio or cloud over the hosted Remote MCP.
Learn moreSelf-hosted
Governance requires the full team product on your own infrastructure: your database, your identity, your backups, with realtime and AI running on your side.
Learn moreOpen source core
Run the engine for free under Apache-2.0 with no account, and read exactly how routing and ranking decide what your agent sees.
Learn moreAccount, team, billing and invites live in Pathrule Web at app.pathrule.io, the cloud management console. Writing knowledge and running your AI assistants happen in Pathrule Studio or the CLI on your machine, where the path-scoped context is delivered.