A trust signal,
not a statement.

Pathrule does not automatically upload your repository source code, local mode needs no account, and most of what this page says can be checked on your own machine in a few minutes.

Verify it yourself Report an issue

What goes whereCLI, VS Code, Cloud

Signed in

memories, rules, skills: Stored in Pathrule Cloud
your prompt: The prompt segment used to rank what applies
snapshot: File tree, manifests, doc samples, git metadata, when you run it
source code: Repository source is not automatically uploaded

The Cloud server checks your session, membership and permissions.

Local mode

memories, rules, skills: A local database under ~/.pathrule
how you work: Stored locally (User Intelligence)
your prompt: Stays with your agent's provider
source code: Knowledge and findings are stored locally

Your own embedding key sends ranked text to that provider. Managed product telemetry is off until you opt in.

Three boundaries, kept separate.

1Local mode keeps knowledge on your machinepathrule setup --local, or the extension's local mode: no account, nothing synced.
2Cloud mode sends what it needs, and says soKnowledge in Cloud, the prompt's start to rank it, a snapshot only when you run one.
3Your coding agent keeps its own boundaryWhat you send Claude or Codex is governed by that provider, exactly as without Pathrule.

We do not say nothing ever leaves your device, because that would be false. What is true is that Pathrule does not automatically upload your repository source code, and that local mode needs no account.

What protects your data.

Server-enforced accessEvery read and write checks your current session and workspace access.
No shared admin keyEach client carries your own session, never a service key.
Sessions you can cut offPassword reset and session revocation end Remote MCP grants.
Step-up reauthSensitive workspace lifecycle actions require fresh authentication.
HTTPS to the cloudBetween every Pathrule client and Pathrule Cloud.
Reversible by designDeletes are soft, restorable until permanently deleted.
An activity trailWhat agents report doing, reviewable by your team.

Questions.

Does Pathrule upload my repository source code?

Pathrule does not automatically upload your repository source code. Local project features can inspect files to validate findings or assemble project metadata. A snapshot you or your agent request includes the file tree, manifests, selected documentation excerpts and git metadata. Knowledge entries contain whatever you intentionally write into them. In local mode your knowledge is not synced to Pathrule Cloud.

What does Pathrule send when I use it with Pathrule Cloud?

Your knowledge (memories, rules and skills) is stored in Pathrule Cloud, and the prompt segment supplied for context retrieval is used to rank which knowledge to deliver. Your coding agent keeps its own model provider: whatever you send Claude or Codex is governed by that provider, exactly as it is without Pathrule. We do not claim that nothing ever leaves your machine.

Does the CLI collect telemetry?

Only after opt-in in a signed-in managed CLI. The standalone local CLI sends none. Events contain no code, paths, prompts, knowledge, email, account or workspace ids. Use pathrule telemetry disable to turn them off. NO_TELEMETRY=1, DO_NOT_TRACK=1 and CI keep telemetry off.

Can I verify Pathrule's claims myself?

Yes. pathrule doctor and pathrule integrations doctor inspect your setup without changing it. Client configuration and managed instruction files are readable, and tools/list shows the tools and schemas of the MCP server you connected. Local stdio and Remote MCP have different catalogs.

Does Pathrule train models on my content?

No. Pathrule does not train models on your content.

The full reference.

Last updated 9 October 2026. For developers evaluating the Pathrule CLI, VS Code extension, MCP and Pathrule Cloud. Report an issue

1. Boundaries by design

Pathrule stores memories, rules, skills, findings, working preferences and related workspace records. A local project feature may inspect files to validate a finding or assemble project metadata; that does not upload the repository source automatically.
Content you or your agent intentionally put into a knowledge entry becomes that entry's content. Avoid storing secrets or customer data there.
Pathrule does not train models on your content.
Knowledge MCP tools have no general shell execution or arbitrary file-read tool. Local project-learning tools can check the source files attached to a finding; they do not expose a general filesystem browser.
Standalone and Local Signals are separate, opt-in runtime observations. Instrumentation is proposed and approved before code is changed. Cloud Signals is part of the plans listed on Pricing.

2. Verify it yourself

Inspect the setup and the tools your agent can use:

pathrule doctor
pathrule integrations list
pathrule integrations doctor
pathrule telemetry

The client configuration and managed instruction files remain readable on disk. Claude Code and Codex can use native plugins or settings hooks. Cursor and Copilot use the hook channels they expose, and Windsurf uses its rules file and MCP. pathrule eject previews project cleanup; pathrule eject --apply carries out the reviewed plan.

Any MCP client can call tools/list to inspect the connected server's tools and schemas. Local stdio and Remote MCP have different catalogs; the reference describes both.

