Time, cost and limits

Settings → Expense → Time and cost of projects shows the history of this machine, including archived and deleted tasks. Select period, area and project. The team cloud only receives value when publishing separately.

Indicator Meaning
Agents The total execution time of all sessions without waiting for permissions; parallel sessions are summed up
By the hour Combined intervals for the execution of one task: a parallel section is counted once
Permissions Waiting time for a human response; multiple open questions do not reset the wait when answering one
Under review / In line Calendar time of the corresponding stage, including closed application
Man Minutes clearly entered through Time and limits → My work
Before acceptance The entire calendar cycle from task creation to adoption of a specific version
Repeated turns The authors' turns after returning the task from verification to work; inspectors are not included
Cost Increases in provider reports with a saved agent and model; "from" indicates incomplete coverage

Completing a turn is considered the completion of a request, while accepting a task is a separate action. The cost of an unknown turn is not considered zero. Service requests through the AI ​​service and auto-naming currently report the duration and number of requests without a price. The amount of context in the previous expense section is an approximate indicator, not the paid input/output tokens.

During operation, a timer is set every five seconds. After an accident, the unfinished interval is closed at the last tick: idle time of the disabled application is not accrued. The last seconds before the accident may be missing. Old data is restored from existing transcripts; Waiting for permissions was not saved in the old version and cannot be restored separately.

The notch only relates to time tracking and does not save anything from the code. It is impossible to return to the state of work on it: git is responsible for rollback - commits, task branch and accepted revision of the result. The word "checkpoint" is deliberately not used here because it promises a return that does not exist.

Unloading

Buttons CSV export and JSON export save what is shown on the screen for the selected period, area and project.

JSON - one object: tasks, a slice by agents and models, a slice by service AI requests, and the narrowing itself (project, taskId, scope, period boundaries) so that the file shows what exactly was calculated.

CSV - three tables in a row in one file, separated by an empty line:

  1. Tasks - first, the header in the first line of the file: import without settings reads it as before.
  2. Agents and models — agent, model, turns, agentMs, costUsd, unknownCostTurns.
  3. Service AI requests outside of sessions — provider, model, requests, durationMs, unknownCostRequests.

Service requests are counted only for the entire history: when you select a project, task, or area other than “all,” the third table is replaced with the line “Not counted: the slice is narrowed by project, task, or area.” An empty table would read “there were no requests,” which is not true.

The unknown price does not appear in the file as zero: cell costUsd remains empty and unknownCostTurns and unknownCostRequests show how many turns and requests were left without a price. Values starting with =, +, -, @, are neutralized - the table will not execute them as formulas.

Consumption by people

Block Consumption by people under the measurement table is built according to the team’s common board, and not according to local accounting: someone else’s value exists exactly where the person himself included Publish the cost of my tasks in "Team Projects". The board is requested only when the block is expanded and is updated with a button.

What the block says about itself directly:

  • The amount for participants is not the cost of the project. As a result, it lists what is not in it: how many participants did not give a value at all, how many published cards came without it, and for how many only part of the turns are known. While the list is not empty, the total is shown with the prefix “from”.
  • “Not published” is not zero. The participant's line without a published cost is signed as such; His turns and timing are real - they are always published.
  • The period and area at the top of the screen have no effect. The board stores the total of the card as a whole, and not a section for the week, and to show this total under the caption “for the month” would mean lying with a number. The selected project is valid: the board is searched using the same repository fingerprint.
  • An author who leaves the team remains a line (“participant outside the composition”): his expenses do not disappear from the amount.
  • No connection a saved snapshot of the board with its time is shown; everything that was spent later was not included in the block.

This cut is not included in the upload: the export is collected in the main process from the local history, and the board comes from the cloud.

Money per day and week in the project summary

Project summary tiles only count measurements that the card author has specifically allowed to be published along with their time. Switch Cost of my tasks still gives only the card total. There is an additional choice for periods Time and cost of measurements per week: Timestamps can show co-workers your work schedule, which is why legacy snaps have it turned off. Server without capability cost-history this choice is not accepted.

The card contains no more than 512 measurements for the last week, including turns with an unknown price. With a larger number of measurements, the history is marked incomplete. The summary counts both windows from the date the board snapshot was taken, not from the time the screen was opened. Old cards without history and cards with incomplete history do not turn into an exact zero: the number is signed “from”, next to it shows how many such cards were not included entirely. After turning off history publishing, the next confirmed snapshot of a card removes it from the board; without a connection, this action waits for connection, like other changes to the shared board.

Limit task

Open Time and limits in the task header. You can set:

  • USD: own task limit or common limit from policy settings;
  • maximum turns of all sessions;
  • total minutes of agent execution.

Turns are rechecked immediately before the request from the queue is executed. The last turn that has already been resolved may end. The time is checked every second; Waiting for permits is not included. When time is exhausted, the processes are stopped and the distribution of the swarm is canceled. The monetary limit is responsive to the post-expense report and does not guarantee an exact payment ceiling. If the price is unknown, use turns and time.

The measurement history is stored separately in userData/metrics/, without code and prompts. Deleting a session or task does not reset the costs and limits of the remaining task. Completely deleting application data also deletes this history. Account and dashboard cards clearly show the area of saved sessions; a full historical report is in the Expense section.