What problem does it solve? AI coding assistant logs are scattered across Claude Code, Codex, and Cursor in different formats, making it hard to answer questions about tool usage, costs, session history, and productivity patterns without manual digging through JSONL files. ## Core Features & Use Cases - Unified DuckDB Database: Incrementally loads logs from all three harnesses into one persistent database with unified views like interactions, daily_by_source, and repo_activity. - SQL and Search Interface: Run arbitrary SQL queries, search conversation content with ILIKE or BM25 full-text search, and inspect reasoning traces. - Cost Tracking: Pre-calculated cost_usd per invocation with editable model_pricing rates and aggregated cost_summary views. - Use Case: Ask which skills you use most, compare Claude Code versus Codex activity by repository, or find your peak coding hours over the last month. ## Quick Start Ask the agent to analyze your AI coding usage, for example by requesting your most used tools or a cost breakdown by repository for the past week.