Pathrule

Products

One product, every way in.

Pathrule Studio is the complete product. The surfaces under it are lighter ways to work with the same workspace: your editor, your terminal, any MCP client, your own infrastructure, or the open core on its own.

Pathrule Studio on macOS, with the workspace tree on the left and a task in the composer

Pathrule Studio is the product.

The macOS app is where the whole thing lives: the agents, the task board, the design canvas, source control and runtime Signals, over one shared understanding of your product. Everything else on this page is a lighter way into the same workspace.

The other ways in.

Same workspace, same knowledge, same MCP contract. Pick by where you work and what you need to control.

Which surface fits.

Each row links to the page that carries its full requirements. Hook-time delivery is the one row worth reading closely: it needs a local runtime, so a hosted MCP client answers on request instead.

SurfacePlatformRuns agentsHook-time deliveryBest for
Pathrule StudiomacOSYes, six engines nativelyYesThe complete product, wired on install
Pathrule CLImacOS, Windows, LinuxThe agents you drive from a shellYesTerminal-first setup, headless boxes, CI
VS Code extensionVS Code and its forksConnects external clients through CLIInjects themWorking inside the editor you already have open
MCPAny MCP clientNo, it is the tool surfaceLocal runtime onlyConnecting a client Pathrule does not install for you
Self-hostedYour infrastructurePer clientPer clientData that cannot leave your boundary
Open source coremacOS, Windows, LinuxThe agents you wire yourselfYesOne person, fully local, no account

Where the org lives.

Account, team, invites and billing are in Pathrule Web at app.pathrule.io, the cloud console. Writing knowledge and running agents happen on your machine, in Studio or the CLI, where the path-scoped context is delivered.

Explain it once.

Pathrule is free for solo developers. Your first memory takes a minute.