fix(cli): normalize since and until date bounds by Copilot · Pull Request #1144 · ryoppippi/ccusage

Copilot · 2026-05-24T22:53:37Z

ccusage daily --since 2026-04-22 was letting earlier rows through because filter comparisons used compact row dates (YYYYMMDD) against raw dashed bounds (YYYY-MM-DD). This caused incorrect lexicographic comparisons for same-year values.

Root cause
- Date filtering logic compares normalized row dates, but CLI/config bounds were stored unnormalized.
Change
- Normalize date bounds at input boundaries:
  - CLI parsing (--since, --until)
  - config application (since, until)
- This keeps existing filter paths unchanged while ensuring all comparisons are YYYYMMDD vs YYYYMMDD.
Scope
- rust/crates/ccusage/src/cli.rs
- rust/crates/ccusage/src/config.rs

Example

pub(crate) fn normalize_date_bound(value: &str) -> String {
    value.replace('-', "")
}

// applied when reading --since/--until and config since/until
shared.since = Some(normalize_date_bound(&raw_since));
shared.until = Some(normalize_date_bound(&raw_until));

This aligns dashed (YYYY-MM-DD) and compact (YYYYMMDD) bounds to the same filtering behavior.

Agent-Logs-Url: https://github.com/ryoppippi/ccusage/sessions/0823e42b-4ac8-4c26-8293-3db870c42528 Co-authored-by: ryoppippi <1560508+ryoppippi@users.noreply.github.com>

cloudflare-workers-and-pages · 2026-05-24T23:01:42Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	ccusage-guide	`5ed2499`	Commit Preview URL Branch Preview URL	May 25 2026, 06:40 PM

Agent-Logs-Url: https://github.com/ryoppippi/ccusage/sessions/0823e42b-4ac8-4c26-8293-3db870c42528 Co-authored-by: ryoppippi <1560508+ryoppippi@users.noreply.github.com>

Add a regression test for issue #1126 showing that dashed YYYY-MM-DD and compact YYYYMMDD --since bounds produce the same filtered daily rows. The test exercises the normalized CLI/config bound shape against the shared summary filter so pre-bound rows stay excluded.

pkg-pr-new · 2026-05-25T18:38:56Z

Open in StackBlitz

ccusage

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

@ccusage/ccusage-darwin-arm64

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

@ccusage/ccusage-darwin-x64

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

@ccusage/ccusage-linux-arm64

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

@ccusage/ccusage-linux-x64

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

@ccusage/ccusage-win32-arm64

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

@ccusage/ccusage-win32-x64

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

commit: 5ed2499

github-actions · 2026-05-25T18:40:55Z

ccusage performance comparison

PR SHA: cb4ecc69d578
Base SHA: 366eb0c4cc6c

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.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`366eb0c4cc6c`	614.1ms	448.2ms	33.2ms	3
PR pkg.pr.new	`cb4ecc69d578`	562.1ms	609.5ms	33.5ms	3

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: 366eb0c4cc6c; PR package: cb4ecc69d578. 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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	493.7ms	493.7ms	1.00x	268.83 MiB	252.08 MiB	0.94x	2.04 GiB/s	2.04 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	373.3ms	367.9ms	1.01x	61.58 MiB	59.45 MiB	0.97x	2.70 GiB/s	2.74 GiB/s

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.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	490.1ms	2.05 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	459.5ms	2.19 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	365.4ms	2.75 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	331.0ms	3.04 GiB/s	1

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	30.9ms	4.1ms	7.56x	43.61 MiB	2.83 MiB	0.06x	0.05 MiB/s	0.38 MiB/s
`claude session --offline --json`	30.5ms	4.1ms	7.51x	43.61 MiB	2.83 MiB	0.06x	0.05 MiB/s	0.38 MiB/s
`codex daily --offline --json`	30.8ms	3.9ms	7.97x	43.48 MiB	2.83 MiB	0.07x	0.03 MiB/s	0.22 MiB/s
`codex session --offline --json`	31.1ms	3.8ms	8.18x	43.61 MiB	2.83 MiB	0.06x	0.03 MiB/s	0.23 MiB/s

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	500.0ms	466.5ms	1.07x	263.33 MiB	259.70 MiB	0.99x	2.01 GiB/s	2.16 GiB/s
`codex --offline --json`	1.01 GiB	359.9ms	328.6ms	1.10x	65.08 MiB	57.45 MiB	0.88x	2.80 GiB/s	3.06 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.25 KiB	+0.00 KiB	1.00x
installed native package binary	3225.49 KiB	3225.49 KiB	+0.00 KiB	1.00x

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

