@cachly-dev/mcp-server 0.10.27 → 0.10.41

package/.env.test.example

@@ -0,0 +1,23 @@
+# E2E test environment variables — copy to .env.test and fill in values.
+# Run: cp .env.test.example .env.test && npx vitest run src/__tests__/e2e/
+
+# API base URL (default: production API)
+E2E_API_URL=https://api.cachly.dev
+
+# Valid Keycloak JWT or long-lived API key (cky_live_...)
+# Get from: cachly.dev/instances → Settings → API Token
+E2E_JWT=
+
+# UUID of an active (running) Brain instance for this token
+E2E_INSTANCE_ID=
+
+# Redis password for the test instance (from connection details)
+E2E_API_KEY=
+
+# Redis host and port for the test instance
+E2E_REDIS_HOST=
+E2E_REDIS_PORT=6380
+E2E_REDIS_TLS=true
+
+# Set to "true" to skip slow tests (provisioning, device flow)
+E2E_SKIP_SLOW=false

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug report
+about: Something isn't working as expected
+title: '[bug] '
+labels: bug
+assignees: ''
+---
+
+## What happened?
+
+<!-- Describe the bug clearly. -->
+
+## Steps to reproduce
+
+1.
+2.
+3.
+
+## Expected behavior
+
+<!-- What should have happened? -->
+
+## Brain doctor output
+
+Run `brain_doctor` in your AI assistant and paste the output here.
+
+<details>
+<summary>brain_doctor output</summary>
+
+```
+(paste here)
+```
+</details>
+
+## Environment
+
+- Package version: <!-- `npm list @cachly-dev/mcp-server` -->
+- Editor / AI assistant: <!-- Claude Code / Cursor / Windsurf / etc. -->
+- OS: <!-- macOS / Linux / Windows -->
+- Node version: <!-- `node --version` -->
+
+## Logs
+
+<details>
+<summary>Relevant logs or error output</summary>
+
+```
+(paste here)
+```
+</details>

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Documentation
+    url: https://cachly.dev/docs/mcp
+    about: Read the full MCP server docs
+  - name: Discord / Community
+    url: https://cachly.dev/discord
+    about: Ask questions and share what you've built

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest a new tool, behavior, or improvement
+title: '[feat] '
+labels: enhancement
+assignees: ''
+---
+
+## What problem does this solve?
+
+<!-- Describe the pain point clearly. What can't you do today that you wish you could? -->
+
+## Proposed solution
+
+<!-- How would you like it to work? Be specific — tool name, input/output, behavior. -->
+
+## Alternatives you've considered
+
+<!-- What workarounds are you using now? What else did you consider? -->
+
+## Context
+
+- Tool(s) involved: <!-- e.g. smart_recall, causal_trace, brain_predict -->
+- Editor / AI assistant: <!-- Claude Code / Cursor / Windsurf / etc. -->
+- Use case: <!-- team / solo / CI / other -->

package/.github/workflows/publish.yml

