claude-code-log 0.1.0__tar.gz

claude_code_log-0.1.0/.claude/settings.local.json

@@ -0,0 +1,29 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(python test:*)",
+      "Bash(uv sync:*)",
+      "Bash(uv run:*)",
+      "Bash(mkdir:*)",
+      "Bash(mv:*)",
+      "Bash(ruff check:*)",
+      "Bash(ruff format:*)",
+      "Bash(cat:*)",
+      "Bash(grep:*)",
+      "Bash(jq:*)",
+      "Bash(open test_tool_example.html)",
+      "Bash(uv lock:*)",
+      "Bash(source:*)",
+      "Bash(pytest:*)",
+      "Bash(rm:*)",
+      "Bash(uv pip install:*)",
+      "Bash(uv add:*)",
+      "Bash(python:*)",
+      "Bash(ls:*)",
+      "Bash(chmod:*)",
+      "Bash(rg:*)",
+      "Bash(act:*)"
+    ],
+    "deny": []
+  }
+}

claude_code_log-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12", "3.13"]
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+      with:
+        enable-cache: true
+
+    - name: Set up Python ${{ matrix.python-version }}
+      run: uv python install ${{ matrix.python-version }}
+
+    - name: Install dependencies
+      run: uv sync --all-extras --dev
+
+    - name: Run tests
+      run: uv run pytest
+
+    - name: Run linting
+      run: uv run ruff check
+
+    - name: Run formatting check
+      run: uv run ruff format --check
+
+    - name: Run type checking
+      run: uv run pyright

claude_code_log-0.1.0/.gitignore

@@ -0,0 +1,176 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+.examples

claude_code_log-0.1.0/CHANGELOG.md

@@ -0,0 +1,73 @@
+# Changelog
+
+All notable changes to claude-code-log will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+- **Summary Message Support**: Added support for `summary` type messages in JSONL transcripts
+  - Summary messages are displayed with green styling and "Summary:" prefix
+  - Includes special CSS class `.summary` for custom styling
+  
+- **System Command Visibility**: System commands (like `init`) are now shown instead of being filtered out
+  - Commands appear in expandable `<details>` elements
+  - Shows command name in the summary (e.g., "Command: init")
+  - Full command content is revealed when expanded
+  - Uses orange styling with `.system` CSS class
+  
+- **Markdown Rendering Support**: Automatic client-side markdown rendering
+  - Uses marked.js ESM module loaded from CDN
+  - Supports GitHub Flavored Markdown (GFM)
+  - Renders headers, emphasis, code blocks, lists, links, and images
+  - Preserves existing HTML content when present
+  
+- **Enhanced CSS Styling**: New styles for better visual organization
+  - Added styles for `.summary` messages (green theme)
+  - Added styles for `.system` messages (orange theme)  
+  - Added styles for `<details>` elements with proper spacing and cursor behavior
+  - Improved overall visual hierarchy
+
+### Changed
+
+- **System Message Filtering**: Modified system message handling logic
+  - System messages with `<command-name>` tags are no longer filtered out
+  - Added `extract_command_name()` function to parse command names
+  - Updated `is_system_message()` function to handle command messages differently
+  - Other system messages (stdout, caveats) are still filtered as before
+
+- **Message Type Support**: Extended message type handling in `load_transcript()`
+  - Now accepts `"summary"` type in addition to `"user"` and `"assistant"`
+  - Updated message processing logic to handle different content structures
+
+### Technical
+
+- **Dependencies**: No new Python dependencies added
+  - marked.js is loaded via CDN for client-side rendering
+  - Maintains existing minimal dependency approach
+  
+- **Testing**: Added comprehensive test coverage
+  - New test file `test_new_features.py` with tests for:
+    - Summary message type support
+    - System command message handling  
+    - Markdown script inclusion
+    - System message filtering behavior
+  - Tests use anonymized fixtures based on real transcript data
+
+- **Code Quality**: Improved type hints and function documentation
+  - Added proper docstrings for new functions
+  - Enhanced error handling for edge cases
+  - Maintained backward compatibility with existing functionality
+
+### Fixed
+
+- **Message Processing**: Improved robustness of message content extraction
+  - Better handling of mixed content types in transcript files
+  - More reliable text extraction from complex message structures
+
+## Previous Versions
+
+Earlier versions focused on basic JSONL to HTML conversion with session demarcation and date filtering capabilities.

claude_code_log-0.1.0/CLAUDE.md

