code-session-memory 0.3.2 → 0.4.0

package/README.md

@@ -51,9 +51,9 @@ The `install` command sets up everything for both tools in one shot:
 3. Writes the MCP server entry into `~/.config/opencode/opencode.json`
 
 **Claude Code:**
-1. Writes a `Stop` hook to `~/.claude/settings.json` (fires after each agent turn)
+1. Writes a `Stop` hook to `~/.claude.json` (user-scoped global config; fires after each agent turn)
 2. Injects the skill into `~/.claude/CLAUDE.md` (with idempotent markers)
-3. Registers the MCP server via `claude mcp add`
+3. Writes the MCP server entry into `~/.claude.json`
 
 **Both tools share:**
 - The same database at `~/.local/share/code-session-memory/sessions.db`
@@ -94,7 +94,7 @@ code-session-memory status
     MCP config     ~/.config/opencode/opencode.json                    ✓
 
   Claude Code
-    Stop hook      ~/.claude/settings.json                             ✓
+    Stop hook      ~/.claude.json                                      ✓
     Skill          ~/.claude/CLAUDE.md                                 ✓
     MCP server     /path/to/dist/mcp/index.js                          ✓
 ```
@@ -137,6 +137,57 @@ Retrieve the full ordered content of a specific session message. Use the `sessio
 | `startIndex` | number | no | First chunk index (0-based) |
 | `endIndex` | number | no | Last chunk index (0-based, inclusive) |
 
+### Browsing sessions
+
+You can browse, inspect, and delete indexed sessions directly from the CLI:
+
+```bash
+npx code-session-memory sessions           # interactive browser
+npx code-session-memory sessions --filter  # with source/date filter step
+```
+
+The interactive browser lists all sessions with their title, date, source tool, and chunk count. Select a session to:
+- **Print** — dump all chunks to stdout (useful for piping or inspection)
+- **Delete** — remove the session from the DB (with confirmation)
+- **Back** — return to the session list
+
+You can also `print` or `delete` directly. Without an ID, an interactive picker opens:
+
+```bash
+npx code-session-memory sessions print             # pick interactively, then print
+npx code-session-memory sessions print --filter    # filter first, then pick and print
+npx code-session-memory sessions print <id>        # print directly by session ID
+
+npx code-session-memory sessions delete            # pick interactively, then delete
+npx code-session-memory sessions delete --filter   # filter first, then pick and delete
+npx code-session-memory sessions delete <id>       # delete directly by session ID
+```
+
+**Print output example:**
+```
+────────────────────────────────────────────────────────────────────────
+Session: Add authentication middleware
+Source:  opencode  2026-02-18
+Project: /Users/you/myproject
+ID:      ses_abc123
+Chunks:  12
+────────────────────────────────────────────────────────────────────────
+
+## Chunk 1/12  —  Section: User
+
+How can I add JWT authentication to the Express middleware?
+
+## Chunk 2/12  —  Section: Assistant
+
+...
+```
+
+**Filtering options** (with `--filter`):
+- Source: All tools / OpenCode / Claude Code
+- Date range: Last 7 / 30 / 90 days, last N days (custom), or older than N days (custom)
+
+> **Note:** Deleting a session only removes it from the database. If the original session files still exist on disk, the session will be re-indexed automatically on the next agent turn.
+
 ### Asking the agent about past sessions
 
 The installed skill teaches the agent when and how to use these tools. Example prompts:
@@ -183,7 +234,8 @@ code-session-memory/
 │   ├── indexer.ts                # Orchestrator: incremental indexing
 │   ├── indexer-cli.ts            # Node.js subprocess (called by OpenCode plugin)
 │   ├── indexer-cli-claude.ts     # Node.js subprocess (called by Claude Code hook)
-│   └── cli.ts                    # install / status / uninstall commands
+│   ├── cli.ts                    # install / status / uninstall / reset-db commands
+│   └── cli-sessions.ts           # sessions list / print / delete (interactive TUI)
 ├── mcp/
 │   ├── server.ts                 # MCP query handlers (testable, injected deps)
 │   └── index.ts                  # MCP stdio server entry point
@@ -191,13 +243,18 @@ code-session-memory/
 │   └── memory.ts                 # OpenCode plugin (session.idle hook)
 ├── skill/
 │   └── memory.md                 # Skill instructions (injected into both tools)
+├── scripts/
+│   └── generate-fixtures.ts      # Generates committed e2e test fixtures (run manually)
 └── tests/
     ├── chunker.test.ts
     ├── database.test.ts
     ├── embedder.test.ts
     ├── indexer.test.ts
     ├── mcp-server.test.ts
