feat(ccusage): add --no-cost flag to hide cost column

[majiayu000]

Summary

Add --no-cost option to all commands (daily, monthly, session, blocks) to hide cost information from table output. This is useful for Claude Pro subscribers who pay a flat rate and don't need cost tracking.

• Add noCost flag to shared args
• Update table utilities to support hideCost option
• Apply hideCost to formatUsageDataRow, formatTotalsRow, pushBreakdownRows
• Update all commands to conditionally hide cost column

Closes #625

Summary by CodeRabbit

• New Features
  • Added new option to hide cost columns from all usage reports and data tables, including daily, monthly, session, and block analysis views. This feature provides a cleaner viewing experience and is specifically designed for Pro subscribers who prefer to focus exclusively on usage metrics without cost information being displayed throughout their reports.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A --noCost flag is added to the shared CLI arguments, then propagated through command handlers (blocks, daily, monthly, session) to conditionally hide cost columns in table outputs. Core table formatting functions are refactored to accept new option types controlling cost and activity display.

Changes

Cohort / File(s)	Summary
CLI Flag Definition apps/ccusage/src/_shared-args.ts	Adds public boolean flag noCost with description and default value false.
Command Implementations apps/ccusage/src/commands/blocks.ts, apps/ccusage/src/commands/daily.ts, apps/ccusage/src/commands/monthly.ts, apps/ccusage/src/commands/session.ts	Each command derives hideCost from ctx.values.noCost (or mergedOptions.noCost), computes dynamic columnCount, and passes hideCost through table configuration and formatting function calls. Adjusts placeholder row generation and header/alignment lists to respect cost column visibility.
Core Table Library packages/terminal/src/table.ts	Introduces new public types FormatRowOptions and FormatTotalsOptions to parameterize formatting. Updates function signatures for formatUsageDataRow, formatTotalsRow, and pushBreakdownRows to accept/respect hideCost option. Extends UsageReportConfig with optional hideCost flag. Conditionally includes cost columns in headers, alignment, and row data based on flag.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• PR #52: Modifies the same table API functions (pushBreakdownRows, formatUsageDataRow, formatTotalsRow) and UsageReportConfig that are extended by this PR.
• PR #603: Updates table utilities and function signatures (formatUsageDataRow, formatTotalsRow) that are further refactored in this PR to accept new option types.
• PR #80: Modifies the blocks command's cost-related output rendering, directly affected by the cost-hiding logic introduced here.

Suggested reviewers

• ryoppippi

Poem

🐰 A carrot-free view of the hop,
No dollar signs make wallets stop,
Just tokens dancing, pure and bright,
Hidden costs—out of sight!
The CLI gets sleek and light,
With flags to set what's just right! 🌕

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main feature added in this PR: a new --no-cost flag for hiding cost columns across all commands.
Linked Issues check	✅ Passed	The PR fully addresses issue #625 by implementing a --no-cost flag that allows users to hide the cost column from output across all commands (daily, monthly, session, blocks).
Out of Scope Changes check	✅ Passed	All changes are directly related to implementing the --no-cost flag feature and its integration across the codebase; no unrelated modifications were introduced.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6335626 and 8d3fd62.

📒 Files selected for processing (6)

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/monthly.ts
• apps/ccusage/src/commands/session.ts
• packages/terminal/src/table.ts

🧰 Additional context used

📓 Path-based instructions (6)

apps/ccusage/src/**/*.ts

📄 CodeRabbit inference engine (apps/ccusage/CLAUDE.md)

apps/ccusage/src/**/*.ts: Write tests in-source using if (import.meta.vitest != null) blocks instead of separate test files
Use Vitest globals (describe, it, expect) without imports in test blocks
In tests, use current Claude 4 models (sonnet-4, opus-4)
Use fs-fixture with createFixture() to simulate Claude data in tests
Only export symbols that are actually used by other modules
Do not use console.log; use the logger utilities from src/logger.ts instead

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• apps/ccusage/src/commands/monthly.ts

apps/ccusage/**/*.ts

📄 CodeRabbit inference engine (apps/ccusage/CLAUDE.md)

