Aggregate API Cost from Parent to Subtasks #1609
Replies: 3 comments 1 reply
-
Nice, that makes a lot of sense |
Beta Was this translation helpful? Give feedback.
-
totally makes sense, but also some other ui improvements for representing the parent-subtask-relation would make sense. This can be one part of some adjustments. I am also thinking on nesting sub tasks under parents in the task history so you can visually see what's going on. |
Beta Was this translation helpful? Give feedback.
-
I think it would be best to break it out into 2 cost fields, So you can see what that task did, and what the total task tree did What would be even better, would be if we could see it broken down, ( So we could see how much each agent type is costing, ext... ), Even clicking the cost and downloading a csv of each task, or something |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
Currently, API costs are tracked individually per task started even subtask from parent task. We need to aggregate subtasks costs to the parent task, providing a total cost view for larger/continual tasks. This will improve cost tracking awareness and Roo usages
Proposed Solution:
Beta Was this translation helpful? Give feedback.
All reactions