feat(statusline): add cost data persistence with statusline and max modes - #577

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

src/_cost-storage.ts (4)

150-169: Guard getLatestCost() against non-Result input (symptom of earlier bug) and keep strict booleans

Once loadCostData() is fixed, this function is fine. Adding an explicit success guard improves robustness and satisfies strict-boolean ESLint in some setups.

Apply this diff:

 export async function getLatestCost(sessionId: string): Promise<Result<CostEntry | null, Error>> {
 	const loadResult = await loadCostData(sessionId);

-	if (Result.isFailure(loadResult)) {
+	if (Result.isFailure(loadResult)) {
 		logger.debug(`Failed to load cost data for session ${sessionId}: ${loadResult.error.message}`);
 		return Result.succeed(null); // Return null instead of propagating error
 	}
 
-	const data = loadResult.value;
-	if (data.costs.length === 0) {
+	const data = loadResult.value;
+	if (data.costs.length === 0) {
 		return Result.succeed(null);
 	}

---

1-8: Strengthen schema and align style: enforce ISO timestamp + double quotes

• timestamp should use the existing branded ISO timestamp schema for validation consistency.
• Coding guideline: double quotes in TS.

Apply this diff:

-import { mkdirSync } from 'node:fs';
-import { readFile, writeFile } from 'node:fs/promises';
-import { join } from 'node:path';
-import { Result } from '@praha/byethrow';
-import { z } from 'zod';
-import { DEFAULT_CLAUDE_CONFIG_PATH } from './_consts.ts';
-import { logger } from './logger.ts';
+import { mkdirSync } from "node:fs";
+import { readFile, writeFile, rename } from "node:fs/promises";
+import { join } from "node:path";
+import { Result } from "@praha/byethrow";
+import { z } from "zod";
+import { DEFAULT_CLAUDE_CONFIG_PATH } from "./_consts.ts";
+import { logger } from "./logger.ts";
+import { isoTimestampSchema } from "./_types.ts";

-const costEntrySchema = z.object({
-	timestamp: z.string(),
+const costEntrySchema = z.object({
+	timestamp: isoTimestampSchema,
 	totalCostUsd: z.number(),
-	source: z.literal('statusline'),
+	source: z.literal("statusline"),
 });

Also applies to: 12-16

---

188-204: Tests: add a happy-path save→load→getLatest roundtrip and a malformed JSON case

Non-blocking, but would prevent regressions and validate atomic writes. Consider adding:

• write a cost entry, then load and assert it’s the latest
• create a malformed JSON file and assert loadCostData() returns failure and getLatestCost() returns null

I can draft the test cases using fs-fixture to isolate ~/.config paths. Want me to follow your test style and open a PR task?

---

111-116: Concurrency: consider file-level atomic append semantics

saveCostData() is read-modify-write. With concurrent writers, last write wins and intermediate appends can be lost. The atomic rename mitigates partial writes but not lost updates. If this becomes an issue, consider:

• advisory lock file in the same dir, or
• use a log-structured file (append-only) and merge on read

I can provide a minimal lock-file helper using fs.open(O_CREAT|O_EXCL) if you’d like.

src/_shared-args.ts (1)

45-48: Nit: switch to double quotes to satisfy TS style guide

Matches project rule “Use double quotes” for TS files.

-			'Cost calculation mode: auto (costUSD → calculate), calculate (tokens only), display (costUSD only), statusline (statusline → costUSD → calculate), max (MAX of all sources)',
+			"Cost calculation mode: auto (costUSD → calculate), calculate (tokens only), display (costUSD only), statusline (statusline → costUSD → calculate), max (MAX of all sources)",

src/commands/statusline.ts (1)

13-13: Nit: use double quotes for local import

Aligns with repository TS style.

-import { saveCostData } from '../_cost-storage.ts';
+import { saveCostData } from "../_cost-storage.ts";

docs/guide/statusline.md (1)

256-336: Docs polish: remove tabs, fix “heading with trailing colon” lint, and one minor style tune

• Replace hard tabs with spaces across this section (MD010).
• Replace bold pseudo-headings that end with a colon with actual headings or remove the trailing colon (MD026).
• “Integration with Other Commands” is already a heading; keep consistent level across the sub-sections.

Apply these focused edits; then run markdownlint --fix:

-## Cost Data Persistence
+## Cost Data Persistence

-	This stored cost data is then used by other commands when you specify:
+This stored cost data is then used by other commands when you specify:

-### Storage Details
+### Storage Details

-**File structure:**
+#### File structure

-**Storage location:**
+#### Storage location

-**Privacy:**
+#### Privacy

-### Integration with Other Commands
+### Integration with Other Commands

I can submit a follow-up patch that systematically converts the remaining tabs in this file to spaces if you prefer.

docs/guide/cost-modes.md (4)

122-156: Clarify that saved statusline costs are per-session totals to avoid double counting in aggregated views

The text implies saved costs can be applied per entry. Saved costs produced by the statusline are per-session totals. Please add one sentence calling this out explicitly and how they are attributed in daily/weekly/monthly views (e.g., allocated to the session’s last activity day or proportionally by tokens). This avoids users assuming a per-entry cost, which would overcount.

---

166-191: Explain “max” mode scope regarding session-level saved costs

Because saved statusline costs are session-level, “max” should clarify that the comparison mixes session-level and entry-level sources. Add a note that for aggregated views, the session-level cost is applied once per session (and how it’s attributed) to prevent confusion.

---

390-429: Document the XDG override for storage path in Setup

You mention XDG-style paths; consider adding that setting XDG_CONFIG_HOME (or the repo’s env override if available) will redirect the storage location. This helps CI/tests and users who don’t want writes to their real home directory.

---

372-388: Performance note: call out caching of saved-cost lookups

Add a tip that saved-cost reads are cached per session during a single run to keep statusline/max at “Moderate.” Without caching, reading the same file per message can degrade to “Slow.”

Would you like me to contribute a short “performance tips” subsection with recommended caching patterns?

src/data-loader.ts (3)

166-176: Naming/behavior mismatch: usage of “display” mode as control path

You special-case mode === 'display' to skip creating PricingFetcher. That’s correct. Consider passing a boolean (“needsPricing”) derived from mode to avoid accidental fetcher usage in future branches, especially with new modes.

---

956-1005: Micro-optimization: avoid calculating model/date/project repeatedly in the tight loop

In the main file-processing loop you parse per-line JSON and immediately call calculateCostForEntry. If/when you move saved-cost logic out of per-entry, you can precompute a per-session cost map to reduce repeated calls and simplify inner loops.

I can provide a targeted refactor plan that builds a session→savedCost map once and uses it across loaders.

---

1567-1621: Blocks view inherits the same per-entry saved-cost duplication risk

loadSessionBlockData calls calculateCostForEntry per entry. Once you move saved-cost application to aggregation, adjust blocks so that the session’s saved total is applied once per block-set (or documented attribution), not per entry.

Would you like me to prototype the attribution rule for blocks (e.g., assign to the block containing last entry, or proportionally by token counts per block)?

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

src/_shared-args.ts (1)

41-48: LGTM: updated mode description aligns with new modes (statusline, max)

Accurately reflects the five-mode flow and default. No further changes needed.

src/commands/statusline.ts (1)

112-118: LGTM: new --save-cost flag is well-scoped and opt-out via --no-save-cost

Defaults and kebab-casing match the rest of the CLI. Good.

src/_types.ts (2)

102-110: LGTM: CostModes extended with 'statusline' and 'max' and documented fallback semantics

Type surface and docs align with the new behavior in data-loader and statusline command.

---

148-168: Schema note: statuslineHookJsonSchema matches usage in statusline; optional cost payload is correctly modeled

No changes required. This ensures hookData.cost?.total_cost_usd is type-safe where accessed.

config-schema.json (7)

32-42: Enums and descriptions updated for new modes — looks good

The additions of “statusline” and “max” and the updated descriptions in defaults are consistent with the code paths.

---

138-148: Daily command mode enum/descriptions are consistent

No issues found; aligns with runtime behavior.

---

356-366: Weekly command mode updates are consistent

Enums/descriptions match defaults and code.

---

472-482: Session command mode updates are consistent

Enums/descriptions OK. Ensure session-level attribution of saved costs is clarified in docs and implemented in code (see data-loader comments).

---

578-588: Blocks command mode updates are consistent

Enums/descriptions OK. Blocks attribution for saved costs needs the same design treatment as sessions/daily (see data-loader comments).

---

686-696: MCP command mode updates are consistent

Enums/descriptions OK.

---

762-767: New statusline.saveCost flag — verify defaults and CLI parity

Default true matches the docs. Please confirm the flag name and default align with src/commands/statusline.ts (i.e., --save-cost / --no-save-cost).

src/_cost-storage.ts (1)

77-124: Guard against concurrent writers (lost updates) with a per-file lock

Concurrent statusline processes can interleave read-modify-write and drop entries. Add a simple lock (e.g., proper-lockfile) around the entire save section so only one writer operates at a time per session file. This prevents lost cost entries.

I can add proper-lockfile usage (acquire before load/append/write, finally release) or a simple advisory .lock file strategy—your call.

src/commands/statusline.ts (1)

469-481: Fix lint and type issues; use non-blocking async IIFE and explicit boolean check

Current .then() chain and truthy check trip strict-boolean and unsafe-call rules. Replace with an async IIFE, keep it fire-and-forget with void, and compare saveCost === true explicitly.

-			// Save Claude Code cost data if available and enabled
-			if (ctx.values.saveCost && hookData.cost?.total_cost_usd != null) {
-				// Save cost asynchronously to avoid blocking statusline output
-				saveCostData(sessionId, hookData.cost.total_cost_usd)
-					.then((result) => {
-						if (Result.isFailure(result)) {
-							logger.debug(`Failed to save cost data: ${result.error.message}`);
-						}
-					})
-					.catch((error: unknown) => {
-						logger.debug(`Error saving cost data: ${error instanceof Error ? error.message : String(error)}`);
-					});
-			}
+			// Save Claude Code cost data if available and enabled (non-blocking)
+			if (ctx.values.saveCost === true && hookData.cost?.total_cost_usd != null) {
+				void (async () => {
+					const result = await saveCostData(sessionId, hookData.cost!.total_cost_usd);
+					if (Result.isFailure(result)) {
+						logger.debug(`Failed to save cost data: ${result.error.message}`);
+					}
+				})().catch((error: unknown) => {
+					logger.debug(`Error saving cost data: ${error instanceof Error ? error.message : String(error)}`);
+				});
+			}

src/data-loader.ts (1)

779-805: “max” mode suffers the same multiplication; apply the same caching now and plan session-level fix

As above, saved costs should be considered once per session, not per entry. Apply the caching guard in the interim.

 	if (mode === 'max') {
 		// Max mode: MAX(saved statusline costs, pre-calculated costUSD, token-based calculation)
 		const costs: number[] = [];
 
 		// Get saved statusline cost
 		if (data.sessionId != null) {
-			const savedCost = await getSavedCost(data.sessionId);
-			if (savedCost != null) {
-				costs.push(savedCost);
-			}
+			const sid = data.sessionId;
+			let savedCost = savedCostCache.get(sid);
+			if (savedCost === undefined && !savedCostCache.has(sid)) {
+				savedCost = await Result.unwrap(
+					Result.try({
+						try: () => getSavedCost(sid),
+						catch: (e: unknown) => {
+							logger.debug(`getSavedCost failed for ${sid}: ${String(e)}`);
+							return e as Error;
+						},
+					})(),
+					undefined,
+				);
+				savedCostCache.set(sid, savedCost);
+			}
+			if (savedCost != null) {
+				costs.push(savedCost);
+			}
 		}

Follow-up (recommended): move saved-cost logic to loadSessionData and daily/weekly/monthly aggregations.

src/_cost-storage.ts (2)

131-147: Differentiate ENOENT vs. malformed JSON; avoid clobbering corrupt files silently

Right now, saveCostData will recreate the file on any load failure—including schema errors—overwriting possibly recoverable data. Consider:

• Treat ENOENT as “no data” (OK to create).
• For parse/validation errors, return a failure Result and don’t overwrite; log a clear message and optionally write a .bak before attempting repair.

I can wire a small helper to classify errors (code === 'ENOENT') and propagate others.

---

1-8: Style: switch to double quotes to align with repo TypeScript guidelines

Imports and string literals use single quotes here. The codebase guideline prefers double quotes for .ts files. Consider running ESLint/formatter or updating literals in this file.

src/data-loader.ts (1)

36-37: Direct dependency on storage API is fine; consider memoizing saved costs to reduce I/O

Import is correct. Later calls to getSavedCost happen per entry—add a small per-run cache to avoid repeated disk reads for the same session.

I propose a tiny Map<string, number | undefined> at module scope; see diffs below in the mode branches.

docs/guide/statusline.md (1)

256-337: Add language to fenced code block for path snippet; minor grammar polish

Markdownlint prefers a language. Use “text” for file paths; also ensure “Claude Code” spelling consistency.

-```
+```text
 ~/.config/claude/ccusage/costs/{sessionId}.json

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used**: CodeRabbit UI

**Review profile**: CHILL

**Plan**: Pro

**💡 Knowledge Base configuration:**

- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 4792c2cfae56fc99a5c67a23ed897713a74a8e20 and c7a584958f63f8e826f2a3b5d978454c816e251c.

</details>

<details>
<summary>📒 Files selected for processing (5)</summary>

* `config-schema.json` (8 hunks)
* `docs/guide/statusline.md` (1 hunks)
* `src/_cost-storage.ts` (1 hunks)
* `src/commands/statusline.ts` (3 hunks)
* `src/data-loader.ts` (3 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>📓 Path-based instructions (3)</summary>

<details>
<summary>**/*.{ts,tsx}</summary>


**📄 CodeRabbit inference engine (CLAUDE.md)**

> `**/*.{ts,tsx}`: Use tab indentation and double quotes; format with ESLint
> Do not use console.log; use logger.ts instead (only allow console.log when explicitly eslint-disabled)
> Use .ts extensions for local file imports (e.g., import { foo } from "./utils.ts")
> Prefer @praha/byethrow Result type over traditional try-catch; use Result.try(), Result.isFailure()/isSuccess() and early returns; reserve try-catch for complex file I/O or legacy code
> For async operations, wrap with a function using Result.try() and call it
> Variables use camelCase; Types use PascalCase; Constants may use UPPER_SNAKE_CASE
> Only export constants/functions/types that are used by other modules; keep internal/private items non-exported
> Always use Node.js path utilities for file paths for cross-platform compatibility
> Use in-source testing blocks guarded by if (import.meta.vitest != null); do not create separate test files
> Use Vitest globals (describe, it, expect) without imports inside test blocks
> Only use dynamic imports (await import()) inside test blocks to avoid tree-shaking issues
> Mock data in tests should use fs-fixture createFixture() for Claude data directory simulation
> Tests must use current Claude 4 models (Sonnet and Opus) and cover both; do not use Claude 3 models
> Model names in tests must exactly match LiteLLM pricing database entries

Files:
- `src/data-loader.ts`
- `src/_cost-storage.ts`
- `src/commands/statusline.ts`

</details>
<details>
<summary>docs/guide/*.md</summary>


**📄 CodeRabbit inference engine (CLAUDE.md)**

> Use image paths like "/screenshot.png" for images stored in /docs/public/ and always include descriptive alt text

Files:
- `docs/guide/statusline.md`

</details>
<details>
<summary>**/_*.ts</summary>


**📄 CodeRabbit inference engine (CLAUDE.md)**

> Internal files should use an underscore prefix (e.g., _types.ts, _utils.ts, _consts.ts)

Files:
- `src/_cost-storage.ts`

</details>

</details><details>
<summary>🧠 Learnings (4)</summary>

<details>
<summary>📚 Learning: 2025-08-17T12:27:03.128Z</summary>

Learnt from: CR
PR: ryoppippi/ccusage#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-17T12:27:03.128Z
Learning: Applies to **/*.{ts,tsx} : Mock data in tests should use fs-fixture createFixture() for Claude data directory simulation

**Applied to files:**
- `src/data-loader.ts`

</details>
<details>
<summary>📚 Learning: 2025-08-17T12:27:03.128Z</summary>

Learnt from: CR
PR: ryoppippi/ccusage#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-17T12:27:03.128Z
Learning: Applies to **/*.{ts,tsx} : Use in-source testing blocks guarded by if (import.meta.vitest != null); do not create separate test files

**Applied to files:**
- `src/data-loader.ts`

</details>
<details>
<summary>📚 Learning: 2025-08-17T12:27:03.128Z</summary>

Learnt from: CR
PR: ryoppippi/ccusage#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-17T12:27:03.128Z
Learning: Applies to **/*.{ts,tsx} : For async operations, wrap with a function using Result.try() and call it

**Applied to files:**
- `src/_cost-storage.ts`

</details>
<details>
<summary>📚 Learning: 2025-08-17T12:27:03.128Z</summary>

Learnt from: CR
PR: ryoppippi/ccusage#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-17T12:27:03.128Z
Learning: Applies to **/*.{ts,tsx} : Prefer praha/byethrow Result type over traditional try-catch; use Result.try(), Result.isFailure()/isSuccess() and early returns; reserve try-catch for complex file I/O or legacy code

**Applied to files:**
- `src/_cost-storage.ts`

</details>

</details><details>
<summary>🧬 Code graph analysis (3)</summary>

<details>
<summary>src/data-loader.ts (1)</summary><blockquote>

<details>
<summary>src/_cost-storage.ts (1)</summary>

* `getSavedCost` (182-190)

</details>

</blockquote></details>
<details>
<summary>src/_cost-storage.ts (2)</summary><blockquote>

<details>
<summary>src/_consts.ts (1)</summary>

* `DEFAULT_CLAUDE_CONFIG_PATH` (62-62)

</details>
<details>
<summary>src/logger.ts (1)</summary>

* `logger` (19-19)

</details>

</blockquote></details>
<details>
<summary>src/commands/statusline.ts (2)</summary><blockquote>

<details>
<summary>src/_cost-storage.ts (1)</summary>

* `saveCostData` (77-124)

</details>
<details>
<summary>src/logger.ts (1)</summary>

* `logger` (19-19)

</details>

</blockquote></details>

</details><details>
<summary>🪛 ESLint</summary>

<details>
<summary>src/data-loader.ts</summary>

[error] 758-758: Unsafe member access .sessionId on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 759-759: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 759-759: Unsafe member access .sessionId on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 766-766: Unsafe member access .costUSD on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 767-767: Unsafe return of a value of type error.

(ts/no-unsafe-return)

---

[error] 767-767: Unsafe member access .costUSD on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 771-771: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 772-772: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 772-772: Unsafe argument of type error typed assigned to a parameter of type `{ input_tokens: number; output_tokens: number; cache_creation_input_tokens?: number | undefined; cache_read_input_tokens?: number | undefined; }`.

(ts/no-unsafe-argument)

---

[error] 772-772: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 772-772: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 772-772: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 773-773: Unsafe return of a value of type error.

(ts/no-unsafe-return)

---

[error] 773-773: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 773-773: Unsafe member access .unwrap on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 784-784: Unsafe member access .sessionId on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 785-785: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 785-785: Unsafe member access .sessionId on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 792-792: Unsafe member access .costUSD on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 793-793: Unsafe argument of type error typed assigned to a parameter of type `number`.

(ts/no-unsafe-argument)

---

[error] 793-793: Unsafe member access .costUSD on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 797-797: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 798-798: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 798-798: Unsafe argument of type error typed assigned to a parameter of type `{ input_tokens: number; output_tokens: number; cache_creation_input_tokens?: number | undefined; cache_read_input_tokens?: number | undefined; }`.

(ts/no-unsafe-argument)

---

[error] 798-798: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 798-798: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 798-798: Unsafe member access .message on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 799-799: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 799-799: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 799-799: Unsafe member access .unwrap on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 800-800: Unsafe argument of type error typed assigned to a parameter of type `number`.

(ts/no-unsafe-argument)

</details>
<details>
<summary>src/_cost-storage.ts</summary>

[error] 12-16: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 12-12: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 12-12: Unsafe member access .object on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 13-13: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 13-13: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 13-13: Unsafe member access .string on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 14-14: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 14-14: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 14-14: Unsafe member access .number on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 15-15: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 15-15: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 15-15: Unsafe member access .literal on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 21-24: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 21-21: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 21-21: Unsafe member access .object on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 22-22: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 22-22: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 22-22: Unsafe member access .string on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 23-23: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 23-23: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 23-23: Unsafe member access .array on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 42-42: Unsafe return of a value of type error.

(ts/no-unsafe-return)

---

[error] 42-42: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 51-51: Unsafe return of a value of type error.

(ts/no-unsafe-return)

---

[error] 51-51: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 61-61: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 62-62: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 62-62: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 65-65: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 65-65: Unsafe member access .fail on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 82-82: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 83-83: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 83-83: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 83-83: Unsafe member access .isFailure on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 98-98: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 101-101: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 101-101: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 101-101: Unsafe member access .isSuccess on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 103-103: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 103-103: Unsafe member access .value on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 104-104: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 104-104: Unsafe member access .costs on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 116-116: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 118-118: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 118-118: Unsafe member access .debug on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 119-119: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 119-119: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 122-122: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 122-122: Unsafe member access .fail on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 134-134: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 134-134: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 135-135: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 136-136: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 136-136: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 136-136: Unsafe member access .safeParse on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 138-138: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 138-138: Unsafe member access .success on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 139-139: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 139-139: Unsafe member access .fail on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 139-139: Unsafe member access .error on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 142-142: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 142-142: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 142-142: Unsafe member access .data on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 145-145: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 145-145: Unsafe member access .fail on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 155-155: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 157-157: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 157-157: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 157-157: Unsafe member access .isFailure on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 158-158: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 158-158: Unsafe member access .debug on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 158-158: Unsafe member access .error on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 158-158: Unsafe member access .error on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 158-158: Unsafe member access .error on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 159-159: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 159-159: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 162-162: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 162-162: Unsafe member access .value on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 163-163: Unsafe member access .costs on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 164-164: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 164-164: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 168-170: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 168-170: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 168-169: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 168-168: Unsafe member access .costs on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 170-170: Unsafe member access .sort on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 170-170: Unsafe argument of type error typed assigned to a parameter of type `string | number | Date`.

(ts/no-unsafe-argument)

---

[error] 170-170: Unsafe member access .timestamp on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 170-170: Unsafe argument of type error typed assigned to a parameter of type `string | number | Date`.

(ts/no-unsafe-argument)

---

[error] 170-170: Unsafe member access .timestamp on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 172-172: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 172-172: Unsafe member access .succeed on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 172-172: Unsafe member access [0] on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 183-183: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 185-185: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 185-185: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 185-185: Unsafe member access .isSuccess on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 185-185: Unsafe member access .value on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 186-186: Unsafe return of a value of type error.

(ts/no-unsafe-return)

---

[error] 186-186: Unsafe member access .value on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 204-204: Unsafe assignment of an error typed value.

(ts/no-unsafe-assignment)

---

[error] 205-205: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 205-205: Unsafe member access .isFailure on an `error` typed value.

(ts/no-unsafe-member-access)

</details>
<details>
<summary>src/commands/statusline.ts</summary>

[error] 470-470: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 470-470: Unsafe member access .values on an `any` value.

(ts/no-unsafe-member-access)

---

[error] 470-470: Unsafe member access .cost on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 472-472: Unsafe argument of type error typed assigned to a parameter of type `string`.

(ts/no-unsafe-argument)

---

[error] 472-472: Unsafe argument of type error typed assigned to a parameter of type `number`.

(ts/no-unsafe-argument)

---

[error] 472-472: Unsafe member access .cost on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 474-474: Unexpected any value in conditional. An explicit comparison or type conversion is required.

(ts/strict-boolean-expressions)

---

[error] 474-474: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 474-474: Unsafe member access .isFailure on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 475-475: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 475-475: Unsafe member access .debug on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 475-475: Unsafe member access .error on an `error` typed value.

(ts/no-unsafe-member-access)

---

[error] 479-479: Unsafe call of a(n) `error` type typed value.

(ts/no-unsafe-call)

---

[error] 479-479: Unsafe member access .debug on an `error` typed value.

(ts/no-unsafe-member-access)

</details>

</details>
<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>docs/guide/statusline.md</summary>

[grammar] ~256-~256: There might be a mistake here.
Context: ...️ Moderate (Yellow) - 🚨 High (Red)  ## Cost Data Persistence  The statusline feat...

(QB_NEW_EN)

---

[grammar] ~258-~258: Ensure spelling is correct
Context: ...ost data for enhanced accuracy in other ccusage commands.  ### How It Works  When Claud...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

</details>

</details>
<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

<details>
<summary>docs/guide/statusline.md</summary>

264-264: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)</summary>

* GitHub Check: Workers Builds: ccusage-guide

</details>

</details>

<details>
<summary>🔇 Additional comments (11)</summary><blockquote>

<details>
<summary>src/_cost-storage.ts (1)</summary><blockquote>

`167-173`: **Sorting safety: rely on validated timestamps or pre-parse once**

If you adopt z.string().datetime(), this is safe. Otherwise, a malformed timestamp yields NaN and an unstable sort. The schema fix above addresses this; no further change needed if applied.

</blockquote></details>
<details>
<summary>src/commands/statusline.ts (1)</summary><blockquote>

`128-134`: **Nice addition: saveCost flag with sensible defaults**

Flag is negatable, kebab-cased, and defaults to true. This lines up with docs and config schema.

</blockquote></details>
<details>
<summary>src/data-loader.ts (1)</summary><blockquote>

`721-723`: **Docstring update accurate**

The parameter doc reflects the new modes and helps keep API self-documenting.

</blockquote></details>
<details>
<summary>config-schema.json (8)</summary><blockquote>

`32-42`: **Extending modes to include statusline and max looks good; descriptions are clear**

Enums and docs line up with code behavior. No issues here.

---

`138-149`: **Daily command mode enum updated consistently**

Matches defaults and other command sections.

---

`255-266`: **Monthly command mode enum updated consistently**

Aligned with other sections.

---

`356-367`: **Weekly command mode enum updated; startOfWeek option complements weekly features**

Looks consistent with code support.

---

`472-483`: **Session command mode enum updated**

Consistent with data-loader changes.

---

`578-589`: **Blocks command mode enum updated**

No concerns.

---

`686-697`: **MCP mode enum updated**

Consistent with global modes.

---

`774-779`: **New statusline.saveCost config mirrors CLI flag**

Property name, default and descriptions match statusline.ts. Good.

</blockquote></details>

</blockquote></details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->