docs: document unsupported source investigations - #1070

@coderabbitai please review this documentation-only PR.

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

No actionable comments were generated in the recent review. 🎉

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

#!/bin/bash
# Get PR info and changed files
gh pr view 1070 --repo ryoppippi/ccusage --json title,body,files,additions,deletions

echo "---FILE DIFF---"
gh pr diff 1070 --repo ryoppippi/ccusage

#!/bin/bash
# Get the PR branch name
gh pr view 1070 --repo ryoppippi/ccusage --json headRefName,headRepository

echo "---FETCH FILES VIA API---"
# Try fetching file contents from the PR
gh api repos/ryoppippi/ccusage/pulls/1070/files --jq '.[].filename'

echo "---source-support-qa.md---"
gh api "repos/ryoppippi/ccusage/contents/docs/guide/source-support-qa.md?ref=refs/pull/1070/head" --jq '.content' | base64 -d

echo "---config.ts patch---"
gh api repos/ryoppippi/ccusage/pulls/1070/files --jq '.[] | select(.filename == "docs/.vitepress/config.ts") | .patch'

echo "---all-reports.md patch---"
gh api repos/ryoppippi/ccusage/pulls/1070/files --jq '.[] | select(.filename == "docs/guide/all-reports.md") | .patch'

echo "---index.md patch---"
gh api repos/ryoppippi/ccusage/pulls/1070/files --jq '.[] | select(.filename == "docs/guide/index.md") | .patch'

#!/bin/bash
# Check frontmatter usage in existing guide pages
echo "=== index.md head ==="
head -20 docs/guide/index.md

echo "=== all-reports.md head ==="
head -10 docs/guide/all-reports.md

echo "=== Check sidebar group label for where the new link was inserted ==="
grep -n -A2 -B2 "OpenClaw\|Source Support\|sources\|Sources\|integrations" docs/.vitepress/config.ts | head -50

@ryoppippi The documentation is well-written and clearly structured. The use of VitePress :::details blocks to isolate each CLI investigation is a clean pattern, the framing is honest ("investigated but found X"), and the privacy advisory at the bottom of "Can These Be Added Later?" is a nice practical touch. No spelling, grammar, or broken-link issues found.

One minor suggestion:

Sidebar placement — The new entry sits inside the Data Sources sidebar group (alongside Claude Code, Gemini CLI, Kimi, OpenClaw, etc.), which groups supported source pages. A reader browsing that section for integration guides might find a "why some things are not supported" Q&A slightly out of place.

- { text: 'Source Support Q&A', link: '/guide/source-support-qa' },
  // inside "Data Sources" group

Two easy options:

1. Move it into its own sidebar group, e.g.:

   {
     text: 'Contributing',
     items: [
       { text: 'Source Support Q&A', link: '/guide/source-support-qa' },
     ],
   },

2. Keep it in "Data Sources" but adjust the label to something like 'Unsupported Sources' so the contrast is explicit in the nav.

That said, it's a small UX concern and the current placement is still findable — happy to defer to your judgment on it. The rest of the PR looks good to me.

Open in StackBlitz

npx https://pkg.pr.new/ryoppippi/ccusage@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-darwin-arm64@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-darwin-x64@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-linux-arm64@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-linux-x64@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-win32-arm64@1070

npx https://pkg.pr.new/ryoppippi/ccusage/@ccusage/ccusage-win32-x64@1070

commit: ab3b4d8

ccusage performance comparison

PR SHA: ab3b4d8fdabe
Base SHA: 7e200245fa60

This compares the Rust PR release binary against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: 7e200245fa60; PR package: ab3b4d8fdabe. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.

Artifact size

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

ccusage performance comparison

PR SHA: ab3b4d8fdabe
Base SHA: 7e200245fa60

This compares the PR package against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: 7e200245fa60; PR package: ab3b4d8fdabe. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.

Artifact size

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.