Your Cursor history. Your patterns. Fully local.
Bumps is a small dashboard that reads Cursor conversation data from your machine. Mirror mode turns it into plain, deterministic insights — where you stall, how you prompt, what seemed to work — with no cloud and no LLM: the same history always produces the same numbers and labels. Mentor mode adds AI-powered behavioral insights using your own Cursor Agent CLI, running locally on your machine.
Cursor chats pile up across projects. It’s hard to see patterns — what keeps pulling you back, whether short or long prompts correlate with fewer follow-ups, which areas you move through cleanly. Nothing in the editor gives you that bird’s-eye view, and you shouldn’t have to ship your chat history to someone else’s server to get it.
Start the CLI. One page. All on your computer.
npx getbumps
npx getbumps --mode=mentor # after Cursor Agent CLI setup — see RequirementsMirror (default): instant, rule-based analytics — same as the original product. Mentor: uses the Cursor Agent CLI for a separate dashboard; setup is local and under your account.
Your browser opens to http://127.0.0.1:3456 (default port 3456). The CLI prints what it’s doing—including Parsed in X ms after reading your local Cursor history (no PII)—reminds you that nothing is sent to a third-party service, and you stop the server with Ctrl+C when you’re done. The dashboard keeps the first paint light by loading the Your bumps Recharts widget in a separate JavaScript chunk after the shell.
URL tip: the server listens on IPv4 loopback (127.0.0.1) only, not ::1. On some systems, http://localhost:… resolves to IPv6 first and may not reach the app — if that happens, use http://127.0.0.1:<port> explicitly (or map localhost to 127.0.0.1 in your hosts file).
Why npx? It runs the published CLI from npm’s cache and does not add getbumps to your current project’s package.json — you can run it from any directory.
Optional — global install (same flags, shorter command):
npm install -g getbumps
getbumps
getbumps --port=3457| Local only | Data is read from Cursor’s on-disk storage on your machine. Nothing is uploaded or sent to a third party. |
| Mirror — no LLM | Mirror mode does not call a model to “interpret” your chats. It parses history and runs fixed rules (counts, buckets, simple stats). |
| Mentor — your CLI | Mentor mode uses your own Cursor Agent CLI running locally. Your data never leaves your machine. Analysis runs under your own Cursor account. |
| Read-only | SQLite databases are opened read-only. |
| You control the run | The server binds to 127.0.0.1 (loopback only, not all interfaces); you choose when to start and stop it. |
Mirror: widgets on the Mirror dashboard — Your Biggest Bump, Your Bumps, Scope Drift, Prompt Habits, What Worked (fast prompt shapes, file-type areas, Helpful Support, MCP usage, model follow-up stats where data exists); stat cards use exact session counts for the current filters and may show a short trust line about merged sources.
Mentor: the Mentor dashboard — behavioral insights from the same local history via your Cursor Agent CLI (see CLAUDE.md for flow and files).
Filters: project and time range (e.g. today, last 7 days, all time).
The published npm tarball does not ship a root lockfile (package-lock.json or npm-shrinkwrap.json). Install resolution uses the semver ranges in package.json, so transitive versions can shift between publishes or over time.
npx getbumps— npm installs (or reuses) the package in its cache; dependency versions follow those ranges at install time.- Contributors — clone the repo and run
npm installat the root: development usespackage-lock.json(committed) for reproducible local installs and CI.
If you need fully pinned installs for the published package, track or request npm-shrinkwrap.json as a maintainer decision; v1 ships without it for simplicity.
Links: github.com/barisermut/bumps · npmjs.com/package/getbumps
- Node.js (LTS recommended — e.g. 20.x or 22.x)
- macOS for v1 — paths follow Cursor’s default layout under your user Library (and related Cursor paths). Other OS support is not the focus yet.
- Cursor — this release targets Cursor only (not Claude Code, Windsurf, etc.).
- Cursor Agent CLI (required for Mentor mode, free one-time setup via
agent login)
| Default | npx getbumps → http://127.0.0.1:3456 |
| Custom port | npx getbumps --port=3457 |
| Port in use | The CLI exits with a short message; pick another --port. |
Cursor local files (global DB, workspace DBs, agent store, JSONL transcripts)
→ parser (read-only) — one canonical session per composerId, merged sources
→ in-memory structured sessions
→ Mirror: analyzer (deterministic rules) — insights + small meta block (counts, trust copy)
→ Mentor: mentor pipeline (Cursor Agent CLI on your machine) — behavioral insights
→ Express API + static React dashboard (MirrorDashboard / MentorDashboard by mode)
git clone https://github.com/barisermut/bumps.git
cd bumps
npm install
cd dashboard && npm install && npm run build && cd ..
node bin/getbumps.js- Dashboard dev server (hot reload):
cd dashboard && npm run dev - Parser / analyzer only:
node src/parser.js·node src/analyzer.js - Tests:
npm test - Product direction: docs/bumps-north-star.md · Architecture & conventions: CLAUDE.md and docs/bumps-v1-spec.md.
If dashboard/dist is missing, the CLI tells you to build the dashboard first. npm pack and npm publish both run prepack, which copies dashboard/dist into publish-dist/ for the tarball — the step fails until the dashboard is built. For a dry run without publishing: npm pack --dry-run.
Full instructions (npm account, login, first publish, 2FA): docs/npm-publish.md.
cd dashboard && npm install && npm run build && cd ..
npm test
npm pack --dry-run # optional
npm publish # after: npm login (use --otp=… if 2FA)prepack runs scripts/check-dashboard-dist.js then scripts/prepare-publish-dist.js; postpack removes temporary publish-dist/ after packing. Locally, src/paths.js prefers dashboard/dist when present.
ISC — see package.json.