github-actions · 2026-05-25T18:41:03Z

ccusage performance comparison

PR SHA: cb4ecc69d578
Base SHA: 366eb0c4cc6c

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.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`366eb0c4cc6c`	1.146s	635.4ms	31.9ms	3
PR pkg.pr.new	`cb4ecc69d578`	798.9ms	546.5ms	31.0ms	3

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: 366eb0c4cc6c; PR package: cb4ecc69d578. 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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	475.4ms	498.4ms	0.95x	245.33 MiB	261.33 MiB	1.07x	2.12 GiB/s	2.02 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	359.8ms	359.2ms	1.00x	52.33 MiB	55.08 MiB	1.05x	2.80 GiB/s	2.80 GiB/s

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.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	477.9ms	2.11 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	453.1ms	2.22 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	352.7ms	2.85 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	325.9ms	3.09 GiB/s	1

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	29.2ms	29.7ms	0.98x	43.61 MiB	43.61 MiB	1.00x	0.05 MiB/s	0.05 MiB/s
`claude session --offline --json`	29.2ms	29.1ms	1.01x	43.61 MiB	43.48 MiB	1.00x	0.05 MiB/s	0.05 MiB/s
`codex daily --offline --json`	29.1ms	29.1ms	1.00x	43.73 MiB	43.48 MiB	0.99x	0.03 MiB/s	0.03 MiB/s
`codex session --offline --json`	29.1ms	28.7ms	1.01x	43.48 MiB	43.61 MiB	1.00x	0.03 MiB/s	0.03 MiB/s

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	475.6ms	473.2ms	1.00x	253.45 MiB	256.45 MiB	1.01x	2.12 GiB/s	2.13 GiB/s
`codex --offline --json`	1.01 GiB	353.2ms	348.5ms	1.01x	54.08 MiB	62.95 MiB	1.16x	2.85 GiB/s	2.89 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.25 KiB	+0.00 KiB	1.00x
installed native package binary	3225.49 KiB	3225.49 KiB	+0.00 KiB	1.00x

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

github-actions · 2026-05-25T18:55:52Z

ccusage performance comparison

PR SHA: 5ed2499a3581
Base SHA: 366eb0c4cc6c

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.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`366eb0c4cc6c`	700.2ms	453.1ms	33.9ms	3
PR pkg.pr.new	`5ed2499a3581`	538.0ms	628.2ms	34.8ms	3

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: 366eb0c4cc6c; PR package: 5ed2499a3581. 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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	499.0ms	491.9ms	1.01x	247.33 MiB	267.70 MiB	1.08x	2.02 GiB/s	2.05 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	365.3ms	363.5ms	1.01x	59.95 MiB	53.33 MiB	0.89x	2.76 GiB/s	2.77 GiB/s

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.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	493.3ms	2.04 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	464.5ms	2.17 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	361.6ms	2.78 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	335.9ms	3.00 GiB/s	1

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	31.1ms	4.2ms	7.42x	43.48 MiB	2.83 MiB	0.07x	0.05 MiB/s	0.37 MiB/s
`claude session --offline --json`	31.2ms	4.2ms	7.39x	43.61 MiB	2.83 MiB	0.06x	0.05 MiB/s	0.37 MiB/s
`codex daily --offline --json`	30.7ms	3.9ms	7.93x	43.61 MiB	2.83 MiB	0.06x	0.03 MiB/s	0.22 MiB/s
`codex session --offline --json`	30.5ms	3.8ms	7.97x	43.48 MiB	2.83 MiB	0.07x	0.03 MiB/s	0.22 MiB/s

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	490.6ms	457.5ms	1.07x	272.08 MiB	267.95 MiB	0.98x	2.05 GiB/s	2.20 GiB/s
`codex --offline --json`	1.01 GiB	362.6ms	333.0ms	1.09x	66.20 MiB	59.95 MiB	0.91x	2.78 GiB/s	3.02 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.25 KiB	+0.00 KiB	1.00x
installed native package binary	3225.49 KiB	3289.49 KiB	+64.00 KiB	0.98x

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

github-actions · 2026-05-25T18:56:26Z

ccusage performance comparison

