AI Active Time vs. Session Time: What Your Statistics Actually Mean

“Time spent with AI” sounds like one statistic, but it can describe several very different measurements.

A chat might remain open for three hours while the model generates for only two minutes. A coding agent might actively run commands for twenty minutes, pause for approval, and then wait while the user reviews a diff.

A trustworthy analytics product should never combine those periods into one unexplained number.

Session wall time

Session wall time measures the elapsed period between the beginning and end of a session.

If a session starts at 1:00 p.m. and its final recorded event occurs at 3:00 p.m., the derived wall time is two hours.

This includes:

• Model generation.
• Tool execution.
• User typing.
• User review.
• Idle time.
• Breaks.
• Approval delays.

Wall time describes the session’s span, not continuous work.

AI active time

AI active time measures periods in which the model or its tools were actively processing.

Depending on the source, this may include:

• Response generation.
• Reasoning spans.
• Tool calls.
• terminal commands.
• subagent tasks.
• code analysis.

Some coding tools expose these spans directly through telemetry. In that case, the number can be source-reported or exact within the provider’s definition.

A basic web-chat export may not contain response-start and response-end events. In that case, exact AI active time is unavailable.

User active time

User active time attempts to measure typing, reading, approving, editing, and reviewing.

It is usually the hardest value to calculate.

A browser or desktop collector can observe interaction events, but an imported conversation history may contain only message timestamps. The tracker can estimate activity windows, but the result must be labelled estimated.

A reasonable heuristic begins a user-active interval when the user submits a prompt or performs an action. It continues while related actions occur within a short idle threshold. Long gaps are excluded.

This still cannot determine whether the user was carefully reading or had simply left the tab open.

Waiting time

Waiting time can include:

• Response latency.
• Tool execution delay.
• Agent queue time.
• approval waits.

The source must provide enough event detail to separate these periods. Otherwise, the tracker should not manufacture a number.

Overlapping activity

Agentic coding introduces another problem: several activities may overlap.

A parent agent can launch subagents while tools run concurrently. Adding every duration together may produce five hours of “work” inside a one-hour session.

Both numbers may be useful, but they answer different questions:

• **Elapsed active time:** how long the user waited.
• **Concurrent compute time:** the sum of all agent spans.
• **Peak concurrency:** the largest number of simultaneous agents.

The dashboard should name these separately.

Why confidence labels matter

Consider two sessions:

### Session A

Claude Code emits model and tool spans.

• Wall time: 38 minutes.
• AI active time: 21 minutes.
• User active time: estimated 11 minutes.
• Idle time: 6 minutes.

### Session B

A ChatGPT export contains message timestamps only.

• Wall time: derived 44 minutes.
• AI active time: unavailable.
• User active time: estimated.
• Idle time: unknown.

Displaying both as “44 minutes worked” would be misleading.

The better dashboard

Each time metric should include:

• Name.
• Definition.
• Source.
• Calculation.
• Quality.
• Known limitations.

A tooltip might say:

> AI active time — Derived from model and tool spans. Overlapping spans are deduplicated. Background activity not emitted by the source may be missing.

Clear definitions make the statistics more useful, not less impressive.

Use time statistics for patterns, not judgement

AI analytics can reveal:

• When sessions happen.
• Which providers dominate.
• Which projects take the most time.
• How often sessions become long and iterative.
• Whether coding agents reduce or increase review time.

They should not automatically declare one user more productive than another. Time is context, not a score.

The most valuable tracker is the one that tells users what it knows, how it knows it, and what remains uncertain.