feat: show root orchestration cost tally for subtasks#11937
Draft
roomote-v0[bot] wants to merge 1 commit intomainfrom
Draft
feat: show root orchestration cost tally for subtasks#11937roomote-v0[bot] wants to merge 1 commit intomainfrom
roomote-v0[bot] wants to merge 1 commit intomainfrom
Conversation
When viewing a subtask spawned by an orchestrator, the TaskHeader now displays the full orchestration cost (aggregated across all tasks in the orchestration) alongside the current task cost. This gives users visibility into total spend without having to navigate back to the parent task. Addresses #11928
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related GitHub Issue
Closes: #11928
Description
This PR attempts to address Issue #11928 by displaying the full orchestration cost (aggregated across all tasks) when viewing a subtask spawned by an orchestrator.
How it works:
rootTaskId(i.e., it is a subtask), we request aggregated costs for the root task via the existinggetTaskWithAggregatedCostsmessage. The response is stored in the existingaggregatedCostsMap.rootOrchestrationCostprop is passed from ChatView. When present and > 0, it renders the orchestration total cost in both the collapsed and expanded views of the task header.chat:costs.orchestrationLabelandchat:costs.orchestrationTotal.No backend changes were needed -- this leverages the existing
rootTaskIdonHistoryItemand the existingaggregateTaskCostsRecursiveinfrastructure.Test Procedure
TaskHeader.spec.tsxcovering orchestration cost display (present, absent, zero value).Manual testing steps:
Pre-Submission Checklist
Documentation Updates
Additional Notes
Feedback and guidance are welcome.
Interactively review PR in Roo Code Cloud