PR SHA: 5ed2499a3581
Base SHA: 366eb0c4cc6c

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.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`366eb0c4cc6c`	762.9ms	554.6ms	35.4ms	3
PR pkg.pr.new	`5ed2499a3581`	379.7ms	420.2ms	34.0ms	3

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: 366eb0c4cc6c; PR package: 5ed2499a3581. 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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	517.4ms	507.9ms	1.02x	251.33 MiB	248.20 MiB	0.99x	1.95 GiB/s	1.98 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	380.3ms	376.7ms	1.01x	62.58 MiB	66.95 MiB	1.07x	2.65 GiB/s	2.67 GiB/s

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.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	493.0ms	2.04 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	465.9ms	2.16 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	361.5ms	2.78 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	336.7ms	2.99 GiB/s	1

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	31.6ms	31.7ms	1.00x	43.73 MiB	43.48 MiB	0.99x	0.05 MiB/s	0.05 MiB/s
`claude session --offline --json`	31.6ms	31.7ms	1.00x	43.48 MiB	43.48 MiB	1.00x	0.05 MiB/s	0.05 MiB/s
`codex daily --offline --json`	31.5ms	30.9ms	1.02x	43.61 MiB	43.61 MiB	1.00x	0.03 MiB/s	0.03 MiB/s
`codex session --offline --json`	31.2ms	31.6ms	0.99x	43.48 MiB	43.61 MiB	1.00x	0.03 MiB/s	0.03 MiB/s

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.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	491.9ms	489.6ms	1.00x	253.20 MiB	257.33 MiB	1.02x	2.05 GiB/s	2.06 GiB/s
`codex --offline --json`	1.01 GiB	364.0ms	363.1ms	1.00x	57.83 MiB	59.70 MiB	1.03x	2.77 GiB/s	2.77 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.25 KiB	+0.00 KiB	1.00x
installed native package binary	3225.49 KiB	3289.49 KiB	+64.00 KiB	0.98x

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

Initial plan

d3d90c8

Copilot AI assigned Copilot and ryoppippi May 24, 2026

Copilot started work on behalf of ryoppippi May 24, 2026 22:53 View session

Copilot AI linked an issue May 24, 2026 that may be closed by this pull request

Bug: daily --since ignores dashed YYYY-MM-DD bounds #1126

Closed

fix: normalize dashed since/until date bounds before filtering

c6f8864

Agent-Logs-Url: https://github.com/ryoppippi/ccusage/sessions/0823e42b-4ac8-4c26-8293-3db870c42528 Co-authored-by: ryoppippi <1560508+ryoppippi@users.noreply.github.com>

refactor: keep date-bound normalization at CLI/config entry points

cb4ecc6

Agent-Logs-Url: https://github.com/ryoppippi/ccusage/sessions/0823e42b-4ac8-4c26-8293-3db870c42528 Co-authored-by: ryoppippi <1560508+ryoppippi@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix daily command to respect dashed YYYY-MM-DD bounds~~ Normalize --since/--until date bounds so dashed and compact formats filter identically May 24, 2026

Copilot finished work on behalf of ryoppippi May 24, 2026 23:06

Copilot AI requested a review from ryoppippi May 24, 2026 23:06

ryoppippi marked this pull request as ready for review May 24, 2026 23:34

ryoppippi changed the title ~~Normalize --since/--until date bounds so dashed and compact formats filter identically~~ fix(cli): normalize since and until date bounds May 25, 2026

ryoppippi merged commit 35e0090 into main May 25, 2026
36 checks passed

ryoppippi deleted the copilot/fix-daily-since-date-bound branch May 25, 2026 18:57

BrewTestBot mentioned this pull request May 25, 2026

ccusage 20.0.5 Homebrew/homebrew-core#284687

Merged

zcutlip mentioned this pull request May 26, 2026

fix: skip compact auto-detect when stdout is not a TTY #1111

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(cli): normalize since and until date bounds#1144

fix(cli): normalize since and until date bounds#1144
ryoppippi merged 4 commits into
mainfrom
copilot/fix-daily-since-date-bound

Copilot AI commented May 24, 2026 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented May 24, 2026 •

edited

Loading

Uh oh!

pkg-pr-new Bot commented May 25, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

Copilot AI commented May 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cloudflare-workers-and-pages Bot commented May 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

pkg-pr-new Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented May 24, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented May 24, 2026 •

edited

Loading

pkg-pr-new Bot commented May 25, 2026 •

edited

Loading