Destination	Purpose
`cloud.pathrule.io`	Cloud workspace services, sign-in and Remote MCP
`app.pathrule.io`	Cloud management console
`models.pathrule.io`	Local model and runtime downloads when you install or update
`eu.i.posthog.com`	Anonymous product telemetry, only after opt-in in a managed CLI or console
npm and the extension registries	Package installation and updates you request

Your agent's own model-provider traffic is separate. You can inspect Pathrule traffic with your firewall or a proxy.

3. What the local runtime touches on disk

The Pathrule home is ~/.pathrule unless you set PATHRULE_HOME. It holds local stores, session credentials when signed in, installed capabilities, hook indexes and diagnostics. Credentials and local stores are restricted to your user.

In a repository, Pathrule writes its managed instruction regions, client integration files and materialized skills. It preserves text outside its managed regions. The local model is installed only when you request setup and downloaded files are verified before activation.

The Local Console binds to loopback, uses a one-time launch link and loads no external resources. Keep the serving terminal open while you use it; Ctrl+C stops it.

4. How the cloud is gated

Pathrule Cloud runs on Cloudflare with authenticated server-side access checks. Workspace reads and writes check the current session, membership, role and workspace state. Every Cloud operation is authorized by the server; hiding a control in the client is not an access check.

Remote MCP tokens are bound to one approved workspace and scopes.
Removing access, archiving or deleting a workspace revokes its grants. Restoring it does not revive old grants.
Password reset and explicit session revocation also end Remote MCP grants.
Refresh tokens rotate. Replaying a rotated token revokes that token family.
Sensitive workspace lifecycle actions require fresh authentication.
Requests, payload sizes, plan entitlements and usage are checked by the server.
Cloud traffic uses HTTPS. Deletes retain the history needed for the documented recovery window.

5. Pathrule Web in the browser

The Cloud console manages workspaces, members, settings and billing. It calls the Cloud API with your bearer session. It does not send an administrative key to the browser and does not run coding agents.

The authenticated console is separate from the public website. Marketing analytics load only after you accept analytics in the cookie banner. Product telemetry in the managed console has its own opt-in setting.

6. The MCP tool surface

Local MCP provides path-scoped knowledge authoring and retrieval, plus project learning, refresh workflows, activity and other local helpers. Remote MCP provides context and list/read operations for memories, rules and skills, plus mutation and history operations with a write grant.

Remote MCP cannot read your filesystem, install hooks or write instruction files. It has no local personal-intelligence delivery. Its schemas are Cloud-native, so clients must inspect tools/list rather than assume local arguments also work remotely.

7. AI and telemetry

The optional local model understands knowledge on your machine. Cloud knowledge indexing and semantic retrieval use Cloudflare Workers AI, and Anthropic's Claude names knowledge topics from topic keywords, folder paths and at most six item titles, never item bodies. Model-assisted Cloud features process the knowledge or evidence needed for that feature; availability follows Pricing. Your coding agent's own model calls stay with its provider.

The standalone local CLI sends no product telemetry. A signed-in managed CLI sends anonymous usage events only after pathrule telemetry enable. They contain command or feature names, result, duration, version, OS family and a random install id, never code, paths, prompts, knowledge, email, account or workspace ids.

pathrule telemetry disable
# These environment settings also keep telemetry off:
NO_TELEMETRY=1 pathrule status
DO_NOT_TRACK=1 pathrule status

Telemetry is always off in CI. Managed product telemetry uses PostHog's EU ingestion service, separately from Cloud knowledge storage and website analytics. See Privacy Policy and Cookie Policy.

8. Distribution and updates

Install or update the CLI with npm i -g @pathrule/cli@latest. The local foundation is Apache-2.0; Cloud and the Intelligence Engine are proprietary capabilities. See Open source.

The CLI can report a newer version but does not update itself. NO_UPDATE_CHECK=1 or a manual update policy disables the automatic check. The VS Code extension requires a trusted workspace before writing integration files and starting its local runtime.

Enterprise self-hosted deployments, with SSO and audit logs, are arranged through Sales; see the self-hosted reference. They are separate from the local CLI and Local Console.

9. Reporting a security issue

Email security@pathrule.io with the affected component, reproduction steps, the impact you observed, and the platform and version. pathrule --version reports the CLI version.

We aim to acknowledge reports within three business days and keep you updated as we investigate. Please test only with accounts and data you own.

10. Contact

Security: security@pathrule.io
General: hello@pathrule.io
Privacy and data requests: privacy@pathrule.io

A trust signal,not a statement.