@@ -0,0 +1,72 @@
+name: Publish to npm
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write  # needed to create GitHub Releases
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          registry-url: 'https://registry.npmjs.org'
+
+      - name: Install dependencies
+        run: npm install --ignore-scripts
+
+      - name: Test
+        run: npm test
+
+      - name: Build
+        run: npm run build
+
+      - name: Check if version is already published
+        id: version_check
+        run: |
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          echo "version=$PKG_VERSION" >> $GITHUB_OUTPUT
+          if npm view "@cachly-dev/mcp-server@$PKG_VERSION" version &>/dev/null; then
+            echo "skip=true" >> $GITHUB_OUTPUT
+            echo "Version $PKG_VERSION already published — skipping."
+          else
+            echo "skip=false" >> $GITHUB_OUTPUT
+            echo "Version $PKG_VERSION is new — will publish."
+          fi
+
+      - name: Extract CHANGELOG notes
+        if: steps.version_check.outputs.skip == 'false'
+        id: changelog
+        run: |
+          VERSION="${{ steps.version_check.outputs.version }}"
+          # Extract section for this version from CHANGELOG.md
+          NOTES=$(awk "/^## \[?${VERSION}\]?/{found=1; next} found && /^## /{exit} found{print}" CHANGELOG.md | sed '/^[[:space:]]*$/d' | head -60)
+          if [ -z "$NOTES" ]; then
+            NOTES="See [CHANGELOG.md](https://github.com/cachly-dev/cachly-mcp/blob/main/CHANGELOG.md) for details."
+          fi
+          # Write to file to avoid env var quoting issues
+          echo "$NOTES" > /tmp/release-notes.md
+          echo "See the [CHANGELOG](https://github.com/cachly-dev/cachly-mcp/blob/main/CHANGELOG.md) for full details." >> /tmp/release-notes.md
+
+      - name: Publish
+        if: steps.version_check.outputs.skip == 'false'
+        run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Create GitHub Release
+        if: steps.version_check.outputs.skip == 'false'
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          VERSION="${{ steps.version_check.outputs.version }}"
+          gh release create "v${VERSION}" \
+            --title "v${VERSION}" \
+            --notes-file /tmp/release-notes.md \
+            --latest

package/CHANGELOG.md

@@ -7,6 +7,258 @@
 
 ---
 
