claude-code-log 1.1.1__tar.gz → 1.3.0__tar.gz

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/.claude/skills/tool-renderer/SKILL.md

@@ -260,6 +260,32 @@ def title_WebSearchInput(self, input: WebSearchInput, message: TemplateMessage)
     return self._tool_title(message, "🔎", f'"{input.query}"')
 ```
 
+### Watch out: the template's wrench-suppression is emoji-range-gated
+
+Tool-use messages get a default `🛠️` prefix prepended by
+`templates/transcript.html` *unless* the title already starts with
+an emoji that `html/utils.py::starts_with_emoji` recognises. That
+function whitelists specific Unicode ranges:
+
+- `0x2300-0x23FF` Misc Technical (`⏰ ⏳ ⏱️ ⏲️ ⏸ ⏹ ⏺ ⏏` …)
+- `0x2600-0x26FF` Misc Symbols
+- `0x2700-0x27BF` Dingbats
+- `0x1F300-0x1F5FF` Misc Symbols and Pictographs
+- `0x1F600-0x1F64F` Emoticons
+- `0x1F680-0x1F6FF` Transport and Map Symbols
+- `0x1F900-0x1F9FF` Supplemental Symbols
+
+If the icon you pass to `_tool_title` falls **outside** these
+ranges, the template will helpfully add a `🛠️` in front of it,
+producing a redundant double-icon title like
+`🛠️ <your-icon> <ToolName>`. Verify by rendering a fixture and
+grepping for `🛠️` co-occurring with your icon, or by checking
+`ord(your_icon)` against the ranges above.
+
+If your icon is a real emoji that lives in a Unicode range not
+listed there, **add the range** to `starts_with_emoji` rather than
+picking a different icon.
+
 ## Step 5: Implement Markdown Renderer
 
 In `markdown/renderer.py`:
@@ -369,7 +395,7 @@ class Test{ToolName}OutputFormatting:
 uv run pytest test/test_{toolname}_rendering.py -v
 
 # Run full test suite to check for regressions
-uv run pytest -n auto -m "not (tui or browser)" -v
+uv run pytest -m "not (tui or browser)" -v
 ```
 
 ## Checklist

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/.github/workflows/ci.yml

@@ -33,13 +33,13 @@ jobs:
       run: uv sync --all-extras --dev && uv run playwright install chromium
 
     - name: Run unit tests with coverage
-      run: uv run pytest -n auto -m "not (tui or browser or benchmark)" --cov=claude_code_log --cov-report=xml --cov-report=html --cov-report=term
+      run: uv run pytest -m "not (tui or browser or benchmark)" --cov=claude_code_log --cov-report=xml --cov-report=html --cov-report=term
 
     - name: Run TUI tests with coverage append
-      run: uv run pytest -n auto -m tui --cov=claude_code_log --cov-append --cov-report=xml --cov-report=html --cov-report=term
+      run: uv run pytest -m tui --cov=claude_code_log --cov-append --cov-report=xml --cov-report=html --cov-report=term
 
     - name: Run browser tests with coverage append
-      run: uv run pytest -n auto -m browser --cov=claude_code_log --cov-append --cov-report=xml --cov-report=html --cov-report=term
+      run: uv run pytest -m browser --cov=claude_code_log --cov-append --cov-report=xml --cov-report=html --cov-report=term
 
     - name: Run benchmark tests with coverage append (primary only)
       if: matrix.is-primary

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/CHANGELOG.md

