5 hour session window usage info by EphemeralSapient · Pull Request #55 · ccusage/ccusage

EphemeralSapient · 2025-06-11T10:31:38Z

A huge mess, made mistake and don't look at this PR

My bad, I've learnt my lesson

gemini-code-assist

Summary of Changes

Hello @EphemeralSapient, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request adds a significant new feature to the ccusage tool: the ability to analyze usage data specifically tailored to the Claude Max plan's 5-hour session window structure and its 50-session monthly limit. It provides detailed breakdowns per window and aggregates monthly statistics, including utilization and remaining sessions, to help users monitor their usage against the plan's constraints.

Highlights

New Command: Introduced a new sessions command to the CLI for tracking Claude Max plan 5-hour session windows.
Session Window Tracking: Implemented logic to group usage data entries into 5-hour windows based on the timestamp of the first message within that window's time slot.
Monthly Limit Monitoring: Added reporting for the 50-session monthly limit, showing total sessions used, remaining sessions, and utilization percentage per month.
Detailed Window Breakdown: The report includes a table detailing each 5-hour window with metrics like duration, message count, conversation count, token usage (input, output, cache), and cost.
Reporting Options: The new command supports existing options like --since, --until for date filtering, --json for machine-readable output, --mode for cost calculation, and --order for sorting monthly results.

Using Gemini Code Assist

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.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	`/gemini help`	Displays a list of available 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 is currently in preview and 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 to provide feedback.

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.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request adds a new sessions command to report Claude Code usage based on 5-hour session windows, including tracking against a monthly limit. The changes are well-tested and cover README updates, command implementation, data loading logic, and type definitions.

Key feedback points include ensuring consistency in default sort order documentation and implementation, correcting a token aggregation bug in loadSessionWindowData for monthly stats, and suggesting improvements for maintainability. The overall structure is good, and addressing these points will enhance the feature's robustness and clarity.

gemini-code-assist · 2025-06-11T10:34:28Z