apps/ccusage/**/*.ts: NEVER use await import() dynamic imports anywhere (especially in tests)
Prefer @praha/byethrow Result type for error handling instead of try-catch
Use .ts extensions for local imports (e.g., import { foo } from './utils.ts')

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• apps/ccusage/src/commands/monthly.ts

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{ts,tsx,js,jsx}: Use ESLint for linting and formatting with tab indentation and double quotes
No console.log allowed except where explicitly disabled with eslint-disable; use logger.ts instead
Use file paths with Node.js path utilities for cross-platform compatibility
Use variables starting with lowercase (camelCase) for variable names
Can use UPPER_SNAKE_CASE for constants

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• packages/terminal/src/table.ts
• apps/ccusage/src/commands/monthly.ts

**/*.ts{,x}

📄 CodeRabbit inference engine (CLAUDE.md)

Use TypeScript with strict mode and bundler module resolution

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• packages/terminal/src/table.ts
• apps/ccusage/src/commands/monthly.ts

**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{ts,tsx}: Use .ts extensions for local file imports (e.g., import { foo } from './utils.ts')
Prefer @praha/byethrow Result type over traditional try-catch for functional error handling
Use Result.try() for wrapping operations that may throw (JSON parsing, etc.)
Use Result.isFailure() for checking errors (more readable than !Result.isSuccess())
Use early return pattern (if (Result.isFailure(result)) continue;) instead of ternary operators when checking Results
Keep traditional try-catch only for file I/O with complex error handling or legacy code that's hard to refactor
Always use Result.isFailure() and Result.isSuccess() type guards for better code clarity
Use uppercase (PascalCase) for type names
Only export constants, functions, and types that are actually used by other modules - internal constants used only within the same file should NOT be exported
In-source testing pattern: write tests directly in source files using if (import.meta.vitest != null) blocks
CRITICAL: DO NOT use await import() dynamic imports anywhere in the codebase - this causes tree-shaking issues
CRITICAL: Never use dynamic imports with await import() in vitest test blocks - this is particularly problematic for test execution
Vitest globals (describe, it, expect) are enabled and available without imports since globals are configured
Create mock data using fs-fixture with createFixture() for Claude data directory simulation in tests
All test files must use current Claude 4 models (claude-sonnet-4-20250514, claude-opus-4-20250514), not outdated Claude 3 models
Model names in tests must exactly match LiteLLM's pricing database entries

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• packages/terminal/src/table.ts
• apps/ccusage/src/commands/monthly.ts

**/*.{ts,tsx,json}

📄 CodeRabbit inference engine (CLAUDE.md)

Claude model naming convention: claude-{model-type}-{generation}-{date} (e.g., claude-sonnet-4-20250514, NOT claude-4-sonnet-20250514)

Files:

• apps/ccusage/src/_shared-args.ts
• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• apps/ccusage/src/commands/session.ts
• packages/terminal/src/table.ts
• apps/ccusage/src/commands/monthly.ts

🧠 Learnings (2)

📚 Learning: 2025-09-18T16:07:16.293Z

Learnt from: CR
Repo: ryoppippi/ccusage PR: 0
File: apps/codex/CLAUDE.md:0-0
Timestamp: 2025-09-18T16:07:16.293Z
Learning: --json outputs structured results with aggregated tokens and USD cost included in totals

Applied to files:

• apps/ccusage/src/commands/blocks.ts
• apps/ccusage/src/commands/daily.ts
• packages/terminal/src/table.ts
• apps/ccusage/src/commands/monthly.ts

📚 Learning: 2025-09-18T16:07:16.293Z

Learnt from: CR
Repo: ryoppippi/ccusage PR: 0
File: apps/codex/CLAUDE.md:0-0
Timestamp: 2025-09-18T16:07:16.293Z
Learning: Cost calculation per model/date: charge non-cached input, cached input (fallback to input rate if missing), and output using the specified per-million token rates

Applied to files:

• apps/ccusage/src/commands/daily.ts

🧬 Code graph analysis (2)

apps/ccusage/src/commands/blocks.ts (2)

apps/ccusage/src/logger.ts (1)

• log (22-22)

apps/codex/src/token-utils.ts (1)

• formatCurrency (54-54)

