Editor extension
A lighter editor surface for Pathrule: the knowledge tree follows your active file, memories and rules open as markdown tabs, and the bundled CLI connects external clients. Local mode needs no account, so it starts working the moment it installs.
That is the one thing no other surface can use as well, and most of what the extension does follows from it.
A tree that follows the editor
Repo-shaped, showing only the paths that carry knowledge. As you move between files it follows to the deepest path covering the current one, and the status bar names it.
Content as markdown tabs
A 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 decision
A teammate's change never lands on top of yours. You are offered reload, keep a copy, or overwrite, so a conflict surfaces instead of a loss.
Right-click any path
Browse the knowledge that applies to a file or folder. Or scope a new memory, rule or skill to it in two keystrokes, with bulk move and undo.
One command for AI clients
The bundled Pathrule CLI registers Cursor, Windsurf and GitHub Copilot for the bound folder. Standalone Claude Code and Codex can also receive managed entries, and the notification lists what was written.
A doctor command
One check for the whole setup. It confirms each client is connected, the hooks are present, and the context server is reachable.
Two modes behind one interface, and the mode is a property of the open folder rather than a guess.
01
Local mode, no account
Initialize a folder and the content lives on your machine, with the open core doing the routing.
02
Sign in when you want the team layer
Shared knowledge, live activity as teammates edit, and the managed backend.
03
Bring the folder with you
One action picks an organization and copies the workspace up, keeping the local copy as a fallback.
Cloud-only actions are hidden rather than broken while a folder is local, and signing in here signs the CLI in too.