@@ -0,0 +1,78 @@
+# Claude Code Log
+
+A Python CLI tool that converts Claude transcript JSONL files into readable HTML format.
+
+## Project Overview
+
+This tool processes Claude Code transcript files (stored as JSONL) and generates clean, minimalist HTML pages showing user prompts chronologically. It's designed to create a readable log of your Claude interactions.
+
+## Key Features
+
+- **Single File or Directory Processing**: Convert individual JSONL files or entire directories
+- **Chronological Ordering**: All messages sorted by timestamp across sessions
+- **Session Demarcation**: Clear visual separators between different transcript sessions
+- **User-Focused**: Shows only user messages by default (assistant responses filtered out)
+- **Date Range Filtering**: Filter messages by date range using natural language (e.g., "today", "yesterday", "last week")
+- **Space-Efficient Layout**: Compact design optimized for content density
+- **CLI Interface**: Simple command-line tool using Click
+
+## Usage
+
+```bash
+# Single file
+claude-code-log transcript.jsonl
+
+# Entire directory
+claude-code-log /path/to/transcript/directory
+
+# Custom output location
+claude-code-log /path/to/directory -o combined_transcripts.html
+
+# Open in browser after conversion
+claude-code-log /path/to/directory --open-browser
+
+# Filter by date range (supports natural language)
+claude-code-log /path/to/directory --from-date "yesterday" --to-date "today"
+claude-code-log /path/to/directory --from-date "last week"
+claude-code-log /path/to/directory --to-date "2025-06-01"
+claude-code-log /path/to/directory --from-date "3 days ago" --to-date "yesterday"
+```
+
+## File Structure
+
+- `claude_code_log/converter.py` - Core conversion logic
+- `claude_code_log/cli.py` - Command-line interface
+- `pyproject.toml` - Project configuration with Click dependency
+
+## Development
+
+The project uses:
+
+- Python 3.12+
+- Click for CLI
+- dateparser for natural language date parsing
+- Standard library for JSON/HTML processing
+
+## Development Commands
+
+### Testing
+
+Run tests with:
+
+```bash
+uv run pytest
+```
+
+### Code Quality
+
+- **Format code**: `ruff format`
+- **Lint and fix**: `ruff check --fix`
+- **Type checking**: `uv run pyright`
+
+### Testing & Style Guide
+
+- **Unit Tests**: See [test/README.md](test/README.md) for comprehensive testing documentation
+- **Visual Style Guide**: `uv run python scripts/generate_style_guide.py`
+- **Manual Testing**: Use representative test data in `test/test_data/`
+
+Test with Claude transcript JSONL files typically found in `~/.claude/projects/` directories.

claude_code_log-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Daniel Demmel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

claude_code_log-0.1.0/PKG-INFO