+
+			const totals = windows.reduce((acc, window) => ({
+				cost: acc.cost + window.totalCost,
+				tokens: acc.tokens + window.inputTokens + window.outputTokens,


The totals.tokens accumulation for monthly stats currently only sums window.inputTokens and window.outputTokens. This is inconsistent with how totalTokens is generally treated for individual windows (which includes all four types: input, output, cache creation, cache read) and how totalTokens is defined in SessionWindowSchema and used in sessions.ts.

To ensure consistency, totalTokens for the month should be the sum of all token types across all windows in that month.

tokens: acc.tokens + window.inputTokens + window.outputTokens + window.cacheCreationTokens + window.cacheReadTokens,

gemini-code-assist · 2025-06-11T10:34:28Z

+ccusage sessions --order asc       # Show oldest months first
+ccusage sessions --order desc      # Show newest months first (default)


The default sort order for months in the sessions command is documented here as desc (newest months first). However, the sharedCommandConfig in src/shared-args.internal.ts specifies asc as the default for the --order argument. The sessionsCommand inherits this default.

This means that without an explicit --order flag, the sessions command will sort months in ascending order (oldest first), contradicting this documentation.

Consider either:

Changing the default for order in src/shared-args.internal.ts to desc if this is the preferred default for most/all commands.

Overriding the default for the order argument specifically within the sessionsCommand definition in src/commands/sessions.ts.

Updating this documentation to reflect asc as the default.

gemini-code-assist · 2025-06-11T10:34:28Z

+			while (sessionWindows.has(newWindowId)) {
+				newWindowStart = new Date(newWindowStart.getTime() + 5 * 60 * 60 * 1000);
+				newWindowId = getSessionWindowId(newWindowStart.toISOString());
+			}


The while loop for finding an unused newWindowId seems to handle a potential key collision in the sessionWindows map. If getSessionWindowId(entry.data.timestamp) (which is newWindowId initially) is already a key, this loop shifts newWindowStart by 5-hour increments until an unused getSessionWindowId is found for the map key.

This means the window.windowId stored for the new session window (line 596) might not be getSessionWindowId(window.startTime). This could be confusing as windowId might not directly correspond to the window's actual start time's 5-hour slot.

If the intent is for window.windowId to always reflect getSessionWindowId(window.startTime), an alternative approach for map keys might be needed, such as using window.startTime.toISOString() as the unique key in sessionWindows map, and then deriving the reported windowId from window.startTime when constructing the SessionWindow object. This would simplify the key management here.

However, if this logic is intentionally mimicking a specific behavior of how Claude might use fixed slots, it might be correct but complex. Adding a comment explaining this specific scenario and why the key might be shifted would improve maintainability.

gemini-code-assist · 2025-06-11T10:34:28Z

+	const sortOrder = options?.order ?? 'desc';
+	const sortedStats = sort(monthlyStats);
+	return sortOrder === 'desc'
+		? sortedStats.desc(item => item.month)
+		: sortedStats.asc(item => item.month);


The default sort order for monthly stats is determined here. options?.order ?? 'desc' means if options.order is undefined or null, it defaults to desc.

However, sharedCommandConfig (in src/shared-args.internal.ts) sets the default for the --order argument to 'asc'. If gunshi passes this default value when the user doesn't specify --order, then options.order will be 'asc', and the ?? 'desc' fallback won't be used. This results in months being sorted ascendingly by default.

This conflicts with the README for the sessions command, which states that desc (newest months first) is the default. This inconsistency should be resolved. See the comment on README.md:223-224 for suggestions.

ryoppippi · 2025-06-11T11:02:24Z

@EphemeralSapient Hi
Thank you for this PR. Awesome.

I found that there is a magic number remainingSessions. 50 session limit is only for $100 plan and $200 plan has different limitation, right? If I'm wrong explain it.

ryoppippi · 2025-06-11T11:02:23Z

+
+				logger.info(`\n${pc.bold(monthStats.month)} - ${pc[utilizationColor](`${monthStats.totalSessions} sessions used`)} (${pc[utilizationColor](`${monthStats.utilizationPercent.toFixed(1)}%`)} of 50 limit)`);
+
+				if (monthStats.remainingSessions <= 5 && monthStats.remainingSessions > 0) {


what does 5 mean?

ryoppippi · 2025-06-11T11:04:15Z

+
+export const SessionWindowSchema = v.object({
+	windowId: v.string(), // Format: YYYY-MM-DD-HH (start of 5-hour window)
+	startTime: v.string(), // ISO timestamp of first message in window
+	endTime: v.string(), // ISO timestamp of last message in window
+	inputTokens: v.number(),
+	outputTokens: v.number(),
+	cacheCreationTokens: v.number(),
+	cacheReadTokens: v.number(),
+	totalCost: v.number(),
+	messageCount: v.number(), // Number of messages in this window
+	conversationCount: v.number(), // Number of unique conversations in this window
+});
+
+export type SessionWindow = v.InferOutput<typeof SessionWindowSchema>;
+
+export const CurrentSessionInfoSchema = v.object({
+	hasActiveSession: v.boolean(),
+	timeRemainingMs: v.number(),
+	timeRemainingFormatted: v.string(),
+	activeWindow: v.optional(SessionWindowSchema),
+});
+
+export type CurrentSessionInfo = v.InferOutput<typeof CurrentSessionInfoSchema>;
+
+export const SessionWindowStatsSchema = v.object({
+	month: v.pipe(
+		v.string(),
+		v.regex(/^\d{4}-\d{2}$/), // YYYY-MM format
+	),
+	totalSessions: v.number(), // Total number of 5-hour windows with activity
+	remainingSessions: v.number(), // 50 - totalSessions (Max plan limit)
+	utilizationPercent: v.number(), // (totalSessions / 50) * 100
+	totalCost: v.number(),
+	totalTokens: v.number(),
+	averageCostPerSession: v.number(),
+	averageTokensPerSession: v.number(),
+	windows: v.array(SessionWindowSchema),
+	currentSession: v.optional(CurrentSessionInfoSchema),
+});
+
+export type SessionWindowStats = v.InferOutput<typeof SessionWindowStatsSchema>;


you can define those types in data-loader.ts because we don't use it in other files.
also you can stop exporting it

pkg-pr-new · 2025-06-11T11:04:38Z

Open in StackBlitz

npm i https://pkg.pr.new/ryoppippi/ccusage@55

commit: 94bd31e

Copilot

Pull Request Overview

This PR implements 5-hour session window tracking for the Claude Max plan, grouping usage into fixed windows and enforcing a 50-session monthly limit.

Defined new Zod‐style schemas (SessionWindow, CurrentSessionInfo, SessionWindowStats) in types.internal.ts
Added loadSessionWindowData, window‐grouping utilities, and current session calculation in data-loader.ts
Introduced ccusage sessions command, corresponding tests, and documentation in commands/ and README.md

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/types.internal.ts	Added session window and monthly stats schemas
src/data-loader.ts	Implemented session window ID calculation and grouping
src/data-loader.test.ts	Added comprehensive tests for loadSessionWindowData
src/commands/sessions.ts	New CLI command for session window reports
src/commands/index.ts	Registered the new `sessions` subcommand
README.md	Updated docs and usage examples for session windows report

Copilot · 2025-06-11T11:16:13Z

+
+			const newWindow = {
+				windowId: newWindowId,
+				startTime: entry.timestamp,


The new window’s startTime is set to the original entry.timestamp even after adjusting newWindowStart in the loop. This can misalign the window start when slot collisions occur. Use newWindowStart instead of entry.timestamp for startTime to match the computed windowId.

Suggested change

startTime: entry.timestamp,

startTime: newWindowStart,

Copilot · 2025-06-11T11:16:14Z

+							+ window.cacheCreationTokens + window.cacheReadTokens;
+
+						windowsTable.push([
+							startTime.toLocaleString().substring(0, 16), // Remove seconds


[nitpick] Using substring on toLocaleString output is brittle and locale-dependent. Consider using toLocaleString with explicit formatting options (e.g., { year: 'numeric', month: '2-digit', day: '2-digit', hour: '2-digit', minute: '2-digit' }) for consistent results.

Suggested change

startTime.toLocaleString().substring(0, 16), // Remove seconds

startTime.toLocaleString('en-US', { year: 'numeric', month: '2-digit', day: '2-digit', hour: '2-digit', minute: '2-digit' }), // Consistent formatting

EphemeralSapient · 2025-06-11T13:12:07Z

ah, forgot about that completely, I thought both 100$ and 200$ plan had same session; I was wrong

followed up with above review; again used CC , sorry if I missed anything :P

coderabbitai · 2025-06-11T13:26:41Z

Walkthrough

A new "Session Windows Report" feature was introduced, targeting the Claude Max plan. This includes a CLI command and data loader logic to aggregate usage into 5-hour session windows, track monthly session limits, and provide detailed per-window and monthly statistics. Documentation, CLI registration, argument defaults, and comprehensive tests were added or updated.

Changes

File(s)	Change Summary
README.md	Added documentation for "Session Windows Report" and updated CLI usage, tool listings, and output examples.
package.json	Reformatted file from tab to space indentation; no content changes.
src/commands/index.ts	Imported and registered the new `sessionsCommand` in the CLI subCommands map.
src/commands/sessions.ts	Added new CLI command for session window reporting, supporting JSON and formatted output, and session limit tracking.
src/data-loader.ts	Added logic for 5-hour session window grouping, aggregation, statistics, and new types; extended loader options.
src/data-loader.test.ts	Added extensive tests for session window data loading, aggregation, and edge cases.
src/shared-args.internal.ts	Changed default sort order to 'desc'; added `sessionLimit` and `warningThreshold` arguments with defaults.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI (sessionsCommand)
    participant DataLoader (loadSessionWindowData)
    participant Formatter/Console

    User->>CLI (sessionsCommand): Run `ccusage sessions` with options
    CLI (sessionsCommand)->>DataLoader (loadSessionWindowData): Load session window data (with filters, limits)
    DataLoader (loadSessionWindowData)-->>CLI (sessionsCommand): Aggregated session stats (per window, per month)
    CLI (sessionsCommand)->>Formatter/Console: Format and output report (JSON or styled table)
    Formatter/Console-->>User: Display session windows report

Poem

In five-hour windows, the sessions align,
Counting each token, each message, in time.
Fifty per month—watch the colors appear,
As limits approach, the warnings draw near.
Now Max plan users can clearly see,
Their session adventures in usage history!
🐇✨

✨ Finishing Touches

📝 Generate Docstrings

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 6

♻️ Duplicate comments (2)

src/data-loader.ts (2)
765-768: ⚠️ Potential issue

Include all token types in monthly total tokens calculation.

The totalTokens calculation currently only sums inputTokens and outputTokens, but cache tokens (cacheCreationTokens and cacheReadTokens) are tracked separately in windows. For consistency with how tokens are aggregated elsewhere in the codebase, include all token types.
 const totals = windows.reduce((acc, window) => ({
 	cost: acc.cost + window.totalCost,
-	tokens: acc.tokens + window.inputTokens + window.outputTokens,
+	tokens: acc.tokens + window.inputTokens + window.outputTokens + window.cacheCreationTokens + window.cacheReadTokens,
 }), { cost: 0, tokens: 0 });
🧰 Tools

🪛 ESLint

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-member-access)

689-708: ⚠️ Potential issue

Fix window start time to match the computed window ID.

When a new window ID is computed after collision detection, the window's startTime should be set to newWindowStart to maintain consistency between the window ID and its actual start time.
 const newWindow = {
 	windowId: newWindowId,
-	startTime: entry.timestamp,
+	startTime: newWindowStart,
 	endTime: entry.timestamp,
 	entries: [entry],
 	conversationIds: new Set([entry.conversationId]),
 };
🧰 Tools

🪛 ESLint

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

(ts/no-unsafe-argument)

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

(ts/no-unsafe-call)

[error] 696-696: Unsafe member access .getTime on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-argument)

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

(ts/no-unsafe-call)

[error] 697-697: Unsafe member access .toISOString on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

[error] 705-705: Unsafe member access .conversationId on an error typed value.

(ts/no-unsafe-member-access)

🧹 Nitpick comments (3)

README.md (1)
365-394: Add language tag to fenced block

Markdown-lint warning MD040 – simply append bash:
-``` 
+```bash
🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

365-365: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)
src/commands/sessions.ts (2)
61-63: totalTokens recomputed but already available

window.totalTokens exists in loader output. Recomputing risks divergence if loader logic changes.
-totalTokens: window.inputTokens + window.outputTokens + window.cacheCreationTokens + window.cacheReadTokens,
+totalTokens: window.totalTokens,
🧰 Tools

🪛 ESLint

[error] 61-61: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 61-61: Unsafe member access .inputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .outputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .cacheCreationTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .cacheReadTokens on an any value.

(ts/no-unsafe-member-access)

[error] 62-62: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 62-62: Unsafe member access .totalCost on an any value.

(ts/no-unsafe-member-access)

[error] 63-63: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 63-63: Unsafe member access .messageCount on an any value.

(ts/no-unsafe-member-access)

144-146: Date display uses brittle substring

toISOString().substring(0, 10) is always UTC; users in other zones may see an off-by-one date. Use locale-aware formatting:
-startTime.toISOString().substring(0, 10)
+startTime.toLocaleDateString('en-CA') // YYYY-MM-DD
Maintains fixed width while respecting local midnight.

🧰 Tools

🪛 ESLint

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

(ts/no-unsafe-argument)

[error] 146-146: Unsafe member access .messageCount on an error typed value.

(ts/no-unsafe-member-access)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6f9836d and 089a153.

📒 Files selected for processing (7)

README.md (4 hunks)
package.json (1 hunks)
src/commands/index.ts (1 hunks)
src/commands/sessions.ts (1 hunks)
src/data-loader.test.ts (2 hunks)
src/data-loader.ts (4 hunks)
src/shared-args.internal.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (3)

src/shared-args.internal.ts (1)

src/types.internal.ts (2)

SortOrder (13-13)

SortOrders (12-12)

src/commands/sessions.ts (4)

src/shared-args.internal.ts (1)

sharedCommandConfig (79-82)

src/logger.ts (2)

logger (5-5)

log (8-8)

src/data-loader.ts (1)

loadSessionWindowData (579-795)

src/utils.internal.ts (2)

formatNumber (1-3)

formatCurrency (5-7)

src/data-loader.test.ts (1)

src/data-loader.ts (2)

loadSessionWindowData (579-795)

UsageData (81-81)

🪛 ESLint

src/shared-args.internal.ts

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

(ts/no-unsafe-assignment)

src/commands/sessions.ts

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-call)

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

(ts/strict-boolean-expressions)

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

(ts/no-unsafe-member-access)

[error] 16-16: Unsafe member access .level on an error typed value.

(ts/no-unsafe-member-access)

[error] 20-20: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-member-access)

[error] 25-25: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

[error] 26-26: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-member-access)

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

(ts/strict-boolean-expressions)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-call)

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