apps/ccusage/src/commands/session.ts (2)

packages/terminal/src/table.ts (4)

• UsageReportConfig (420-431)
• createUsageReportTable (450-509)
• pushBreakdownRows (370-415)
• addEmptySeparatorRow (597-600)

apps/ccusage/src/_date-utils.ts (1)

• formatDateCompact (70-85)

🔇 Additional comments (16)

apps/ccusage/src/_shared-args.ts (1)

111-115: LGTM! Clean implementation of the new flag.

The noCost flag follows the established pattern of other boolean arguments in sharedArgs. The naming will correctly convert to --no-cost via the toKebab: true configuration.

packages/terminal/src/table.ts (4)

368-415: LGTM! Clean implementation of hideCost in breakdown rows.

The conditional cost rendering is correctly implemented. The parameter is properly added at the end to maintain backward compatibility with existing callers.

---

429-431: LGTM! Proper config extension and conditional column handling.

The UsageReportConfig type extension and the conditional spreading in createUsageReportTable are well implemented. The type assertion for TableCellAlign in the spread is necessary and correctly applied.

Also applies to: 450-489

---

511-552: LGTM! Good refactoring to options object pattern.

The migration from positional lastActivity parameter to an options object (FormatRowOptions) improves extensibility. All command files in this PR have been updated to use the new signature with { lastActivity, hideCost }.

---

554-590: LGTM! Consistent refactoring pattern.

The formatTotalsRow function follows the same options object pattern as formatUsageDataRow, maintaining consistency across the API.

apps/ccusage/src/commands/daily.ts (3)

136-148: LGTM! Correct hideCost derivation and column count calculation.

The Boolean() wrapper ensures proper boolean conversion from the CLI value, and the column count calculation (7 vs 8) correctly accounts for the cost column removal.

---

170-184: LGTM! Proper hideCost propagation in project-grouped display.

The hideCost option is correctly passed to both formatUsageDataRow and pushBreakdownRows within the project-grouped display path.

---

192-222: LGTM! Consistent hideCost handling in standard display and totals.

Both the standard display loop and the totals row correctly propagate the hideCost option through all formatting functions.

apps/ccusage/src/commands/blocks.ts (4)

326-326: LGTM! Complete hideCost handling in single active block view.

All cost-related outputs (total cost, burn rate cost/hour, and projection cost) are properly guarded by the hideCost flag. The empty log('') calls maintain visual spacing when cost is hidden.

Also applies to: 344-370

---

400-414: LGTM! Correct conditional header construction.

The cost column is properly excluded from both headers and alignment arrays when hideCost is true.

---

442-444: LGTM! Consistent cost column handling in table rows.

Both gap rows and regular block rows correctly handle the conditional cost column.

Also applies to: 466-468

---

487-497: LGTM! Proper type annotations for mixed row structures.

The explicit type annotation (string | { content: string; hAlign: 'right' })[] is necessary here because the row contains a mix of strings and objects with custom alignment. The conditional cost handling is correctly implemented for both REMAINING and PROJECTED rows.

Also applies to: 508-525

apps/ccusage/src/commands/monthly.ts (2)

101-114: LGTM! Consistent implementation with daily.ts.

The hideCost derivation and column count calculation follow the same pattern as the daily command, ensuring consistent behavior across commands.

---

116-145: LGTM! Complete hideCost propagation through all formatting calls.

All formatting functions (formatUsageDataRow, pushBreakdownRows, addEmptySeparatorRow, formatTotalsRow) correctly receive and use the hideCost option.

apps/ccusage/src/commands/session.ts (2)

127-141: LGTM! Correct column count for session reports.

The column count calculation (8 vs 9) correctly accounts for both the optional cost column and the session-specific Last Activity column. Session reports have one more column than daily/monthly reports.

---

150-178: LGTM! Complete hideCost propagation with session-specific options.

All formatting calls correctly combine the session-specific options (lastActivity, includeLastActivity, trailing columns) with the new hideCost option. The pushBreakdownRows call correctly uses trailingColumns=1 to account for the Last Activity column.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[ryoppippi]

@majiayu000 looks good! please apply it for codex and opencode as well!!!