Duration and usage

Use timing and usage to understand where effort went and where a process needs attention. A recorded cost, an operating budget, and available Workspace funding answer different questions.

Active and elapsed duration

The Task separates execution effort from the time that passed:

• Active time adds completed, successful work sessions. It excludes unfinished or unsuccessful Runs, automatic blocked-work and pull-request rechecks, and gaps between sessions.
• Elapsed time measures the span from the first included session starting to the last one ending, including pauses between them.

Several Workers running at once can accumulate more active time than elapsed time. Neither measure predicts how long the next Task will take.

Task time can be broken down by execution stage, such as planning, implementation, review, and rework. Use that distinction to find repeated review or rework instead of assuming every long Task spent its time on implementation.

Recorded cost and tokens

Task usage records the cost and tokens attributed to the work. Compare stages when you need to understand where usage accumulated. A failed attempt may still have consumed resources. Recorded Task usage, your operational budget, and the Workspace's available managed usage answer different questions.

See Billing and usage for charges and Analytics for comparisons across Tasks.

Compare work in Pulse

Use Timeline and Analytics in Pulse to compare the work you may access. Inspect a Task or Run for the detail behind a total. Billing explains how managed usage becomes a charge.