PathruleYour knowledge,
on this machine.
Memories, rules and skills are easier to keep useful when you can see them. The Local Console opens in your browser, reads the same local workspaces as the CLI, and needs no account.
local
$ npm i -g @pathrule/cli$ pathrule setup --local$ pathrule ui# opens a one-time launch link in your browser# served on 127.0.0.1 while this command runs
See what your agents know.
Browse by workspaceFind the memories, rules and skills that belong to each local project.Keep the source usefulCreate and edit knowledge, archive what no longer applies, and restore an item when you need it again.Read the activityInspect what agents reported doing and the workspace paths they touched.
What happened. What still needs proof.
Runtime evidenceReview grouped errors and events, their code paths, releases and verification state.A fix needs coverageRecording a fix is a claim. Successful observations from a newer release are what verify it.Inspect the runtimeSee the local runtime’s state and use the CLI’s read-only diagnostics when setup needs attention.
Local Signals keeps runtime observations beside the knowledge for the project.
Local has a clear boundary.
- Local or CloudChoose where the workspace knowledge lives and who needs to share it.
- Cloud consoleShared workspaces, people, plans and billing belong to Pathrule Cloud.
- SecurityWhat stays local, what Cloud receives and how to check it.
The console loads no external resources and does not sync local knowledge to Cloud. Your coding agent keeps its own provider connections.