-    └── session-to-md.test.ts
+    ├── session-to-md.test.ts
+    ├── e2e-claude.test.ts        # End-to-end: Claude Code pipeline
+    ├── e2e-opencode.test.ts      # End-to-end: OpenCode pipeline
+    └── fixtures/                 # Committed session files (generated by generate-fixtures)
 ```
 
 ## Development
@@ -217,38 +274,73 @@ npm run test:watch
 
 # Coverage report
 npm run test:coverage
+
+# Regenerate e2e fixtures (requires claude and opencode CLIs)
+npm run generate-fixtures
 ```
 
 ### Running tests
 
 Tests use [Vitest](https://vitest.dev) and run without any external dependencies:
 - No real OpenAI API calls — the embedder is mocked
-- No real DB files — SQLite uses in-memory databases (`:memory:`) for unit tests
-- Indexer tests use a temp directory on disk
+- No real DB files — SQLite uses in-memory databases (`:memory:`) for unit tests, temp files for indexer/e2e tests
+- E2e tests use committed fixture files in `tests/fixtures/` (real transcripts, no CLI calls during `npm test`)
 
 ```
- ✓ tests/chunker.test.ts       (15 tests)
- ✓ tests/mcp-server.test.ts    (13 tests)
- ✓ tests/session-to-md.test.ts (18 tests)
- ✓ tests/embedder.test.ts       (9 tests)
- ✓ tests/database.test.ts      (25 tests)
- ✓ tests/indexer.test.ts        (8 tests)
-   Tests  88 passed
+ ✓ tests/chunker.test.ts        (15 tests)
+ ✓ tests/mcp-server.test.ts     (13 tests)
+ ✓ tests/session-to-md.test.ts  (18 tests)
+ ✓ tests/embedder.test.ts        (9 tests)
+ ✓ tests/database.test.ts       (25 tests)
+ ✓ tests/indexer.test.ts         (8 tests)
+ ✓ tests/e2e-claude.test.ts     (16 tests)
+ ✓ tests/e2e-opencode.test.ts   (14 tests)
+   Tests  118 passed
 ```
 
+To refresh the e2e fixtures (e.g. after changing the indexer or parsers), run:
+```bash
+npm run generate-fixtures
+```
+This invokes the real `claude` and `opencode` CLIs to generate two-turn sessions with tool use, then commits the results to `tests/fixtures/`.
+
 ## Uninstall
 
 ```bash
 npx code-session-memory uninstall
 ```
 
-This removes the plugin, hooks, and skill files for both tools. The database is **not** removed automatically.
+This removes the plugin, hooks, skill files, and MCP config entries for both tools. The database is **not** removed automatically.
+
+To delete individual sessions instead of wiping everything, use the [session browser](#browsing-sessions):
+```bash
+npx code-session-memory sessions
+npx code-session-memory sessions delete <id>
+```
 
-To also remove the database:
+To wipe the entire database:
 ```bash
 rm ~/.local/share/code-session-memory/sessions.db
 ```
 
+Or use the built-in command, which prompts for confirmation before deleting:
+
+```bash
+npx code-session-memory reset-db
+```
+
+```
+code-session-memory reset-db
+
+  Database: ~/.local/share/code-session-memory/sessions.db
+  Indexed chunks:   1842
+  Sessions tracked: 47
+
+  This will permanently delete all indexed data. Confirm? [y/N] y
+
+  Done. Database reset — all indexed data removed.
+```
+
 ## Architecture notes
 
 ### Incremental indexing

package/dist/src/cli-sessions.d.ts

@@ -0,0 +1,16 @@
+#!/usr/bin/env node
+/**
+ * sessions sub-commands for code-session-memory CLI
+ *
+ *   sessions [list]              Browse sessions (interactive TUI)
+ *   sessions list --filter       Browse with filter step first
+ *   sessions print [id]          Print all chunks of a session to stdout
+ *   sessions print --filter      Pick session interactively with filter, then print
+ *   sessions delete [id]         Delete a session from the DB
+ *   sessions delete --filter     Pick session interactively with filter, then delete
+ */
+export declare function cmdSessionsList(args: string[]): Promise<void>;
+export declare function cmdSessionsPrint(sessionId?: string, args?: string[]): Promise<void>;
+export declare function cmdSessionsDelete(sessionId?: string, args?: string[]): Promise<void>;
+export declare function cmdSessions(argv: string[]): Promise<void>;
+//# sourceMappingURL=cli-sessions.d.ts.map

package/dist/src/cli-sessions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli-sessions.d.ts","sourceRoot":"","sources":["../../src/cli-sessions.ts"],"names":[],"mappings":";AACA;;;;;;;;;GASG;AAkPH,wBAAsB,eAAe,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAkDnE;AAMD,wBAAsB,gBAAgB,CAAC,SAAS,CAAC,EAAE,MAAM,EAAE,IAAI,GAAE,MAAM,EAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAiB7F;AAmDD,wBAAsB,iBAAiB,CAAC,SAAS,CAAC,EAAE,MAAM,EAAE,IAAI,GAAE,MAAM,EAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAoD9F;AAwCD,wBAAsB,WAAW,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAuC/D"}