@@ -0,0 +1,212 @@
+Metadata-Version: 2.4
+Name: claude-code-log
+Version: 0.1.0
+Summary: Convert Claude transcript JSONL files to HTML
+Project-URL: Homepage, https://github.com/daaain/claude-code-log
+Project-URL: Issues, https://github.com/daaain/claude-code-log/issues
+Author-email: Daniel Demmel <hello@danieldemmel.me>, "Edward Z. Yang" <ezyang@mit.edu>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.12
+Requires-Dist: click>=8.0.0
+Requires-Dist: dateparser>=1.0.0
+Requires-Dist: jinja2>=3.0.0
+Requires-Dist: pydantic>=2.0.0
+Description-Content-Type: text/markdown
+
+# Claude Code Log
+
+A Python CLI tool that converts Claude transcript JSONL files into readable HTML format.
+
+## Project Overview
+
+This tool processes Claude Code transcript files (stored as JSONL) and generates clean, minimalist HTML pages showing user prompts chronologically. It's designed to create a readable log of your Claude interactions with support for both individual files and entire project hierarchies.
+
+## Key Features
+
+- **Project Hierarchy Processing**: Process entire `~/.claude/projects/` directory with linked index page
+- **Single File or Directory Processing**: Convert individual JSONL files or specific directories
+- **Chronological Ordering**: All messages sorted by timestamp across sessions
+- **Session Demarcation**: Clear visual separators between different transcript sessions
+- **User-Focused**: Shows only user messages by default (assistant responses filtered out)
+- **Date Range Filtering**: Filter messages by date range using natural language (e.g., "today", "yesterday", "last week")
+- **Summary Support**: Display summary messages with highlighted formatting
+- **System Command Visibility**: Show system commands (like `init`) in expandable details
+- **Markdown Rendering**: Automatic markdown rendering in message content using marked.js
+- **Project Navigation**: Master index page with project statistics and quick navigation
+- **Space-Efficient Layout**: Compact design optimized for content density
+- **CLI Interface**: Simple command-line tool using Click
+
+## Usage
+
+### Default Behavior (Process All Projects)
+
+```bash
+# Process all projects in ~/.claude/projects/ (default behavior)
+claude-code-log
+
+# Explicitly process all projects
+claude-code-log --all-projects
+
+# Process all projects and open in browser
+claude-code-log --open-browser
+
+# Process all projects with date filtering
+claude-code-log --from-date "yesterday" --to-date "today"
+claude-code-log --from-date "last week"
+```
+
+This creates:
+
+- `~/.claude/projects/index.html` - Master index with project cards and statistics
+- `~/.claude/projects/project-name/combined_transcripts.html` - Individual project pages
+
+### Single File or Directory Processing
+
+```bash
+# Single file
+claude-code-log transcript.jsonl
+
+# Specific directory
+claude-code-log /path/to/transcript/directory
+
+# Custom output location
+claude-code-log /path/to/directory -o combined_transcripts.html
+
+# Open in browser after conversion
+claude-code-log /path/to/directory --open-browser
+
+# Filter by date range (supports natural language)
+claude-code-log /path/to/directory --from-date "yesterday" --to-date "today"
+claude-code-log /path/to/directory --from-date "3 days ago" --to-date "yesterday"
+```
+
+## File Structure
+
+- `claude_code_log/converter.py` - Core conversion logic and hierarchy processing
+- `claude_code_log/cli.py` - Command-line interface with project discovery
+- `claude_code_log/models.py` - Pydantic models for transcript parsing
+- `pyproject.toml` - Project configuration with dependencies
+
+## Development
+
+The project uses:
+
+- Python 3.12+ with uv package management
+- Click for CLI interface and argument parsing
+- Pydantic for robust data modeling and validation
+- dateparser for natural language date parsing
+- Standard library for JSON/HTML processing
+- Minimal dependencies for portability
+- marked.js (CDN) for client-side markdown rendering
+
+## Development Commands
+
+### Testing
+
+Run tests with:
+
+```bash
+uv run pytest
+```
+
+**Comprehensive Testing & Style Guide**: The project includes extensive testing infrastructure and visual documentation. See [test/README.md](test/README.md) for details on:
+
+- **Unit Tests**: Template rendering, message type handling, edge cases
+- **Visual Style Guide**: Interactive documentation showing all message types
+- **Representative Test Data**: Real-world JSONL samples for development
+- **Style Guide Generation**: Create visual documentation with `uv run python scripts/generate_style_guide.py`
+
+### Code Quality
+
+- **Format code**: `ruff format`
+- **Lint and fix**: `ruff check --fix`
+- **Type checking**: `uv run pyright`
+
+### All Commands
+
+- **Test**: `uv run pytest`
+- **Format**: `ruff format`
+- **Lint**: `ruff check --fix`
+- **Type Check**: `uv run pyright`
+- **Generate Style Guide**: `uv run python scripts/generate_style_guide.py`
+
+Test with Claude transcript JSONL files typically found in `~/.claude/projects/` directories.
+
+## Project Hierarchy Output
+
+When processing all projects, the tool generates:
+
+```sh
+~/.claude/projects/
+├── index.html                    # Master index with project cards
+├── project1/
+│   └── combined_transcripts.html # Individual project page
+├── project2/
+│   └── combined_transcripts.html
+└── ...
+```
+
+### Index Page Features
+
+- **Project Cards**: Each project shown as a clickable card with statistics
+- **Summary Statistics**: Total projects, transcript files, and message counts
+- **Recent Activity**: Projects sorted by last modification date
+- **Quick Navigation**: One-click access to any project's detailed transcript
+- **Clean URLs**: Readable project names converted from directory names
+
+## Message Types Supported
+
+- **User Messages**: Regular user inputs and prompts
+- **Assistant Messages**: Claude's responses (when not filtered)
+- **Summary Messages**: Session summaries with special formatting
+- **System Commands**: Commands like `init` shown in expandable details
+- **Tool Use**: Tool invocations and results with proper formatting
+
+## HTML Output Features
+
+- **Responsive Design**: Works on desktop and mobile
+- **Syntax Highlighting**: Code blocks properly formatted
+- **Markdown Support**: Full markdown rendering including:
+  - Headers, lists, emphasis
+  - Code blocks and inline code
+  - Links and images
+  - GitHub Flavored Markdown features
+- **Session Navigation**: Clear visual breaks between transcript sessions
+- **Command Visibility**: System commands shown with context but not cluttering the main view
+- **Tool Interactions**: Tool use and results displayed in collapsible sections
+
+## Installation
+
+Install using pip (coming soon to PyPI):
+
+```bash
+pip install claude-code-log
+```
+
+Or install from source:
+
+```bash
+git clone https://github.com/your-username/claude-code-log.git
+cd claude-code-log
+uv sync
+uv run claude-code-log
+```
+
+## TODO
+
+- ✅ **Project Hierarchy Processing**: Process entire `~/.claude/projects/` with linked navigation
+- ✅ **Master Index Page**: Project cards with statistics and quick navigation
+- **Enhanced UI**: Make it look even nicer with improved styling
+- **GitHub Action CI**: Automated testing and deployment
+- ✅ **Template Refactoring**: Move HTML templates into separate files (use Jinja or similar)
+- Handle thinking tokens
+- Handle pasted images (and text?)
+- **Tool Use Preview**: Show first few lines of tool use and other collapsed details
+- **Rich Metadata**: Render timestamps, durations, token usage, etc.
+- **Session Navigation**: Navigation between sessions within page
+- **In-page Filtering**: Client-side filtering and search
+- **PyPI Publishing**: Push to PyPI with secure token
+- **TodoWrite Rendering**: Render TodoWrite as actual todo list with checkboxes