(ts/no-unsafe-call)

[error] 34-34: Unsafe member access .warn on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-call)

[error] 36-36: Unsafe member access .exit on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/strict-boolean-expressions)

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

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 43-43: Unsafe member access .month on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 44-44: Unsafe member access .totalSessions on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 45-45: Unsafe member access .remainingSessions on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 46-46: Unsafe member access .utilizationPercent on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 47-47: Unsafe member access .sessionLimit on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 48-48: Unsafe member access .totalCost on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 49-49: Unsafe member access .totalTokens on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 50-50: Unsafe member access .averageCostPerSession on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 51-51: Unsafe member access .averageTokensPerSession on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

[error] 52-52: Unsafe member access .currentSession on an error typed value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-assignment)

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

(ts/no-unsafe-call)

[error] 53-53: Unsafe member access .windows on an error typed value.

(ts/no-unsafe-member-access)

[error] 54-54: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 54-54: Unsafe member access .windowId on an any value.

(ts/no-unsafe-member-access)

[error] 55-55: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 55-55: Unsafe member access .startTime on an any value.

(ts/no-unsafe-member-access)

[error] 56-56: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 56-56: Unsafe member access .endTime on an any value.

(ts/no-unsafe-member-access)

[error] 57-57: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 57-57: Unsafe member access .inputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 58-58: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 58-58: Unsafe member access .outputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 59-59: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 59-59: Unsafe member access .cacheCreationTokens on an any value.

(ts/no-unsafe-member-access)

[error] 60-60: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 60-60: Unsafe member access .cacheReadTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 61-61: Unsafe member access .inputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .outputTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .cacheCreationTokens on an any value.

(ts/no-unsafe-member-access)

[error] 61-61: Unsafe member access .cacheReadTokens on an any value.

(ts/no-unsafe-member-access)

[error] 62-62: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 62-62: Unsafe member access .totalCost on an any value.

(ts/no-unsafe-member-access)

[error] 63-63: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 63-63: Unsafe member access .messageCount on an any value.

(ts/no-unsafe-member-access)

[error] 64-64: Unsafe assignment of an any value.

(ts/no-unsafe-assignment)

[error] 64-64: Unsafe member access .conversationCount on an any value.

(ts/no-unsafe-member-access)

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

(ts/no-unsafe-call)

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

(ts/no-unsafe-call)

[error] 72-72: Unsafe member access .box on an error typed value.

(ts/no-unsafe-member-access)

[error] 76-76: Unsafe member access .utilizationPercent on an error typed value.

(ts/no-unsafe-member-access)

[error] 78-78: Unsafe member access .utilizationPercent on an error typed value.

(ts/no-unsafe-member-access)