Contact
Pick the address that matches what you need. Security and privacy are separate inboxes so that each reaches the person who can act on it.
| Need | Address |
|---|---|
| Product support | support@pathmode.io Bugs, questions, anything not working. Include what you tried and what you saw. |
| Security | security@pathmode.io Vulnerability reports and suspected account compromise. See reporting a security issue. |
| Privacy & data | privacy@pathmode.io Data export, deletion requests, and questions about what we store. |
| Sales & partnerships | hello@pathmode.io |
MCP server and Claude Code plugin
The @pathmode/mcp-server package and the Claude Code plugin share one server. The plugin pins a server version, so updating the plugin is how you move the server. Most reports fall into one of the cases below.
- Tools fail with a 401. The configured API key is invalid or was revoked. Mint a fresh key under Workspace settings → API keys and re-run
npx @pathmode/mcp-server@latest setup pm_live_…. Or removePATHMODE_API_KEYand restart to fall back to keyless local mode, where specs live inintent.mdand no account is needed. - Cloud tools are missing from the tool list. Keyless mode registers only the repo tools, so the agent sees only what will work. Configure a key to get intent management, evidence, and graph tools.
setupstarts the server instead of the installer. You are on an old package version. Use@latest, or setPATHMODE_API_KEYdirectly in theenvblock of your MCP config.- The readiness check keeps failing. That is the verdict, not an error.
check_intent_readinessnames the exact blockers inintent.md; repair them or accept the named risk explicitly. The six checks are documented in the intent.md profile. - Installing the plugin. In Claude Code run
/plugin marketplace add pathmodeio/claude-plugin, then/plugin install pathmode@pathmode.
Tool and prompt references are on the developer docs. For anything reproducible, open an issue on GitHub with the package version and the client you are using; otherwise email support.
Workspace, CLI, and review links
The hosted workspace at pathmode.io is where private evidence, attributed review, and cross-repo staleness live. Sign-in supports Google, GitHub, and an email link. If a sign-in link never arrives, check spam, then email support with the address you used so we can check delivery on our side.
@pathmode/cli is one bundle that runs as a command-line tool and as a GitHub Action. Commands, flags, and the REST API it calls are documented on the developer docs; the error catalogue there explains each status code you can get back.
Review links are read-only views of a spec revision shared by its owner. If one stops opening, the owner has reset it; ask them to share again. Pre-merge review checks on pull requests are advisory and never block a merge.
Pathmode for Jira
The Jira app is available on request rather than from a public Marketplace listing. Setup, the three panel states and what each means, and verification steps are on the Jira documentation. To request an install, email support@pathmode.io with your Atlassian site URL. To have data from an uninstalled app deleted, email privacy@pathmode.io.
Reporting a security issue
Email security@pathmode.io with details of the vulnerability and how to reproduce it. Please do not post it publicly. We acknowledge within one business day and coordinate disclosure with you.
How we store and protect data is described on Trust & Security.
Resources
- Developer docs: MCP tools, REST API, authentication, errors.
- IntentSpec: the open specification for the
intent.mdfiles Pathmode writes. - Playbook: guides on writing specs, evidence, and intent workflows.
- Changelog: recent releases across the workspace, server, and plugin.
- Trust & Security, Privacy Policy, and Terms of Service.