+## [0.10.38] – 2026-05-25
+
+### `cachly status` — Brain health at a glance
+
+- New CLI command `npx @cachly-dev/mcp-server@latest status`: shows lessons, recalls, quality score, Brain level, team contributors (with count), and your personal invite link — all in one terminal card.
+
+---
+
+## [0.10.37] – 2026-05-25
+
+### Viral wow moments — invite link + first-recall tweet button
+
+- **`cachly invite` fixed** — previously called a non-existent `/api/v1/team/invite` endpoint (always 404). Now calls `GET /api/v1/referral/me` and shows your personal referral link with pre-written Slack DM + tweet text. One command = shareable invite.
+- **First-recall email** — the "Your AI just remembered" email now includes a one-click `𝕏 Share this moment` tweet button and a `🤝 Share with your team` section with your personal referral link (shows only if referral code exists). The highest-value wow moment now has a viral exit.
+
+---
+
+## [0.10.36] – 2026-05-25
+
+### ESLint flat-config (ESLint 10 / v9 API)
+
+- Added `eslint` v9 and `typescript-eslint` v8 as devDependencies.
+- Created `eslint.config.js` using ESLint flat-config API — replaces the legacy `--ext .ts` syntax that broke with ESLint 10.
+- Updated lint script: `eslint src --ext .ts` → `eslint src`.
+- Rules: `no-explicit-any` warn, `no-unused-vars` warns but ignores `_`-prefixed params.
+
+---
+
+## [0.10.35] – 2026-05-25
+
+### Docs catch-up
+
+- Backfilled CHANGELOG entries for 0.10.25–0.10.34 (they were missing).
+- README now documents the `index` and `learn-git` CLI commands plus the PR-merge auto-learn GitHub Action tip.
+
+---
+
+## [0.10.34] – 2026-05-25
+
+### `learn-git` CLI — auto-learn from commits (PR-merge ready)
+
+- New command `npx @cachly-dev/mcp-server learn-git [./repo] [--max-commits N]` runs `brain_from_git` over recent commits and fires the `brain_from_git` telemetry event. Building block for PR-merge auto-learning in CI.
+
+---
+
+## [0.10.33] – 2026-05-25
+
+### Close the setup funnel
+
+- The setup wizard now fires `setup_completed` at the end of a successful run (with `instance_id` + JWT attribution), so the onboarding funnel `setup_started → setup_completed` is finally traceable.
+
+---
+
+## [0.10.32] – 2026-05-25
+
+### Viral moments: shareable digest card + team first-briefing
+
+- `cachly digest` now prints a tweet-ready card with a pre-filled X/Twitter URL (lessons, recalls, tokens saved, top lesson, brain level).
+- **Team-virality**: when `session_start` runs for a user who has lessons from teammates but has never seen them, a one-time "Your team's AI brain has been briefing you" section surfaces exactly which teammate solved what.
+
+---
+
+## [0.10.31] – 2026-05-25
+
+### Unblock npm publish — tests green
+
+- `vitest.config.ts` excludes `**/__tests__/e2e/**` from the unit-test suite (E2E tests require live credentials and were failing CI, blocking every publish since 0.10.27).
+- CLI with no args now writes the setup banner to **stdout** and exits 0 (was stderr + exit 1, invisible to callers).
+- `process.exit(0)` guarded with an `_isMain` check so importing modules never trigger early exit.
+
+---
+
+## [0.10.30] – 2026-05-24
+
+### CLAUDE.md delivers a visible briefing
+
+- CLAUDE.md template now calls `session_start` (with `workspace_path`) as the first action of every conversation and `session_end` as the last, so the brain briefing is visible to the user instead of running silently.
+
+---
+
+## [0.10.29] – 2026-05-24
+
+### Fix: recall counting + git bootstrap actually fires
+
+- `smart_recall` (the primary recall tool in CLAUDE.md) now also fires `recall_best_solution` when it returns lessons, so `BrainRecallCount` reflects real usage.
+- Auto-session-start now passes `process.cwd()` as `workspace_path` so the git auto-bootstrap introduced in 0.10.28 actually triggers.
+
+---
+
+## [0.10.28] – 2026-05-24
+
+### Auto-bootstrap the brain from git on first session
+
+- On a first session with a `workspace_path`, `brain_from_git` runs automatically and its summary is appended inline to the `session_start` briefing — the brain learns from your repo history with zero setup.
+
+---
+
+## [0.10.27] – 2026-05-24
+
+### Fix: session_start counts as a recall
+
+- `session_start` now fires `recall_best_solution` when the brain has lessons (not the first-session welcome), so the dashboard activation nudge clears and the first-recall email fires for active users.
+
+---
+
+## [0.10.26] – 2026-05-14
+
+### Fix: brain_from_git + brain_predict telemetry
+
+- `brain_from_git` and `brain_predict` telemetry events were dead code paths and never fired; both now correctly send per-tool telemetry.
+
+---
+
+## [0.10.25] – 2026-05-14
+
+### Per-tool telemetry events for all brain tools
+
+- Every brain tool (`session_start`, `session_end`, `learn_from_attempts`, `smart_recall`, `recall_best_solution`) now emits a dedicated telemetry event for accurate funnel + report breakdowns.
+
+---
+
+## [0.10.24] – 2026-05-14
+
+### Funnel visibility + server.json version sync
+
+- `first_call_success` now includes `instance_id` for full per-tenant attribution in the `mcp_events` table.
+- `server.json` version bumped to 0.10.24 — Smithery and MCP directory indexes now show the current version.
+
+---
+
+## [0.10.23] – 2026-05-14
+
+### Full activation funnel + UTM tracking
+
+- **`sendFunnelEvent` carries JWT**: all funnel events (`setup_started`, `device_flow_completed`, `first_call_success`) now include the JWT so the backend can resolve them to a tenant. Activation funnel is now fully attributable per user.
+- **`cachly share` UTM link**: the generated tweet now includes `https://cachly.dev?ref=share&utm_source=x&utm_medium=social&utm_campaign=cli-share` so shares can be traced back to new signups.
+
+---
+
+## [0.10.22] – 2026-05-14
+
+### Activation telemetry, health Redis ping, join backup
+
+- **`first_call_success` telemetry**: fires once per process on the first successful brain/context tool call. Combined with `setup_started → device_flow_completed → first_call_success`, the full activation funnel is now visible.
+- **`cachly health` Redis PING**: section 3 now opens an actual Redis connection and sends `PING` — verifies end-to-end connectivity, not just instance metadata.
+- **`cachly join` corrupt JSON**: backs up corrupted config files to `.bak` before overwriting, matching the `mergeMcpConfig` behavior.
+
+---
+
+## [0.10.21] – 2026-05-14
+
+### Stability hardening — corrupt configs, silent auth failures, upgrade validation
+
+- **`mergeMcpConfig` corrupt JSON**: instead of silently overwriting, backs up the corrupted file to `.bak` and prints a warning so the user knows their previous config was preserved.
+- **`getConnection` auth failure**: if the `/connection` endpoint returns 401/403, throws an actionable "run `cachly setup` to refresh credentials" error instead of silently attempting a password-less Redis connect that fails with cryptic `NOAUTH`.
+- **`upgrade` version validation**: validates that the npm registry response contains a valid semver string before comparing — prevents false "update available" from a malformed registry response.
+
+---
+
+## [0.10.20] – 2026-05-14
+
+### Edge case hardening — silent failures eliminated
+
+- **`getConnection` status messages**: `failed`, `suspended`, and `pending_payment` now each get a specific actionable message instead of the generic "not reachable" fallback. Users know exactly what happened and where to go to fix it.
+- **`setup` write errors**: config file write failures now print a clear warning with the OS error and a recovery hint instead of silently succeeding.
+- **`join` write errors**: permission and unexpected filesystem errors are surfaced per-file instead of silently swallowed. Expected "editor not installed" cases are still quiet.
+- **Auto-provision telemetry**: if free-tier auto-provision returns a non-2xx response, a `auto_provision_failed` telemetry event fires so the team can detect new-user activation failures in real time.
+
+---
+
+## [0.10.19] – 2026-05-14
+
+### Fix: accurate provisioning time estimate
+
+- `getConnection` no longer says "30 seconds" — the message now correctly says "1–3 minutes" for first-time provisioning. This prevents users from thinking their instance failed just because the first tool call waited 25 s and still saw `provisioning`.
+- Dashboard instance detail page provisioning banner updated to match ("1–3 minutes" instead of "under 60 seconds").
+
+---
+
+## [0.10.17] – 2026-05-14
+
+### `cachly upgrade` — check for newer versions
+
+- **`cachly upgrade`** — fetches the latest version from the npm registry and compares with the running version. If outdated, shows current vs. latest and the one-liner to update (`npx @cachly-dev/mcp-server@latest setup`). No auth required.
+- Added `upgrade` to no-auth bypass list and splash screen.
+
+### Dashboard — Brain Badge widget
+
+- Instance detail page now shows a live badge preview + copy-ready Markdown and HTML snippets directly in the dashboard. No CLI needed.
+- Badge renders as `![cachly Brain](https://api.cachly.dev/api/v1/badge/<id>)` — one click to copy.
+
+---
+
+## [0.10.16] – 2026-05-14
+
+### `cachly join` — accept a Brain invite in one command
+
+- **`cachly join <token>`** — the missing half of the invite loop. Accepts a shared Brain invite link:
+  1. Fetches invite info (public, no auth) — shows Brain name, tier, expiry
+  2. Prompts for confirmation
+  3. If no JWT: starts Device Flow sign-in (browser, 10 s)
+  4. Writes `CACHLY_BRAIN_INSTANCE_ID` into every detected editor MCP config (`.mcp.json`, `.cursor/mcp.json`, `.windsurf/mcp.json`, `.vscode/mcp.json`, `~/.claude/mcp.json`)
+  5. Suggests `cachly badge` as next step
+- Added `join` to no-auth bypass list
+- Splash screen updated to list `join` command
+
+### MCP Directory metadata
+
+- **`smithery.yaml`** — added `name` + `description` block for Smithery listing quality
+- **`glama.json`** — added keywords: `cline`, `zed`, `brain-from-git`, `failure-prediction`, `memory-crystals`, `readme-badge`, `incremental-learning`
+- **`server.json`** — version bumped to `0.10.15`
+
+---
+
+## [0.10.15] – 2026-05-14
+
+### Brain Badge
+
+- **`cachly badge`** — new CLI command that outputs the Markdown + HTML snippet for embedding a live lesson-count badge in any README or website. Badge SVG served by `GET /api/v1/badge/:instanceId` (public, no auth, rate-limited 30 req/min, result cached 1 h in instance Valkey). Badge shows lesson count only — no topic names or content.
+- **Setup CTA** — both setup flows now print `npx ... badge` as the next suggested action after successful configuration.
+- **README** — Brain Badge section added with copy-paste Markdown snippet and explanation. Badge shield added to header.
+
+---
+
+## [0.10.8] – 2026-05-14
+
+### Viral CLI — 6 new commands
+
+- **`cachly demo`** — zero-signup Brain preview. Reads local `.git/` history, classifies commits by type (fix/feat/security/deploy/refactor/perf), and renders an ASCII table showing commit count, date range, contributors, per-category bar charts, and sample security + bug-fix lessons. No account or token required — works before any sign-in.
+
+- **`cachly share`** — shareable ASCII stats card. Fetches live Brain stats (lessons, recalls, tokens/cost saved, Brain level) and generates a tweet-ready text block with `#AIMemory #ClaudeCode #Cursor` hashtags. Requires `CACHLY_JWT`.
+
+- **`cachly digest`** — weekly Brain summary. Displays a formatted summary table: lessons stored, recalls performed, tokens saved, estimated cost saved, Brain level, top team contributors, and top-recalled lessons. Includes a crontab snippet for automated Monday morning delivery. Requires `CACHLY_JWT`.
+
+- **`cachly invite [email]`** — team referral. Accepts an email address as argument or via interactive prompt, then POSTs to `/api/v1/team/invite`. Handles 409 (already a member) gracefully. Requires `CACHLY_JWT`.
+
+- **`cachly health`** — connection check. Validates JWT (decode + expiry), tests API reachability, checks Brain instance status, scans all editor MCP config files (Claude Code, Cursor, Windsurf, VS Code, Zed, Continue), and verifies the git post-commit hook. Exits 1 if any checks fail — CI-friendly.
+
+- **No-args splash screen** — running `npx @cachly-dev/mcp-server@latest` in a TTY now shows a violet-framed help card listing all commands instead of silently starting the MCP server.
+
+### brain_from_git — Incremental mode + progress feedback
+
+- **Incremental by default** — after the first full run, subsequent calls only process commits since the last ingested SHA (stored in Redis with 90-day TTL). Repeated calls on active repos are near-instant.
+- **Progress output** — reports progress to stderr every ~10% of commits (`⏳ Processing N/total…`) and prints a completion summary (`✅ brain_from_git complete: N/total commits ingested`).
+- New `incremental` boolean parameter (default `true`). Pass `false` to force a full reprocess.
+
+### README
+
+- Complete rewrite: `cachly demo` featured at the very top with embedded ASCII preview output, all 6 CLI commands documented, Zed manual-setup section added, competitor table updated, FAQ expanded with incremental `brain_from_git` Q&A.
+
+---
+
 ## [0.10.0] – 2026-05-08
 
 ### Zero-Friction Onboarding

