getprismo 0.1.26 → 0.1.28

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # prismodev
2
2
 
3
+ [![npm version](https://img.shields.io/npm/v/getprismo.svg)](https://www.npmjs.com/package/getprismo)
4
+ [![npm downloads](https://img.shields.io/npm/dw/getprismo.svg)](https://www.npmjs.com/package/getprismo)
5
+ [![license: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
6
+
3
7
  local ai coding cost control. one command to diagnose token waste, fix it, and prove the improvement.
4
8
 
5
9
  ```bash
@@ -492,6 +496,14 @@ Run npx getprismo optimize, then start from .prismo/architecture-summary.md.
492
496
 
493
497
  timeline shows exactly what leaked, what repeated, and what to do differently next time.
494
498
 
499
+ to turn a postmortem into a safer next-session policy, run:
500
+
501
+ ```bash
502
+ npx getprismo cc timeline --firewall --task auth-bug
503
+ ```
504
+
505
+ this writes `.prismo/timeline-firewall-suggestions.md`, `.prismo/context-firewall.suggested.md`, `.prismo/allowed-context.suggested.txt`, and `.prismo/blocked-context.suggested.txt` from the latest session evidence. it does not overwrite your active firewall; it gives you a per-task allow/block recommendation for the next session.
506
+
495
507
  ---
496
508
 
497
509
  ## how doctor improves a repo
@@ -537,9 +549,49 @@ it only creates new files and recommendations. you decide what to apply.
537
549
 
538
550
  ---
539
551
 
552
+ ## cursor session tracking
553
+
554
+ prismodev now reads cursor's local sqlite databases directly. cursor stores data differently from claude code and codex, no jsonl session logs, but it has its own tracking databases with unique data.
555
+
556
+ ```bash
557
+ npx getprismo cursor # summary of all cursor sessions
558
+ npx getprismo cursor list # list composer sessions with modes and models
559
+ npx getprismo cursor authorship # ai vs human code authorship from scored commits
560
+ npx getprismo cursor timeline # timeline of ai activity across commits and files
561
+ npx getprismo cursor files # ai-generated and ai-deleted file tracking
562
+ npx getprismo cursor --json # machine-readable output
563
+ ```
564
+
565
+ cursor tracks something claude code and codex can't: per-commit ai authorship. every commit is scored with how many lines came from composer (agent), tab completions, and human typing. prismodev surfaces this as an authorship percentage.
566
+
567
+ ```
568
+ AI Authorship (from Cursor scored commits)
569
+
570
+ Commits analyzed: 47
571
+ Total lines added: 3812
572
+
573
+ Composer (agent): 2104 lines
574
+ Tab completions: 891 lines
575
+ Human: 817 lines
576
+ --------------------------------------------------
577
+ AI authorship: 78%
578
+ ```
579
+
580
+ prismodev also tracks ai-generated files cursor is watching, files cursor deleted, conversation summaries, and model usage distribution across sessions.
581
+
582
+ what cursor can't do vs claude code: cursor doesn't expose per-message token counts, exact api costs, or full conversation transcripts in its local data. that means live context pressure, loop detection, exact cost breakdowns, cache savings analysis, and shield don't apply the same way. this is a cursor limitation. prismodev gets about 60-65% feature parity with cursor compared to claude code/codex.
583
+
584
+ what cursor gives you that the others don't: ai authorship percentages per commit, tab vs composer vs human line counts, conversation summaries with tldr, and ai-generated file tracking with churn detection.
585
+
586
+ the `prismo_cursor_sessions` mcp tool exposes all of this to compatible agents.
587
+
588
+ `scan` and `doctor` now detect cursor's tracking database automatically and flag ai-generated files still present in the repo.
589
+
590
+ ---
591
+
540
592
  ## how watch catches waste live
541
593
 
542
- watch reads local session logs from codex and claude code. it detects:
594
+ watch reads local session logs from codex, claude code, and cursor. it detects:
543
595
 
544
596
  | signal | what it means |
545
597
  |--------|--------------|
@@ -615,6 +667,7 @@ no install needed. npx runs it directly.
615
667
  | `watch` | live session monitoring with warnings |
616
668
  | `cc` | claude code cost breakdown |
617
669
  | `cc timeline` | session reconstruction with events |
670
+ | `cursor` | cursor session tracking and ai authorship |
618
671
  | `scan --usage` | full repo scan with local usage data |
619
672
  | `scan --optimizer-fit` | recommend which token-optimization path fits your repo/session |
620
673
  | `scan --report-card` | shortest decision-layer summary |
@@ -669,6 +722,7 @@ npx getprismo watch --rescue --json # include rescuePrompt in JSON
669
722
  npx getprismo watch --once --redact-paths # hide local paths
670
723
  npx getprismo watch codex # only codex sessions
671
724
  npx getprismo watch claude # only claude code sessions
725
+ npx getprismo watch cursor # only cursor sessions
672
726
  ```
673
727
 
674
728
  ### shield mode
@@ -700,6 +754,7 @@ npx getprismo mcp /path/to/repo
700
754
  - `prismo_context_pack`
701
755
  - `prismo_firewall`
702
756
  - `prismo_cc_timeline`
757
+ - `prismo_cursor_sessions`
703
758
 
704
759
  This lets an MCP-compatible agent search prior shielded test/build output, request scoped context packs, inspect token-waste signals, or coordinate multiple local agents without pasting giant logs into the conversation.
705
760
 
@@ -736,6 +791,7 @@ For local development from this repo:
736
791
  ```bash
737
792
  npx getprismo cc # latest session cost
738
793
  npx getprismo cc timeline # event timeline for latest session
794
+ npx getprismo cc timeline --firewall --task auth-bug # suggest next-session firewall rules
739
795
  npx getprismo cc list # list recent sessions
740
796
  npx getprismo cc last 5 # last 5 sessions
741
797
  npx getprismo cc all # everything
@@ -793,9 +849,10 @@ local logs exact when codex/claude session logs expose token fields
793
849
  prismo proxy exact usage/cost when traffic routes through prismo base url
794
850
  ```
795
851
 
796
- prismodev reads local session logs from:
852
+ prismodev reads local session data from:
797
853
  - codex: `~/.codex/sessions/**/*.jsonl`
798
854
  - claude code: `~/.claude/projects/**/*.jsonl`
855
+ - cursor: `~/.cursor/ai-tracking/ai-code-tracking.db` and `~/Library/Application Support/Cursor/User/globalStorage/state.vscdb`
799
856
 
800
857
  no api keys. no intercepted prompts. no data uploaded.
801
858
 
@@ -881,7 +938,8 @@ lib/prismo-dev/scan-path-utils.js scan ignore/path helper logic
881
938
  lib/prismo-dev/shield.js local command shield and searchable output index
882
939
  lib/prismo-dev/usage-cost.js Claude Code cost and timeline analysis
883
940
  lib/prismo-dev/usage-log-utils.js local session log parsing helpers
884
- lib/prismo-dev/usage-sessions.js local Codex/Claude session discovery
941
+ lib/prismo-dev/cursor-sessions.js Cursor SQLite session and authorship tracking
942
+ lib/prismo-dev/usage-sessions.js local Codex/Claude/Cursor session discovery
885
943
  lib/prismo-dev/usage-watch.js watch orchestration, JSON payloads, live files
886
944
  lib/prismo-dev/utils.js shared terminal/file/token helpers
887
945
  lib/prismo-dev/watch-live.js live context-pressure decisions
@@ -901,6 +959,7 @@ npx getprismo shield --help
901
959
  npx getprismo mcp --help
902
960
  npx getprismo mcp doctor
903
961
  npx getprismo cc --help
962
+ npx getprismo cursor --help
904
963
  npx getprismo scan --help
905
964
  ```
906
965