claude-code-log 1.2.0__tar.gz → 1.4.0__tar.gz

{claude_code_log-1.2.0 → claude_code_log-1.4.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.2.0 → claude_code_log-1.4.0}/.github/workflows/ci.yml

@@ -20,6 +20,12 @@ jobs:
 
     steps:
     - uses: actions/checkout@v4
+      with:
+        # Full history so test/test_commit_linkifier.py's
+        # TestIntegrationLocalRepo can resolve SHAs older than the
+        # current tip (`git branch -r --contains` reads local refs
+        # only and needs the commits in the object DB).
+        fetch-depth: 0
 
     - name: Install uv
       uses: astral-sh/setup-uv@v4
@@ -33,13 +39,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.4.0/.github/workflows/docs.yml

@@ -0,0 +1,68 @@
+name: Docs
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+# Allow the deploy job to publish to GitHub Pages.
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Avoid overlapping deploys; let an in-progress run finish.
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+env:
+  # Silence the Material-for-MkDocs vendor banner about a future MkDocs 2.0.
+  DISABLE_MKDOCS_2_WARNING: "true"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v8.2.0
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install 3.12
+
+      - name: Install docs dependencies
+        run: uv sync --group docs
+
+      - name: Build site (strict)
+        run: uv run mkdocs build --strict
+
+      - name: Upload site as artifact (downloadable preview)
+        uses: actions/upload-artifact@v7
+        with:
+          name: site-preview
+          path: site
+          retention-days: 14
+
+      - name: Upload Pages artifact
+        if: github.ref == 'refs/heads/main'
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    # Only publish from main; PRs just run the strict build above.
+    if: github.ref == 'refs/heads/main'
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

{claude_code_log-1.2.0 → claude_code_log-1.4.0}/.gitignore

@@ -147,6 +147,8 @@ venv.bak/
 
 # mkdocs documentation
 /site
+# Locally-generated TUI screenshots (regenerated at build time by gen-files)
+docs/assets/tui/
 
 # mypy
 .mypy_cache/
