PathrulePathrule, in the editor
you already have open.
The knowledge tree follows your active file, memories and rules open as ordinary editor tabs, and one command connects your AI clients. Local mode needs no account, so it starts working the moment it installs.
Pathrule
Knowledge
- api2
- deploy1
- docs
- apps5
- admin1
- web4
- src
- Memories2
- Checkout uses the shared API client
- Authentication sessions and token renewal
- Rules1
- Skills1
- packages2
- ui1
- billing1
Checkout uses the shared API client.md
---memory: Checkout uses the shared API clientscope: /apps/web--- ## Use the shared client Load orders through the API client. It owns authentication, retries and error handling. Use React Query for server state. Avoid a second fetch wrapper inside checkout components. ## Verify the change Run the checkout tests and check the loading and error states before calling the work done.
It knows which file you are looking at.
A tree that follows the editorRepo-shaped, showing only the paths that carry knowledge. As you move between files it follows to the closest path covering the current one.Content as markdown tabsA memory or rule opens as an ordinary editor tab. Edit it like any file, with the tooling you already use, and save to persist through Pathrule.Conflicts as a decisionA teammate's change never lands silently on top of yours. You choose to reload, keep a copy of your version, or overwrite, so a conflict surfaces instead of a loss.Right-click any pathBrowse the knowledge that applies to a file or folder, including what it inherits from parent paths. Or scope a new memory, rule or skill to it in two keystrokes.One command for AI clientsCopilot agent mode is registered automatically. Connect AI Clients writes MCP entries for the clients you pick and the hooks for Claude Code, and for Codex when the repository has Codex files, then lists what was written where.Check IntegrationOne check for the whole setup. It confirms each client is connected, the hooks are present, and the MCP server starts.
That is the one thing no other surface can use as well, and most of what the extension does follows from it.
Start local, add the team later.
- Local mode, no accountInitialize a folder and the content is stored on your machine, in a local store built on Pathrule's open-source core.
- Sign in when you want the team layerConnect a Pathrule Cloud workspace so memories, rules and skills are shared with your team, with version-aware writes.
- Bring the folder with youPush Workspace to Cloud picks an organization and copies the local workspace up.
Two modes behind one interface, and the mode is a property of the open folder rather than a guess. Team management and billing live in Pathrule Web at app.pathrule.io.