diff --git a/README.md b/README.md
index 64eda6d0..0632c2ff 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ npx @code-insights/cli
code-insights dashboard
- The CLI parses sessions from Claude Code, Cursor, Codex CLI, and Copilot CLI into a + The CLI parses sessions from Claude Code, Cursor, Codex CLI, Pi, and Copilot CLI into a local SQLite database. All data stays on your machine.
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 30179ba8..dd5de014 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -22,7 +22,7 @@ code-insights/ │ ├── commands/ # CLI commands (init, sync, status, stats, dashboard, config, insights) │ ├── commands/stats/ # Stats command suite (4-layer architecture) │ ├── analysis/ # Prompt builders, response parsers, normalizers, runner interface (shared by CLI + server) -│ ├── providers/ # Source tool providers (claude-code, cursor, codex, copilot, copilot-cli) +│ ├── providers/ # Source tool providers (claude-code, cursor, codex, pi, copilot, copilot-cli) │ ├── parser/ # JSONL parsing, title generation │ ├── db/ # SQLite schema, migrations, queries │ ├── utils/ # Config, device, paths, telemetry @@ -66,7 +66,7 @@ code-insights/ - `actions/` — Action handlers for each subcommand + shared error handler - `index.ts` — Command tree with lazy imports - `shared.ts` — Shared CLI flags -- `providers/` — Source tool providers (claude-code, cursor, codex, copilot, copilot-cli) +- `providers/` — Source tool providers (claude-code, cursor, codex, pi, copilot, copilot-cli) - `providers/types.ts` — `SessionProvider` interface - `providers/registry.ts` — Provider registration and lookup - `parser/jsonl.ts` — JSONL file parsing (used by ClaudeCodeProvider) diff --git a/docs/LANDSCAPE.md b/docs/LANDSCAPE.md index e8a10ac5..bfe8895a 100644 --- a/docs/LANDSCAPE.md +++ b/docs/LANDSCAPE.md @@ -16,7 +16,7 @@ Code Insights occupies the **developer self-reflection analytics** layer — it | **Developer analytics** | Helps humans understand their AI usage patterns | **Code Insights** | | **Session capture** | Records what happened during a session | Entire.io CLI, Claude Code JSONL | -Code Insights is neutral across runtimes (parses 5 providers), analytics-focused (friction taxonomy, pattern taxonomy, weekly reflect), and local-first. Competing tools are typically tied to a single runtime and focused on forward-looking agent continuity rather than backward-looking human learning. +Code Insights is neutral across runtimes (parses 6 providers), analytics-focused (friction taxonomy, pattern taxonomy, weekly reflect), and local-first. Competing tools are typically tied to a single runtime and focused on forward-looking agent continuity rather than backward-looking human learning. --- @@ -43,7 +43,7 @@ Entire CLI captures rich context behind code changes: prompts, transcripts, and |-----------|-----------------|---------------| | Primary consumer | The AI agent (runtime) | The human developer (analytics) | | Time orientation | Present task continuity | Cross-session pattern aggregation | -| Source support | Entire CLI only | 5 providers (Claude Code, Cursor, Codex CLI, Copilot CLI, VS Code Copilot Chat) | +| Source support | Entire CLI only | 6 providers (Claude Code, Cursor, Codex CLI, Pi, Copilot CLI, VS Code Copilot Chat) | | Output | Agent context window | Dashboard, CLI stats, `.code-insights.md` | | Core question | "What was happening in this session?" | "How are my patterns changing over time?" | | Freshness gate | None | `code-insights attach --check` (CI staleness gate) | diff --git a/docs/PRODUCT.md b/docs/PRODUCT.md index 52c8bfbc..ae3519ab 100644 --- a/docs/PRODUCT.md +++ b/docs/PRODUCT.md @@ -6,7 +6,7 @@ Turn your AI coding sessions into knowledge. Code Insights extracts patterns fro ## The Problem -AI coding tools store every conversation as files on your machine. Claude Code uses JSONL in `~/.claude/projects/`. Cursor stores state in SQLite. Codex CLI and Copilot CLI write their own session formats. This is valuable data: +AI coding tools store every conversation as files on your machine. Claude Code and Pi use JSONL session files. Cursor stores state in SQLite. Codex CLI and Copilot CLI write their own session formats. This is valuable data: - What features did you work on last week? - Why did you choose that architecture? - What mistakes did you make (and fix)? @@ -29,7 +29,7 @@ Code Insights provides: ## Who It's For -- **Developers using multiple AI coding tools** who want to understand their AI-assisted work patterns across Claude Code, Cursor, Codex CLI, Copilot CLI, and VS Code Copilot Chat +- **Developers using multiple AI coding tools** who want to understand their AI-assisted work patterns across Claude Code, Cursor, Codex CLI, Pi, Copilot CLI, and VS Code Copilot Chat - **Learners** who want to review and reinforce what they've built with AI assistants - **Privacy-conscious developers** who want insights without giving up their data to a cloud service @@ -52,6 +52,7 @@ LLM analysis uses your own API key, stored in `~/.code-insights/config.json` (mo | **Claude Code** | JSONL sessions from `~/.claude/projects/` | | **Cursor** | Sessions from Cursor's local SQLite state | | **Codex CLI** | Rollout files from `~/.codex/sessions/` | +| **Pi** | JSONL sessions from `~/.pi/agent/sessions/` | | **Copilot CLI** | Event files from `~/.copilot/session-state/` | | **VS Code Copilot Chat** | Sessions from VS Code Copilot Chat local storage | @@ -316,6 +317,7 @@ Each provider implements the `SessionProvider` interface (`discover()`, `parse() | **Claude Code** | JSONL (append-only, one JSON object per line) | `~/.claude/projects/