@@ -6,6 +6,58 @@ 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).
 
 
+## [1.3.0] - 2026-05-14
+
+### Changed
+
+- **Render ScheduleWakeup and Cron* tools (#148) (#152)**
+- **Render hook attachment entries at FULL detail (#128) (#149)**
+- **Style sidechain filter toggle with dashed border**
+- **scrub_surrogates: handle high surrogate range (CR follow-up) (#150)**
+- **Render the built-in Monitor tool with Task-end backlink (#142) (#147)**
+- **Add support for ai-title and prefer it over legacy summary (#136)**
+- **fix: add errors='replace' to read_text/write_text for Unicode safety (#139) (#146)**
+- **Fix UnicodeEncodeError on JSONL with lone surrogates (#139) (#144)**
+- **Use `--dist=worksteal` to speed up tests + move `-n auto` to config to make it default (#145)**
+- **Fix/prevent dag cycle (#138)**
+- **Render away_summary recap entries (#111) (#141)**
+- **System info cosmetic improvements + chain-pairing fix (#137) (#140)**
+- **dev-docs: introduce application_model.md as entry point, normalize naming, clean work/ (#134)**
+- **export conversations to json (#36)**
+- **Suppress noise in system-info messages (#129) (#133)**
+- **Fix DAG cyclic-children hang and add SIGUSR1 stack dump (#135)**
+- **Support async agents (#90) (#132)**
+- **Robust within-session fork rendering: collapse parallel-tool_use forks, consistent labels (#131)**
+- **Render user content as Markdown with raw fallback toggle (#119)**
+- **Add --detail user-only level (#118)**
+- **Pair Slash Command with User (slash command) (#126) (#127)**
+- **Fold Skill name into tool_use title and drop the params row**
+- **Fold Skill body into its tool_use block (#121)**
+- **docs: add Community Extensions section (#120)**
+- **Support teammates (#91): stitching + session headers + index (PR 3 of 3) (#125)**
+- **Support teammates (#91): rendering (PR 2 of 3) (#122)**
+- **Support teammates (#91): parsing + data model (draft) (#117)**
+
+
+## [1.2.0] - 2026-04-19
+
+### Changed
+
+- **Preserve agentId anchors in parallel-Task stitch + tool-param UI fix (#115)**
+- **Per-level output files for --detail and --compact (#114)**
+- **Handle custom-title, agent-name, and agent-color transcript entry types (#113)**
+- **Ignore 'last-prompt' message type (#112)**
+- **Detail levels and compact rendering of conversations (#96)**
+- **Skip PassthroughTranscriptEntry in _render_messages**
+- **Integrate agent transcripts into the DAG (Phase C) (#99)**
+- **Implement DAG-based message ordering (Phases A+B) (#97)**
+- **Fix slow test hitting real ~/.claude/projects (5GB) (#109)**
+- **feat: add --session-id flag for exporting a single  (#103)**
+- **Fix search broken when HTML saved with different filename (#106)**
+- **Add Grep tool renderer with pattern in title (#107)**
+- **Fix TUI square bracket escaping issue (#105)**
+
+
 ## [1.1.1] - 2026-03-10
 
 ### Changed

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/CLAUDE.md

@@ -47,28 +47,30 @@ claude-code-log --from-date "last week"
 
 See @CONTRIBUTING.md for detailed development setup, testing, architecture, and release process.
 
+**Before pushing, always remind the user to run `just ci`.**
+
 ### Claude-Specific Testing Tips
 
-**Always use `-n auto` for parallel test execution:**
+**Config in `pyproject.toml` sets `-n auto --dist=worksteal` so you might need to unset for pdb, etc**
 
 ```bash
 # Unit tests (fast, recommended for development)
 just test
-# or: uv run pytest -n auto -m "not (tui or browser)" -v
+# or: uv run pytest -m "not (tui or browser)" -v
 
 # TUI tests
 just test-tui
-# or: uv run pytest -n auto -m tui
+# or: uv run pytest -m tui
 
 # Browser tests
 just test-browser
-# or: uv run pytest -n auto -m browser
+# or: uv run pytest -m browser
 
 # All tests
 just test-all
 ```
 
-**Tip:** Add `-x` to stop on first failure (e.g., `uv run pytest -n auto -m "not (tui or browser)" -v -x`).
+**Tip:** Add `-x` to stop on first failure (e.g., `uv run pytest -m "not (tui or browser)" -v -x`).
 
 ### Code Quality
 
@@ -93,7 +95,30 @@ The interactive timeline is implemented in JavaScript within `claude_code_log/te
 
 ## Architecture
 
-For detailed architecture documentation, see:
+Start with [dev-docs/application_model.md](dev-docs/application_model.md)
+— the entry point covering subsystems, data lifecycle, and a glossary,
+with pointers to the deep-dive docs:
+
 - [dev-docs/rendering-architecture.md](dev-docs/rendering-architecture.md) - Data flow and rendering pipeline
 - [dev-docs/messages.md](dev-docs/messages.md) - Message type reference
 - [dev-docs/css-classes.md](dev-docs/css-classes.md) - CSS class combinations
+- [dev-docs/dag.md](dev-docs/dag.md) - DAG-based session/fork architecture
+- [dev-docs/agents.md](dev-docs/agents.md) - Sync/async/teammate agent integration
+- [dev-docs/teammates.md](dev-docs/teammates.md) - Teammates feature deep-dive
+- [dev-docs/message-hierarchy.md](dev-docs/message-hierarchy.md) - Fold/unfold state machine
+- [dev-docs/implementing-a-tool-renderer.md](dev-docs/implementing-a-tool-renderer.md) - How-to: add a new tool
+
+User-facing docs live in [docs/](docs/); plans and TODOs live in [work/](work/).
+
+### Keeping dev-docs/ in sync
+
+`dev-docs/` is **as-built reference** — the code is the authoritative
+source. When a non-trivial change alters behavior, structure, or
+invariants documented in a deep-dive, update the relevant page in
+the same commit (or as a prompt follow-up). If `dev-docs/` and the
+code disagree, the doc is wrong.
+
+Typical lifecycle: a feature begins as a spec in `work/`, evolves
+into a WIP scratchpad as the code adapts to reality, then graduates
+into `dev-docs/` (new page or merged into an existing one) once the
+implementation has stabilized.

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/CONTRIBUTING.md

@@ -50,7 +50,9 @@ claude_code_log/
 
 scripts/                # Development utilities
 test/test_data/         # Representative JSONL samples
-dev-docs/               # Architecture documentation
+dev-docs/               # Architecture / dev documentation (start in application_model.md)
+docs/                   # User-facing operations docs
+work/                   # Plans, TODOs, in-flight design docs
 ```
 
 ## Development Setup
@@ -94,7 +96,7 @@ The project uses a categorized test system to avoid async event loop conflicts.
 ```bash
 # Unit tests only (fast, recommended for development)
 just test
-# or: uv run pytest -n auto -m "not (tui or browser)" -v
+# or: uv run pytest -m "not (tui or browser)" -v
 
 # TUI tests (isolated event loop)
 just test-tui
@@ -114,16 +116,23 @@ just test-cov
 Snapshot tests detect unintended HTML output changes using [syrupy](https://github.com/syrupy-project/syrupy):
 
 ```bash
-# Run snapshot tests
-uv run pytest -n auto test/test_snapshot_html.py -v
+# Run snapshot tests (parallel mode is fine for read-only runs)
+uv run pytest test/test_snapshot_html.py -v
 
 # Update snapshots after intentional HTML changes
-uv run pytest -n auto test/test_snapshot_html.py --snapshot-update
+# IMPORTANT: run --snapshot-update with -n0 (see warning below)
+uv run pytest test/test_snapshot_html.py -n0 --snapshot-update
 ```
 
+> **Warning — don't let `--snapshot-update` run with `-n auto`.** Syrupy
+> and pytest-xdist race when writing snapshot files in parallel: the
+> `.ambr` file ends up truncated (observed: ~6000 lines silently
+> deleted on a single run, leaving the file structurally broken but
+> still passing on next read). Run `--snapshot-update` serially.
+
 When snapshot tests fail:
 1. Review the diff to verify changes are intentional
-2. If intentional, run `--snapshot-update` to accept new output
+2. If intentional, run `--snapshot-update` (serially) to accept new output
 3. If unintentional, fix your code and re-run tests
 
 ### Test Prerequisites
@@ -151,7 +160,7 @@ Running all tests together can cause "RuntimeError: This event loop is already r
 just test-cov
 
 # Or manually:
-uv run pytest -n auto --cov=claude_code_log --cov-report=html --cov-report=term
+uv run pytest --cov=claude_code_log --cov-report=html --cov-report=term
 ```
 
 HTML coverage reports are generated in `htmlcov/index.html`.
@@ -186,9 +195,23 @@ CLAUDE_CODE_LOG_DEBUG_TIMING=1 claude-code-log path/to/file.jsonl
 
 This outputs detailed timing for each rendering phase. The timing module is in `claude_code_log/renderer_timings.py`.
 
+## Diagnosing Hangs
+
+If `claude-code-log` appears stuck (100% CPU, no output), send `SIGUSR1` to print the live Python stack to stderr without killing the process:
+
+```bash
+# In another terminal
+kill -USR1 $(pgrep -f claude-code-log | head -1)
+```
+
+The handler is installed in `cli.py` via `faulthandler.register(SIGUSR1)`. POSIX-only; no-op on Windows. Unlike `py-spy`, it needs no root and no extra install.
+
 ## Architecture
 
-For detailed architecture documentation, see [dev-docs/rendering-architecture.md](dev-docs/rendering-architecture.md).
+Start with [dev-docs/application_model.md](dev-docs/application_model.md)
+for the system overview (subsystems, data lifecycle, glossary). For
+the rendering pipeline specifically, see
+[dev-docs/rendering-architecture.md](dev-docs/rendering-architecture.md).
 
 ### Data Flow Overview
 

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-log
-Version: 1.1.1
+Version: 1.3.0
 Summary: Convert Claude Code 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
@@ -66,6 +66,7 @@ uvx claude-code-log@latest --open-browser
 - **Rich Message Types**: Support for user/assistant messages, tool use/results, thinking content, images
 - **System Command Visibility**: Show system commands (like `init`) in expandable details with structured parsing
 - **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using mistune
+- **Detail Levels & Compact Mode**: `--detail full|high|low|minimal|user-only` filters by verbosity and `--compact` merges repeated section headings — pairs well with `--format md` to feed past conversations back to an LLM for analysis or experience building
 - **Floating Navigation**: Always-available back-to-top button and filter controls
 - **CLI Interface**: Simple command-line tool using Click
 
@@ -81,6 +82,7 @@ This tool helps you answer questions like:
 - **"How can I share my Claude Code conversation with others?"**
 - **"What's the timeline of my project development?"**
 - **"How can I analyse patterns in my Claude Code usage?"**
+- **"How can I feed a past session back to an LLM for analysis or experience building?"**
 
 ## Usage
 
@@ -164,6 +166,28 @@ 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"
 ```
 
+### Feeding Past Conversations to an LLM
+
+The combination `--detail low --format md --compact` produces condensed Markdown suitable as context for an LLM to review or distill patterns from past work:
+
+```bash
+# Session → compact Markdown for LLM review
+claude-code-log transcript.jsonl --detail low --format md --compact -o session.md
+
+# Whole project history
+claude-code-log /path/to/project --detail low --format md --compact
+```
+
+`--detail` levels (smallest → largest output):
+
+- `user-only` — just user prompts and steering (useful as input to a downstream agent, e.g. building a requirements doc)
+- `minimal` — user + assistant text only
+- `low` — interaction-focused; keeps WebSearch, WebFetch, and Task (agent delegations) as key signals
+- `high` — detailed but cleaned; drops system/hook noise
+- `full` — everything (default)
+
+`--compact` merges consecutive same-type sections in Markdown so runs of assistant responses share one heading instead of repeating `### 🤖 Assistant:` for each.
+
 ## Project Hierarchy Output
 
 When processing all projects, the tool generates:
@@ -228,6 +252,7 @@ Markdown export provides a lightweight, portable alternative to HTML:
 - **Code Preservation**: Syntax highlighting hints via fenced code blocks
 - **Embedded Viewer**: TUI includes built-in Markdown viewer with table of contents
 - **Image Support**: Configurable image handling (placeholder, embedded base64, or referenced files)
+- **`--compact` Mode**: Merge consecutive same-type section headings — most useful with `--detail low` or `minimal` where tool stripping creates runs of Assistant or User sections
 
 ## Installation
 
@@ -256,6 +281,17 @@ uv run claude-code-log
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and architecture documentation.
 
+## Community Extensions
+
+Projects built on top of `claude-code-log`:
+
+- **[archive-session](https://github.com/lifeinchords/claude-code-skills#archive-session-skill--slash-command--optional-hook)** by [@lifeinchords](https://github.com/lifeinchords). Wraps the CLI as three integration surfaces:
+  - a Claude Code [Skill](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/skills/archive-session/SKILL.md)
+  - a Claude Code slash [Command](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/commands/archive-session.md) `/archive-session` for explicit in-chat invocation
+  - a Claude Code PreCompact [Hook](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/hooks/pre-compact-archive.sh) that auto-archives transcripts and subagent logs right before context compaction
+
+Cross-platform (macOS and Windows/MSYS).
+
 ## TODO
 
 - tutorial overlay

{claude_code_log-1.1.1 → claude_code_log-1.3.0}/README.md

@@ -42,6 +42,7 @@ uvx claude-code-log@latest --open-browser
 - **Rich Message Types**: Support for user/assistant messages, tool use/results, thinking content, images
 - **System Command Visibility**: Show system commands (like `init`) in expandable details with structured parsing
 - **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using mistune
+- **Detail Levels & Compact Mode**: `--detail full|high|low|minimal|user-only` filters by verbosity and `--compact` merges repeated section headings — pairs well with `--format md` to feed past conversations back to an LLM for analysis or experience building
 - **Floating Navigation**: Always-available back-to-top button and filter controls
 - **CLI Interface**: Simple command-line tool using Click
 
@@ -57,6 +58,7 @@ This tool helps you answer questions like:
 - **"How can I share my Claude Code conversation with others?"**
 - **"What's the timeline of my project development?"**
 - **"How can I analyse patterns in my Claude Code usage?"**
+- **"How can I feed a past session back to an LLM for analysis or experience building?"**
 
 ## Usage
 
@@ -140,6 +142,28 @@ 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"
 ```
 
+### Feeding Past Conversations to an LLM
+
+The combination `--detail low --format md --compact` produces condensed Markdown suitable as context for an LLM to review or distill patterns from past work:
+
+```bash
+# Session → compact Markdown for LLM review
+claude-code-log transcript.jsonl --detail low --format md --compact -o session.md
+
+# Whole project history
+claude-code-log /path/to/project --detail low --format md --compact
+```
+
+`--detail` levels (smallest → largest output):
+
+- `user-only` — just user prompts and steering (useful as input to a downstream agent, e.g. building a requirements doc)
+- `minimal` — user + assistant text only
+- `low` — interaction-focused; keeps WebSearch, WebFetch, and Task (agent delegations) as key signals
+- `high` — detailed but cleaned; drops system/hook noise
+- `full` — everything (default)
+
+`--compact` merges consecutive same-type sections in Markdown so runs of assistant responses share one heading instead of repeating `### 🤖 Assistant:` for each.
+
 ## Project Hierarchy Output
 
 When processing all projects, the tool generates:
@@ -204,6 +228,7 @@ Markdown export provides a lightweight, portable alternative to HTML:
 - **Code Preservation**: Syntax highlighting hints via fenced code blocks
 - **Embedded Viewer**: TUI includes built-in Markdown viewer with table of contents
 - **Image Support**: Configurable image handling (placeholder, embedded base64, or referenced files)
+- **`--compact` Mode**: Merge consecutive same-type section headings — most useful with `--detail low` or `minimal` where tool stripping creates runs of Assistant or User sections
 
 ## Installation
 
@@ -232,6 +257,17 @@ uv run claude-code-log
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and architecture documentation.
 
+## Community Extensions
+
+Projects built on top of `claude-code-log`:
+
+- **[archive-session](https://github.com/lifeinchords/claude-code-skills#archive-session-skill--slash-command--optional-hook)** by [@lifeinchords](https://github.com/lifeinchords). Wraps the CLI as three integration surfaces:
+  - a Claude Code [Skill](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/skills/archive-session/SKILL.md)
+  - a Claude Code slash [Command](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/commands/archive-session.md) `/archive-session` for explicit in-chat invocation
+  - a Claude Code PreCompact [Hook](https://github.com/lifeinchords/claude-code-skills/blob/main/.claude/hooks/pre-compact-archive.sh) that auto-archives transcripts and subagent logs right before context compaction
+
+Cross-platform (macOS and Windows/MSYS).
+
 ## TODO
 
 - tutorial overlay