PathruleLocal or Cloud
Choose a local workspace with no account or shared knowledge in Pathrule Cloud. What each mode stores, where you manage it and how agent delivery differs.
On this page
The first choice is where the workspace knowledge should live. Local keeps it on this machine. Cloud makes it available through your Pathrule account. Your coding agent stays the one you already use in either mode.
Choose by who needs the knowledge
| Local | Cloud | |
|---|---|---|
| Account | Not required | Pathrule account |
| Workspace knowledge | Local store on this machine | Managed Cloud workspace |
| Sharing | This local workspace | According to workspace membership and permissions |
| Repository setup | CLI or VS Code | CLI or VS Code |
| Browser surface | Local Console, with pathrule ui | Cloud console at app.pathrule.io |
| Hosted MCP | Not available | OAuth access to an approved workspace |
| Signals | Local storage and verification | Managed ingest, fix recording and verification on Pro, Team and Enterprise |
Start with Local when the knowledge is for this machine. Choose Cloud when another machine or teammate needs the same authored source. Plan availability and limits are on Pricing.
Set up Local
From your repository:
pathrule setup --local
pathrule ui
Setup connects the local workspace and the clients you choose. pathrule ui opens the Local Console, where you browse, search, edit and restore knowledge and inspect activity or Local Signals.
The optional local model has its own platform requirements. Knowledge delivery continues without it. If you configure an external embedding provider, the text you rank goes to that provider.
Set up Cloud
pathrule setup
Choose Cloud in setup, sign in and select or create the workspace for this repository. Each teammate attaches their own local folder. Shared knowledge does not share another person’s folder bindings or client configuration.
The Cloud console manages workspaces, people, plans and settings. A client that cannot run a local process can use Remote MCP, with an approved workspace grant. Remote tools have their own schemas and install no local hooks.
What the agent receives
The local runtime delivers knowledge through the files and hooks each client supports, with MCP for deeper reads and writes. That works with either local or Cloud workspace knowledge. Remote MCP returns Cloud knowledge when called; it does not provide hook-time delivery.
Memories, rules and skills keep their meaning in either mode. Project requirements still outrank personal preference, and source-backed findings remain advice to verify.
Move deliberately
Choosing Cloud does not automatically publish an existing local workspace. Select the destination workspace and review the entries you want to share. Keep secrets, private customer data and personal notes out of shared knowledge. Security explains the local, Cloud and coding-agent provider boundaries.