package/LAUNCH_TEXTS.md

@@ -0,0 +1,182 @@
+# Launch Texts — cachly AI Brain
+
+---
+
+## Product Hunt
+
+### Tagline (60 chars max)
+Persistent memory + causal AI for Claude, Cursor & Copilot
+
+### Description (260 chars)
+Your AI forgets everything between sessions. cachly fixes that permanently. One command sets it up: detects your editors, writes all configs, bootstraps lessons from your git history. Free forever. No credentials required.
+
+### Full Description
+
+**The problem:** Every morning you re-explain your architecture to your AI. Every bug gets re-researched. Every fix gets re-discovered. The average developer wastes 45 minutes/day on this.
+
+**The fix:** `npx @cachly-dev/mcp-server@latest setup`
+
+One command. It signs you in (one browser click), detects every editor you have (Claude Code, Cursor, Windsurf, VS Code, Copilot, Cline, Zed), writes the correct config for each, bootstraps your Brain from your git history, and installs a git hook that learns from every future commit automatically.
+
+**What your AI gets:**
+- A briefing at every session start: last session, open failures, relevant past fixes
+- Causal root cause analysis: `causal_trace("auth breaks after restart")` → Root cause → Chain → Exact fix from 3 months ago with the command that worked
+- Failure prediction before it happens: `brain_predict` reads your history before every deploy
+- A running "time saved" counter — so you can see the ROI
+
+**What makes it different from mem0, MemGPT, etc.:**
+The `causal_trace` tool. No other memory system builds a Causal Knowledge Graph. Most systems store facts. cachly stores WHY things broke and HOW they were fixed — with the full chain of cause and effect. 30 minutes of git blame in one call.
+
+**Free forever:** 25 MB, German servers, GDPR-compliant, no credit card.
+
+### First Comment (post immediately after launch)
+Hey PH! 👋
+
+I built cachly after watching my AI re-research the same deployment bug for the third time in a month. It had no memory. I did.
+
+The thing I'm most proud of: `causal_trace`. You describe a problem in plain English, and it walks your Brain's Causal Knowledge Graph to find: the root cause, the intermediate failure chain, and the exact fix that worked last time — including the date and the command. Nothing else does this.
+
+5000+ developers are already using the npm package. Would love your feedback on what's missing.
+
+**Commands to try after setup:**
+- `causal_trace(problem="[your last bug]")` — see if it already knows the answer
+- `brain_predict(context="about to deploy")` — what will go wrong?
+- `brain_doctor` — Brain health check
+
+---
+
+## Hacker News — Show HN
+
+**Title:**
+Show HN: cachly – causal memory for AI coding assistants (MCP server, free)
+
+**Text:**
+I built cachly after noticing that my AI re-researched the same bug three times in a month. The context window empties, the memory vanishes.
+
+cachly is an MCP server that gives Claude Code, Cursor, Copilot, and Windsurf persistent memory with one command:
+
+  npx @cachly-dev/mcp-server@latest setup
+
+It detects your editors, writes all the MCP configs, bootstraps from your git history, and installs a git hook that learns from every future commit. No credentials needed in any config file — OAuth Device Flow handles auth inline on the first tool call.
+
+The part I think is technically interesting: `causal_trace`. Instead of just storing facts like most memory systems, cachly builds a Causal Knowledge Graph — typed edges: `fixes`, `requires`, `co-occurs`, `causes`, `contradicts`. When you describe a problem, it walks the graph to reconstruct the failure chain and surface the exact fix.
+
+  causal_trace(problem="auth breaks after restart")
+  → Root: k8s:namespace-terminating
+  → Via:  keycloak:jwks-race
+  → Fix:  PollUntilContextTimeout 3min ← worked March 12
+
+Sessions start and end automatically (no manual session_start/session_end). Everything runs in the background.
+
+Free tier: 25 MB, German servers, GDPR. Apache-2.0.
+
+GitHub: https://github.com/cachly-dev/cachly-mcp
+npm: https://www.npmjs.com/package/@cachly-dev/mcp-server
+
+Happy to answer questions about the architecture.
+
+---
+
+## Reddit — r/ClaudeAI
+
+**Title:**
+I built persistent memory for Claude Code — no credentials, no config, one command
+
+**Text:**
+After the 10th time explaining my project architecture to Claude, I built cachly.
+
+**What it does:**
+Run `npx @cachly-dev/mcp-server@latest setup` once. It:
+1. Signs you in with one browser click (no credentials in config)
+2. Detects Claude Code, Cursor, Windsurf, VS Code, Cline — writes all configs automatically
+3. Bootstraps your Brain from your git history right away
+4. Installs a git hook so every future commit feeds the brain automatically
+
+From that point, your AI arrives pre-briefed every session. No `session_start` needed — it's automatic.
+
+**The feature I'm most excited about:**
+`causal_trace("auth breaks after restart")` — it doesn't just search for similar lessons, it walks a Causal Knowledge Graph to reconstruct the failure chain and return the exact fix you used before, with commands and file paths.
+
+**Free forever** — 25 MB, German servers, GDPR, no credit card.
+
+GitHub: https://github.com/cachly-dev/cachly-mcp
+
+Would love feedback from this community — what memory features would you most want?
+
+---
+
+## Reddit — r/LocalLLaMA
+
+**Title:**
+MCP server that learns from your git history automatically — causal memory for AI coding
+
+**Text:**
+Built this for the problem of AI context loss between sessions. Technical highlights:
+
+- **Causal Knowledge Graph (CKG):** Typed edges (fixes, requires, co-occurs, causes, contradicts). `causal_trace` walks the graph instead of just doing text similarity.
+- **Continuous Learning Stream:** git post-commit hook + GitHub Actions step. Every commit → lessons extracted automatically. Zero `session_end` calls needed.
+- **brain_predict:** Before deploys, reads your CKG for patterns that match past failures and returns probability-weighted warnings.
+- **Memory Crystals:** Compresses 30-50 sessions into a dense snapshot injected at every session start.
+- **11-language BM25+ search:** EN, DE, FR, ES, IT, PT, ZH, JA, KO, AR, HE — cross-lingual retrieval (e.g. `smart_recall("deploy")` finds デプロイ, 部署, 배포).
+
+Works with any MCP host: Claude Code, Cursor, Windsurf, VS Code, Cline, Zed, Continue.dev.
+
+Free tier: 25 MB. Apache-2.0. German servers.
+
+GitHub: https://github.com/cachly-dev/cachly-mcp
+
+---
+
+## Twitter/X Thread
+
+**Tweet 1:**
+Your AI forgets everything between sessions.
+I built the fix.
+
+`npx @cachly-dev/mcp-server@latest setup`
+
+One command → persistent AI memory across Claude, Cursor, Copilot, Windsurf.
+Free forever. 🧵
+
+**Tweet 2:**
+The part that took the longest to build: `causal_trace`
+
+You type: "auth breaks after restart"
+
+It returns:
+→ Root: k8s:namespace-terminating
+→ Via: keycloak:jwks-race
+→ Fix: PollUntilContextTimeout 3min ← you used this March 12, it worked
+
+30 minutes of git blame. One call.
+
+**Tweet 3:**
+How setup works:
+1. Run the command
+2. Browser opens → one click sign-in (no password)
+3. It detects every editor you have
+4. Writes MCP config for each automatically
+5. Bootstraps Brain from your git history
+6. Installs git hook for automatic future learning
+
+Restart editor. Done.
+
+**Tweet 4:**
+What your AI sees every morning:
+
+🧠 Session Briefing
+⏱️ Brain saved you ~4h 30m total
+✅ api:auth — Bearer in header, not cookie
+✅ docker:build — ARG changes bust cache
+⚠️ k8s:deploy — namespace terminating race condition
+
+🤝 Your team has 3 new lessons since yesterday
+
+**Tweet 5:**
+Free tier: 25 MB, German servers, GDPR-compliant, no credit card.
+Open source: Apache-2.0
+
+GitHub: github.com/cachly-dev/cachly-mcp
+npm: @cachly-dev/mcp-server
+
+If this saves you time, a ⭐ means a lot.