Pathrule

CLI

Pathrule, from your terminal.

The same runtime Studio bundles, without the window. One install brings the MCP server, the hook supervisor and the local cache to macOS, Windows and Linux, and every command speaks JSON when a script is reading.

zsh

$ pathrule login

signed in as [email protected]

$ pathrule workspace attach --path ~/repos/acme-shop

workspace acme-shop attached

$ pathrule install claude && pathrule install cursor

claude-code config written + hooks registered

cursor config written

$ pathrule doctor

cache ok · mcp ok · hooks ok · clients 2/2

What the CLI owns.

Everything the local runtime needs, plus the parts that only make sense in a terminal. Pick one to see the command behind it.

ssh prod-builder

$ pathrule login --device

open https://app.pathrule.io/device

code: FJKD-2M9Q

signed in as [email protected]

Two flows, one of them headless.

A browser PKCE flow on a desktop, and a device code flow that works over SSH or on a box with no browser at all.

From install to a wired agent.

Three commands, and the fourth tells you whether it worked. Cloud-only flows like billing and team admin open Pathrule Web in your browser rather than being reimplemented in the terminal.

  1. 01

    Install and sign in

    One npm install, then a browser flow on a desktop or a device code over SSH.

  2. 02

    Attach a workspace

    Bind it to a local directory, which is how a session's working directory resolves to the right knowledge.

  3. 03

    Install your clients

    Configs and hooks are written for Cursor, Windsurf and GitHub Copilot. Standalone Claude Code and Codex CLI are available too, and pathrule doctor confirms every connection.

Where to go deeper.

One install, and your agents are wired.