@@ -187,11 +189,10 @@ test/test_data/*.html
 .local.code-workspace
 local.ps1
 
-# Generated documentation examples (uploaded to GitHub releases instead)
-docs/claude-code-log-transcript.html
-docs/cache/
 
 # Integration test data - exclude generated cache/HTML, keep JSONL files
 test/test_data/real_projects/*/cache/
 test/test_data/real_projects/*/*.html
 test/test_data/real_projects/index.html
+# SQLite cache the CLI drops into a projects dir when run against test data
+claude-code-log-cache.db

{claude_code_log-1.2.0 → claude_code_log-1.4.0}/CHANGELOG.md

@@ -6,6 +6,87 @@ 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.4.0] - 2026-06-03
+
+### Changed
+
+- **Fix sed**
+- **Add MkDocs documentation site with live TUI reference (#197)**
+- **Relax Textual constraint from `==` to `>=` (#196)**
+- **Add `--version` flag to the CLI (#195)**
+- **Fix AskUserQuestion result rendering + highlight chosen options (#180) (#189)**
+- **Derive render_session_id from the SessionTree, not a loop variable (#190)**
+- **Fix collapsible body overlapping preceding content in tool cards (#153) (#187)**
+- **Extract compute_session_data + compute_project_aggregates (C9b) (#188)**
+- **Add C9a characterization tests for session-scan call sites (#186)**
+- **Route converter summary + ai-title extraction through shared helpers (#185)**
+- **status: Wave B fully merged; Wave C kickoff (C8/C9a/C9b stacked, C10 dropped, decisions locked)**
+- **Compute branch preview once from the DAG-line (#184)**
+- **status: #184 fully validated (CI 11/11, CodeRabbit clean) — ready to merge**
+- **docs: keep simplification status note self-contained to project scope**
+- **status: correct #184 state; move GitHub CI/CodeRabbit ops to github guideline**
+- **status: reverse-order stacked-PR lift recipe CONFIRMED on #184**
+- **Factor session-header construction out of _render_messages (#183)**
+- **status: #183/#184 rebased + CodeRabbit forced (#183 clean, #184 2 doc fixes); record @coderabbitai + reverse-order workarounds**
+- **Dedup requestId tokens in pagination cache-miss fallback (#182)**
+- **status: Wave B track complete — opp 7 PR #184 up, all monk-approved; add merge sequence**
+- **status: note stacked-PR CI/CodeRabbit defers to merge-time**
+- **status: opp 1 green (#182, awaiting merge); opp 6 #183 in review; opp 7 in progress**
+- **status: opp 1 -> PR #182 (in review); opp 6 in progress**
+- **Add live-status section to simplification plan**
+- **Add converter/renderer simplification plan**
+- **Move detail-visibility predicate onto MessageContent (#181)**
+- **Sync rendering-architecture.md §5 with the current pipeline (#178)**
+- **Extract inline junction-forward-link block into a named pass (#177)**
+- **Co-locate the away-summary detail rule on AwaySummaryMessage (#176)**
+- **Remove vestigial progress-chain parent repair (#175)**
+- **plugins: dev-docs gaps + public helper API + ToolResult example (Phase 2) (#173)**
+- **Implement unified plugin system from RFC #166 (#169)**
+- **Render Read tool results with pygments via structured payload (closes #170) (#172)**
+- **work/: triage against shipped main (#171)**
+- **Always regenerate projects index so variant-flag toggles refresh links (#168)**
+- **RFC: plugin system (unified message-transformer mechanism) (#166)**
+- **Per-message timestamps in Markdown output (#160) (#165)**
+- **Support non-GitHub forges via static map + `--git-link` fallback (#156) (#164)**
+- **Obsidian-friendly output: --output dir + --expand-paths + --filter-path (#151) (#155)**
+- **Linkify commit SHAs in rendered Markdown + HTML — closes #156 (#161)**
+- **CSS clean-ups (issue #153) (#163)**
+- **Cross-link TaskOutput / TaskUpdate headers back to their spawn (#154) (#158)**
+
+
+## [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

{claude_code_log-1.2.0 → claude_code_log-1.4.0}/CLAUDE.md

@@ -51,26 +51,26 @@ See @CONTRIBUTING.md for detailed development setup, testing, architecture, and
 
 ### 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
 
@@ -95,7 +95,37 @@ 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
+- [dev-docs/plugins.md](dev-docs/plugins.md) - Plugin system reference + author guide
+
+User-facing docs live in [docs/](docs/); plans and TODOs live in [work/](work/).
+
+A documentation site (MkDocs + Material) is published to GitHub Pages from
+`docs/` + `mkdocs.yml`. The CLI reference is rendered live from Click, and the
+TUI reference (keybindings + screenshots) is auto-generated at build time. See
+the "Documentation Site" section of @CONTRIBUTING.md. Preview with
+`just docs-serve`; strict build with `just docs-build`.
+
+### 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.2.0 → claude_code_log-1.4.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,64 @@ 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.
+
+## Documentation Site
+
+The project publishes a documentation site to GitHub Pages, built with
+[MkDocs](https://www.mkdocs.org/) and the
+[Material](https://squidfunk.github.io/mkdocs-material/) theme. The site
+configuration is `mkdocs.yml`; pages live under `docs/`.
+
+```bash
+# Install docs dependencies
+uv sync --group docs
+
+# Live-reload preview at http://127.0.0.1:8000
+just docs-serve
+
+# Strict build (fails on broken links/nav — same as CI)
+just docs-build
+```
+
+Key points:
+
+- **CLI reference** (`docs/reference/cli.md`) is rendered live from the Click
+  command via the `mkdocs-click` plugin — no manual upkeep.
+- **TUI reference** (`reference/tui.md`) is generated at build time by
+  `docs/gen_pages.py` (a `mkdocs-gen-files` script): it introspects the Textual
+  `BINDINGS` for the keybindings tables (`scripts/generate_tui_docs.py`) and
+  captures SVG screenshots of the running TUI
+  (`scripts/generate_tui_screenshots.py`). Both scripts are runnable standalone.
+- **Example output** (`example.md` + `examples/transcript.html`) is rendered at
+  build time from a bundled sample project
+  (`scripts/generate_example_output.py`, also `just example`) — no private data
+  or release asset involved. Generation is fault-tolerant so a render hiccup
+  can't block the build.
+- **Development** section surfaces `dev-docs/` (symlinked as `docs/development`).
+  `CONTRIBUTING.md` and `CHANGELOG.md` are symlinked in as `docs/contributing.md`
+  and `docs/changelog.md`. A build hook (`docs/hooks.py`) rewrites links to repo
+  source files (e.g. `../claude_code_log/cli.py`) into GitHub URLs so the strict
+  build stays green.
+- Deployment is automated by `.github/workflows/docs.yml`: PRs run a strict
+  build; pushes to `main` deploy to Pages. The repo's **Settings → Pages →
+  Source** must be set to **GitHub Actions** (one-time).
+
 ## 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.2.0 → claude_code_log-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-log
-Version: 1.2.0
+Version: 1.4.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
@@ -18,7 +18,7 @@ Requires-Dist: mistune>=3.1.4
 Requires-Dist: packaging>=25.0
 Requires-Dist: pydantic>=2.12.0
 Requires-Dist: pygments>=2.19.2
-Requires-Dist: textual==6.5.0
+Requires-Dist: textual>=6.5.0
 Requires-Dist: toml>=0.10.2
 Description-Content-Type: text/markdown
 
@@ -40,7 +40,7 @@ TUI demo:
 
 This tool generates clean, minimalist HTML pages showing user prompts and assistant responses chronologically. It's designed to create a readable log of your Claude Code interactions with support for both individual files and entire project hierarchies.
 
-📄 **[View Example HTML Output](https://github.com/daaain/claude-code-log/releases/latest/download/claude-code-log-transcript.html)** - Download a real example generated from this project's development (large file, ~100 MB)
+📄 **[View Example HTML Output](https://daaain.github.io/claude-code-log/example/)** - A real example generated from a sample of this project's development, regenerated on every docs build
 
 ## Quickstart
 
@@ -66,7 +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` 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
+- **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
 
@@ -180,6 +180,7 @@ 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
@@ -187,6 +188,21 @@ claude-code-log /path/to/project --detail low --format md --compact
 
 `--compact` merges consecutive same-type sections in Markdown so runs of assistant responses share one heading instead of repeating `### 🤖 Assistant:` for each.
 
+### Linking Commit SHAs
+
+Plain `7c2e6f6`-shaped tokens in transcript prose get turned into clickable commit links when the SHA is reachable from a local remote-tracking branch. **github.com**, **gitlab.com**, and **bitbucket.org** work out of the box. For self-hosted forges (in-house GitLab, Gitea, Forgejo, …), supply a URL template via `--git-link`:
+
+```bash
+# Self-hosted GitLab
+claude-code-log /path/to/transcript --git-link 'https://{host}/{path}/-/commit/{sha}'
+
+# Same thing via env var (useful for TUI / repeated invocations)
+export CLAUDE_CODE_LOG_GIT_LINK='https://{host}/{path}/-/commit/{sha}'
+claude-code-log --tui
+```
+
+Placeholders: `{host}`, `{path}`, `{sha}`. The template fires only when the static map doesn't already know the host, so a mix of GitHub repos + self-hosted GitLab gets correct links from both. SHAs not reachable from any local remote-tracking ref render as plain text — local-only work-in-progress commits never produce broken links.
+
 ## Project Hierarchy Output
 
 When processing all projects, the tool generates:
@@ -280,6 +296,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.2.0 → claude_code_log-1.4.0}/README.md

@@ -16,7 +16,7 @@ TUI demo:
 
 This tool generates clean, minimalist HTML pages showing user prompts and assistant responses chronologically. It's designed to create a readable log of your Claude Code interactions with support for both individual files and entire project hierarchies.
 
-📄 **[View Example HTML Output](https://github.com/daaain/claude-code-log/releases/latest/download/claude-code-log-transcript.html)** - Download a real example generated from this project's development (large file, ~100 MB)
+📄 **[View Example HTML Output](https://daaain.github.io/claude-code-log/example/)** - A real example generated from a sample of this project's development, regenerated on every docs build
 
 ## Quickstart
 
@@ -42,7 +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` 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
+- **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
 
@@ -156,6 +156,7 @@ 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
@@ -163,6 +164,21 @@ claude-code-log /path/to/project --detail low --format md --compact
 
 `--compact` merges consecutive same-type sections in Markdown so runs of assistant responses share one heading instead of repeating `### 🤖 Assistant:` for each.
 
+### Linking Commit SHAs
+
+Plain `7c2e6f6`-shaped tokens in transcript prose get turned into clickable commit links when the SHA is reachable from a local remote-tracking branch. **github.com**, **gitlab.com**, and **bitbucket.org** work out of the box. For self-hosted forges (in-house GitLab, Gitea, Forgejo, …), supply a URL template via `--git-link`:
+
+```bash
+# Self-hosted GitLab
+claude-code-log /path/to/transcript --git-link 'https://{host}/{path}/-/commit/{sha}'
+
+# Same thing via env var (useful for TUI / repeated invocations)
+export CLAUDE_CODE_LOG_GIT_LINK='https://{host}/{path}/-/commit/{sha}'
+claude-code-log --tui
+```
+
+Placeholders: `{host}`, `{path}`, `{sha}`. The template fires only when the static map doesn't already know the host, so a mix of GitHub repos + self-hosted GitLab gets correct links from both. SHAs not reachable from any local remote-tracking ref render as plain text — local-only work-in-progress commits never produce broken links.
+
 ## Project Hierarchy Output
 
 When processing all projects, the tool generates:
@@ -256,6 +272,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