ShareXP is the fix database that knows what doesn't work. It tracks dead ends and verifies fixes after reuse, so AI coding agents stop repeating the same mistakes.
Claude Code (recommended):
/plugin install sharexp
Other tools:
npm install -g @willytop8/sharexp
npx sharexp quickstartFor Cursor, Codex, OpenCode, Gemini CLI, and other MCP-compatible agents, see docs/AGENT-SETUP.md.
- Cross-user remediation memory — Share verified fixes across your team and the broader community. Resolutions are outcome-verified, not just captured once and forgotten.
- Dead-end tracking — Record what didn't work, with negative trust deltas. When another user hits the same error, they see "2 people tried solution X and it made things worse."
- Outcome verification and Bayesian trust — Every fix is scored by how many times it's been reused successfully. Trust scores update as new reuse data arrives.
- MCP-native — Ships as a Claude Code plugin and a standard MCP server. Works locally by default; publishing requires explicit consent.
- Privacy-first by design — Credential, PII, and path sanitization happen at the egress chokepoint on your machine before data leaves. The hub re-sanitizes on ingress.
The seeds/ directory contains 127 hand-crafted resolutions across flagship debugging patterns, Next.js, Vite, Prisma, and Docker. A bulk-imported corpus of resolutions from popular OSS repositories is hosted on the hub at https://sharexp-hub.fly.dev.
Core tools (always available):
find_similar_resolutions— Search local and hub resolutions for similar errorssearch_resolutions_by_description— Find fixes by describing what you're trying to docapture_resolution_candidate— Record a potential fix locallyfinalize_resolution— Mark a candidate as verified and optionally publish to the hubrecord_resolution_outcome— Report reuse success or failurerecord_dead_end— Track what didn't work and update trust scoresget_value_report— View resolution quality metrics and reuse statistics
Advanced tools (set ER_ADVANCED_TOOLS=true to enable):
Chains, anomaly detection, operational signals, CI outcome reporting, strategy analysis, and root-cause labeling.
Public repos only by default. ShareXP only publishes fixes from public repos. Private repos stay entirely on your machine. No flag to remember — the right behavior is the default.
To publish from a private repo, set SHAREXP_PUBLISH_PRIVATE=true in your shell or in the mcpServers env block. To disable all publishing, set SHAREXP_NO_PUBLISH=true.
Identifier-aware redaction. In addition to credential, PII, and path sanitization, ShareXP now strips CamelCase function names, internal file paths, scoped package names, and repo identifiers from outgoing payloads before transmission. pull_request_url is never sent. Repo identifiers are replaced with a 12-char SHA-256 hash prefix.
Verify what's shared. Use the get_repo_visibility_status MCP tool to check your current repo's publishing status before doing sensitive work.
See SECURITY.md and docs/PRIVACY.md for the full privacy posture.
If you don't trust the hosted hub at sharexp-hub.fly.dev, you can run your own. See docs/SELF-HOSTING.md.
ShareXP is an alpha project with a hosted hub on Fly.io, a growing curated seed corpus, and early tooling for outcome verification. We're actively expanding the corpus and looking for early users.